# Status Errors

### 400: Bad Request <a href="#id-400-bad-request" id="id-400-bad-request"></a>

*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 <a href="#id-403-forbidden" id="id-403-forbidden"></a>

*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 <a href="#id-429-too-many-requests" id="id-429-too-many-requests"></a>

*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.

If you require a rate limit increase, please reach out to **<support@heypoplar.com>**

### 500: Internal Server Error <a href="#id-500-internal-server-error" id="id-500-internal-server-error"></a>

*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 **<support@heypoplar.com>** for assistance.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.heypoplar.com/integrations/troubleshooting/status-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.