Troubleshooting
Please use our Sandbox environment to develop and test your code.
If your private API request is failing, turn on debug logging so you can capture:
- the request method and URL, with credentials and sensitive query parameters redacted
- non-secret request headers, with API-key, authorization, payload, and signature values removed
- the HTTP status code of the response
- the response body after removing account identifiers and other sensitive data
Never share API secrets, private keys, signed payloads, authorization tokens, or full unredacted request and response data.
Make sure that you are not sending the JSON as the POST body.
If you receive a 400 error that you are missing required data, then copy the base64 encoded string in X-GEMINI-PAYLOAD to a base64 decoder such as https://www.base64decode.org/ and decode it. Compare the decoded JSON to the documentation for the endpoint you are trying to access.
If you are receiving a 429 response, then see Rate Limits.
Support
If you still have a problem, use the Gemini Support request form with the following information:
- Which environment did you try to make the request in, production or sandbox?
- What URL were you trying to hit?
- What IP address did you make the request from?
- What date and time (including time zone) did you try to make the request?
Please include, after redacting secrets and personal data:
- relevant non-secret HTTP request headers
- the redacted JSON response from the server
If you leave any of this information out, the response to your support request may be delayed.