rest-graphql-debug

Verify the Authorization header is actually sent using curl -v, then check the token is unexpired by decoding the JWT exp claim. Confirm the correct auth scheme (Bearer vs Basic vs API key) and that you are not using a staging key against production.

GraphQL servers often return HTTP 200 even when the query fails, placing error details in the errors field of the response body. Always inspect data.get("errors") regardless of status code and print each error's message and path.

Implement exponential backoff by checking the Retry-After header and retrying up to five attempts with increasing wait times. Also inspect X-RateLimit-* headers to understand your quota before retrying.

Passing a string via data= sends form-encoded data even if you set a JSON header manually, causing silent 415 or 400 errors. Use the json= parameter instead, which serializes the payload and sets Content-Type: application/json automatically.

Pass a tuple timeout like (3.05, 30) to requests and catch ConnectTimeout versus ReadTimeout separately. With curl, use -w to print time_connect and time_starttransfer: high connect time indicates network issues, while high TTFB indicates a slow server.

Skip this workflow for UI rendering bugs, database query tuning, or DNS and firewall infrastructure problems, which should be escalated to the appropriate owners. It targets application-layer HTTP and GraphQL diagnosis only.