Key response codes you may encounter while using the Kit API
We return the Unauthorized error in a variety of situations, including:
In order to troubleshoot this yourself, please check the error message, which will help you understand why access is not being granted. If this issue persists, please reach out to support.
If you try to enqueue too many bulk requests at once, you’ll receive an error response with a 413
status code, which your code should gracefully handle. Details on handling bulk processing can be found here.
When you create or update a field, you may receive an error response with status code 422
if any fields contain bad data or required fields are missing.
We have different rate limits depending on the authentication strategy used:
If your request rate exceeds our limits, you will receive an error response with status code 429
, which your code should gracefully handle. We recommend spacing out your requests and performing an exponential backoff to keep within the limit.
If the server is overloaded or you encounter a bug, you will receive a response with status code 500
. Try again after a short period, and if you continue to encounter an error, please raise the issue with support.
Key response codes you may encounter while using the Kit API
We return the Unauthorized error in a variety of situations, including:
In order to troubleshoot this yourself, please check the error message, which will help you understand why access is not being granted. If this issue persists, please reach out to support.
If you try to enqueue too many bulk requests at once, you’ll receive an error response with a 413
status code, which your code should gracefully handle. Details on handling bulk processing can be found here.
When you create or update a field, you may receive an error response with status code 422
if any fields contain bad data or required fields are missing.
We have different rate limits depending on the authentication strategy used:
If your request rate exceeds our limits, you will receive an error response with status code 429
, which your code should gracefully handle. We recommend spacing out your requests and performing an exponential backoff to keep within the limit.
If the server is overloaded or you encounter a bug, you will receive a response with status code 500
. Try again after a short period, and if you continue to encounter an error, please raise the issue with support.