---
title: Response status codes
slug: response-status-codes
docTags: 
createdAt: 2023-04-12T08:24:38.000Z
---

The API can respond with any of the following response codes:

:::hint{type="success"}
**2xx – **The response was successful.
:::

:::hint{type="danger"}
**400 Bad Request – **Something was wrong with your request. We don't have further details — but we do recommend checking your syntax and parameters of your request, and that the queried organization ID and event ID exist.
:::

:::hint{type="danger"}
**403 Forbidden – **You didn't provide a valid API Access Token, or the owner of the API key have "Organization Administrator" (Org Admin) privileges within your event's organization on Brella.
:::

:::hint{type="danger"}
**404 Not Found – **You are trying to access a resource that doesn't exist. This error can also occur if there are issues with the request url. For example, assume that you are trying to GET /api/integration/organizations/1/events/123. 



While an event with id 123 does exist, it belongs to organization 2. As such, the API would return a response of 404, as it is searching for event 123 in organization 1 — which is an entity that does not exist.
:::

:::hint{type="danger"}
**422 Unprocessable Entity – **You are trying to create or update a resource with invalid data. We recommend checking your syntax and parameters of your request, and that the queried organization ID and event ID exist.
:::

:::hint{type="danger"}
**5xx Internal Server Error –** Our code crashed. Sorry about that. Our error tracking system probably caught this, and we will look into it soon. However, if you are in a hurry, please reach out to your Brella contact person (most likely your Customer Success Manager or Key Account Manager) to request a quick fix. You can also leave us a message via our Technical Support team.
:::