Errors, Warnings & Limits

permissions fields which you do not have permission to access will result in a response with an error block, with errortype set to unauthorized the response payload is still valid and may be consumed you can test your applications handling of deprecated fields by calling query myquery { debug { permissiondeniedexample } } this will trigger the api to return a permissions error within your query if you wish to access a field you do not have access to, contact your account representative field deprecation any query which uses a deprecated field will result in a response with an error block, with errortype set to deprecated the message field will provide an explanation of the deprecation and an alternative field to use, if available the response payload is still valid and may be consumed you can test your applications handling of deprecated fields by calling query myquery { debug { deprecatedexample } } this will trigger the api to return a deprecated error within your query note that this field may be hidden in the graphiql explorer (as it hides deprecated fields by default), however it is present deprecated fields will be removed in future releases if your application receives a deprecated error message, remove the affected fields from your queries and mutations in the event of any other type of error being received, the response payload must be discarded rate limits service rate burst quota profile api 5 per second 3 requests 100 requests per day matching api 100 per second 50 requests 1,000,000 requests per day http errors 429 too many requests when you have exceeded your rate limit to resolve this error, use retries and an exponential backoff algorithm with jitter, and then resubmit your api request 429 limit exceeded when you have exceeded your daily quota