Skip to content

Commit 799a24d

Browse files
Update faq.mdx
Added a section about 500: `bad_database_response` errors
1 parent b7e46b5 commit 799a24d

File tree

1 file changed

+4
-0
lines changed
  • website/src/pages/en/token-api

1 file changed

+4
-0
lines changed

website/src/pages/en/token-api/faq.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,10 @@ You can find the code for the MCP client in [The Graph's repo](https://github.co
7676

7777
Check that you included the `Authorization: Bearer <jwt>` header with the correct, non-expired token. Common issues include using the API key instead of generating a new JWT, forgetting the "Bearer" prefix, using an incorrect token, or omitting the header entirely. Ensure you copied the JWT exactly as provided by The Graph Market.
7878

79+
### Why am I getting 500 errors?
80+
81+
Networks that are currently or temporarily unavailable on a given endpoint will return a `bad_database_response`, `Endpoint is currently not supported for this network` error. Databases that are in the process of ingestion will produce this response.
82+
7983
### Are there rate limits or usage costs?
8084

8185
During Beta, the Token API is free for authorized developers. There are no specific rate limits, but reasonable throttling exists to prevent abuse. High request volumes may trigger HTTP 429 errors. Monitor official announcements for future pricing changes after Beta.

0 commit comments

Comments
 (0)