Skip to content
pokemontcgapi.com
sign in

welcome

Payment received. The plan is landing on your account.

Nothing else is required from you. This page exists so that the seconds between the payment and the new limits are explained rather than silent.

  1. 01

    Nothing to rotate

    The plan lives on the account, not on the key. The key you already have is the key that now carries the new limits — no new credential, no redeploy, no second integration.

  2. 02

    Give it a few seconds

    Stripe returns you here as soon as the payment succeeds; the plan is applied by a webhook that lands moments later, and every running process picks it up within about a minute.

  3. 03

    Then check it

    GET /v1/me is the answer that counts: it reports the plan, the credit ceiling, what you have spent and when the period rolls over. If it still says the trial after a minute, write to us with the request_id.

is it live?
curl -s "https://api.pokemontcgapi.com/v1/me" -H "X-Api-Key: $PTCG_API_KEY"

# "plan": { "code": "GROWTH", … }
# "quota": { "credits_limit": 2500000, "renews": true, … }

next

Three things worth doing in the first hour.

None of them are required. All three save a support conversation later.

Mint a second key

One per environment. POST /v1/me/keys issues it, and revoking one never touches the others — which is the whole reason to have more than one.

Handle 429 properly

Every rejection carries Retry-After and an error code that says which ceiling you hit. The errors page lists all of them.

Cache with ETags

A 304 costs nothing at all. Card data changes when a set releases, not when you poll, so a client that revalidates properly serves far more lookups than it spends credits.

Invoices, the payment method and cancellation are all on the billing page. Anything else: [email protected].