Skip to content
pokemontcgapi.com

Contact

Contact pokemontcgapi

One address for support, billing, data and security questions, read by the people who run the API. Pick the channel by what you need, not by which one answers first.

Email
Support, billing, data corrections, rights complaints and security reports. The only channel for anything that involves an account. riccardo (at) rarebit.app
Discord
Questions while you integrate, and the fastest place to ask whether something you see is expected. Join the server
GitHub
Bugs and pull requests for the SDKs, the MCP server and the examples, which are open source. Open an issue
X
Release notes and incidents, announced as they happen. Not monitored for support. @pokemontcgapi

What to include in a support request

Five things that let us answer at the first exchange instead of the third.

  1. The endpoint and the full URL you called, query string included, without the key.
  2. The error.code and the request_id from the response body: they identify the exact call in our logs. The code is repeated in the X-Error-Code header.
  3. The time of the call, in UTC, and roughly how many calls you were making per second.
  4. The first characters of the key you used, never the whole secret. If you have pasted a secret anywhere public, rotate it from your account first.
  5. What you expected to receive, and what the documentation page you were following says.

Support by plan

What each plan includes, as published on the pricing page.

PlanSupport
TrialCommunity
DeveloperEmail
GrowthEmail, one business day
ProfessionalEmail, same business day
EnterpriseNamed contact

Billing, data and security

Three kinds of message that each need one extra detail.

Billing. Paid plans are billed by Stripe. Plan changes and cancellations are made from your account page; for an invoice question, quote the account email and the invoice number.

Data corrections. For a wrong card, set or quote, send the card id or set code, what the API returns and what you believe is correct, with a reference we can check. Corrections are recorded in the changelog.

Security. Report a vulnerability by email with “security” in the subject rather than in a public issue or on Discord. Include the steps to reproduce it and the impact you believe it has.

Before you write

Most questions about costs, limits and errors are answered in the documentation, which is also available as Markdown for your assistant.