Support
Email contact@goalschema.com. Put the details below in your first message, so the problem can be traced from your request to the answer it got, without a round of questions first.
What to send
Most errors explain themselves: error.code is stable, and the errors table says what each one means. When that is not enough, send these.
| Send | Where to find it |
|---|---|
| The key's prefix | gs_live_ and the eight characters after it, as the console's Keys page shows them. Never the whole key: if one was ever pasted anywhere, create a replacement and revoke the old one. |
| The request | The method, the path and the query string. The API never reads a key from the URL; if you put one there, take it out before you send the URL (and replace that key). |
| The time, in UTC | When you sent it, to the second. |
| The status and error.code | The HTTP status, and error.code from the body of the answer. |
| meta.generated_at | In the body of every answer, errors included. |
| X-Quota-* and X-Plan | Response headers on a keyed request. curl -i prints them above the body; on a 429, add Retry-After. |
Key prefix: gs_live_… (never the whole key)
Request: GET /football-scores/v1/…
Time (UTC): YYYY-MM-DDTHH:MM:SSZ
Status: HTTP status and error.code
Generated: meta.generated_at
Headers: X-Quota-*, X-Plan
Expected: what you expected insteadSend the match id, the field that looks wrong (a score, the kickoff or the status), the value you got and the one you expected, with a link to where you saw it. The sync re-reads recent matches on every run, so a recent one can still change on its own: read it again before you report it.
Business limits and support are agreed by email. To size it, tell us:
Keys, usage and billing live in the console. A plan is changed or cancelled under Billing.