Status Errors
A guide to status errors you may encounter when testing integrations.
400: Bad Request
Client Error
A 400 error indicates a client error somewhere in the webhook. We recommend checking the following:
Your Poplar campaign is Active and has creative uploaded.
The variables in your webhook match the values in the user profile.
The required address_1, city, state, and postal_code data is present.
The user you are testing with has all the data above saved on their profile.
Double check the JSON syntax is correct and you dont have any extra commas or curly braces.
403: Forbidden
Client Error
A 403 error indicates a client error related to Authentication. We recommend checking the following:
The key to your Authorization header has "Bearer testorproductiontoken".
Your API access token was copy and pasted completely.
(Klaviyo Only) If a webhook has been duplicated, make sure you copy and paste your access token directly from Poplar otherwise the hashes ### will be copied over instead of the full access token.
If you have multiple organizations, make sure you're using the correct corresponding token for the account.
If you are connecting to an endpoint other than the Mailing API (Audiences, Orders, Do Not Mail, etc.), make sure you are using your Production token. Only the Mailing API is built to accept the Test token.
429: Too Many Requests
Client Error
A 429 error indicates too many requests are being sent through at once and a rate limit is being hit - either on the side of your CRM/ESP or on the Poplar end.
To prevent misuse, our API endpoints implement rate limiting. If your application exceeds this limit then a HTTP 429 "Too Many Requests" response code will be returned.
HTTP headers are returned on all endpoints which contain how many more requests your application is allowed.
x-rate-limit-limit
The rate limit for a given endpoint
x-rate-limit-remaining
The number of requests remaining
x-rate-limit-reset
The time at which the rate limit resets
500: Internal Server Error
Server Error
A 500 error indicates a server error on the Poplar side, meaning our servers could be down. This is extremely rare, and we recommend double checking all of the points above to be safe. If you're still experiencing a 500, reach out to [email protected] for assistance.
Last updated