Skip to main content

Troubleshooting common API errors and issues

General troubleshooting guide when encountering errors or issues with Float API

Jon Palustre avatar
Written by Jon Palustre
Updated yesterday

If you encounter trouble while using the Float API, here’s some troubleshooting steps you can try to resolve them.

For full API reference, check our developer docs. This resource provides information on authentication, endpoints, request parameters, and response formats.

API error codes

401 Unauthorized error

  • Confirm you're using a valid API key (found under Team Settings > Integrations - accessible by the Account Owner).

  • Check that your API key is included in the request headers.

  • Double-check the base URL:
    https://api.float.com/v3

If using IP restrictions:
Ensure the IP address making the request is allowed in your account settings.

404 Not Found error

  • Check for typos in your endpoint path and confirm you're using a valid route from our API documentation.

  • Common mistakes include missing /v3 or incorrect resource names or ID's.

  • Missing required parameters

    • Some endpoints require specific parameters to return results.

      For example, when retrieving reports and filtering by project, both start_date and end_date are required.

      Example:

      GET https://api.float.com/v3/reports?project_id=12345&start_date=2024-01-01&end_date=2024-01-31

  • Incorrect parameters

    • Incorrect resource names or IDs. Always make sure that the ID of the data you want to pull in is correct.

      Example:

      GET https://api.float.com/v3/reports?project_id=12345


      Always refer to the API documentation for the required query parameters per endpoint.

400 Bad request error when sending body with GET request

  • Remove the request body from all GET requests. Float’s API expects all parameters to be passed in the query string.

422 Error

  • Invalid Data Format

    • Make sure fields are formatted correctly (e.g., date fields are in YYYY-MM-DD format).

    • Use proper JSON structure - no trailing commas or malformed brackets.

  • When sending an array of tasks

    • Currently, the Float API only supports creating one task per request. Sending an array (e.g., [{}, {}]) will result in an error.

    • Send each task in a separate POST request. Do not wrap them in an array.

Testing API call in Postman

Postman is a free, beginner-friendly tool for testing APIs without writing code. It allows you to send test requests and instantly see the response or errors before implementing the API fully.

Here are the steps to test API calls in Postman:

  1. Set up your environment:

    • Base URL: https://api.float.com/v3

    • Add Header:

      Authorization: Bearer YOUR_API_KEY 
      Content-Type: application/json
  2. Make a request:

    • Example: Get all tasks for a specific date

      GET https://api.float.com/v3/tasks?expand=task_days&start_date=2021-04-14&end_date=2021-04-14
  3. Review the response:

    • Status code, headers, and body

    • Check for clues in the message or error fields for validation issues

General Troubleshooting Checklist

Before reaching out to support, review the following:

  • API Key: Is it correct and active?

  • Endpoint: Does the full URL match the format https://api.float.com/v3/{endpoint}?

  • Method: Are you using the correct HTTP method (GET, POST, PUT, DELETE)?

  • Headers: Is your API key added correctly in the Authorization header?

  • Payload Format: Are you sending valid JSON when required?

  • API Changes: We regularly update and enhance our API. Please refer to our changelog to check if any recent changes may impact your current API setup.

If you’ve checked everything and are still stuck, please share the following with our support team:

  • API endpoint you’re calling

  • Request method and full URL

  • Headers and payload (if applicable)

  • Full error message or response

Did this answer your question?