# API Response Codes

**200 - Success**

Returned when the request is valid and the authenticated admin has access to this api endpoint. Response body is a JSON array of job applications formatted for HRIS.

**400 - Bad Request**

The request could not be processed due to invalid input. Common causes:

* Incorrect date format
* \`job\_application\_status\_start\` or \`job\_application\_status\_end\` is not a valid date/datetime.
* Expected formats:
  * \`yyyy-MM-dd\` or \`yyyy-MM-ddTHH:mm:ss\` or \`
* Example message:
  * “Invalid date format: 'Tuesday'. Expected date or datetime in one of the following ISO-8601 formats: " + "'yyyy-MM-dd', 'yyyy-MM-dd'T'HH:mm:ss', or 'yyyy-MM-dd'T'HH:mm:ssZ' (with timezone or UTC offset).”
* Invalid date range
  * \`job\_application\_status\_start\` is after \`job\_application\_status\_end\`.
  * Example message: “job\_application\_status\_start date must be before the job\_application\_status\_end”
* Invalid status filter
  * \`job\_application\_status\` is not a recognized pipeline status for your jobs.
  * The status needs exist on an active Pipeline
  * Example message: “'INVALID\_STATUS' is not a valid active status value.'”
* Invalid status bucket filter
  * \`job\_application\_status\_bucket\` is not a recognized pipeline status bucket for your jobs.
  * The status needs exist on an active Pipeline
  * Example message: “'INVALID\_STATUS' is not a valid status bucket value.'”

Fix this status code by correcting parameter formats/values and retrying.

**401 - Unauthorized**

Authentication or authorization failed. Typical reasons:

* The HRIS API feature is not enabled for your organization.
* You are attempting to use the API with credentials tied to a non-admin user
* Example message:
  * “Reach out to support for access to this endpoint”

Remediation: Contact Flo Support to enable access and ensure your account has the necessary permissions.

**429 - Too Many Requests**

The request was rate-limited. Our API is Rate Limited to 1000 requests / 5 minutes.Remediation: Back off and retry after the time specified in response headers (if present), or implement client-side rate limiting/retries with exponential backoff.

**500 - Internal Server Error**

An unexpected error occurred on the server while processing the request.

* Example message:
  * “Failed to fetch candidates”

Remediation: Retry later. If the error persists, contact Flo Support with the request details and timestamp.<br>


---

# 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.joinflo.com/flo-apis/hris-api/api-response-codes.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.