# Troubleshoot API integrations
URL: https://support.starshipit.com/articles/14700000001010-troubleshoot-api-integrations
Canonical: https://support.starshipit.com/articles/14700000001010-troubleshoot-api-integrations
Markdown: https://support.starshipit.com/articles/14700000001010-troubleshoot-api-integrations.md
Updated: 2026-06-18

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Fix common API request failures and know what to check first.

If an API request fails, start by checking the API family, endpoint, credentials, headers, and request body. Most issues are caused by one of those five things.

Use the [Starshipit API reference](/developers/api-reference/starshipit) or [WMS API reference](/developers/api-reference/wms) to compare request fields, headers, and response examples.

## Common failures

| Response | Likely cause | What to check |
| --- | --- | --- |
| 400 Bad Request | Request parameters or body are invalid | Compare the payload to the reference docs and confirm required fields are present. |
| 401 Unauthorized | Credentials are missing or incorrect | Confirm the API key, subscription key, and environment are correct. |
| 403 Forbidden | The request is not allowed | Check account access, key permissions, and whether you are calling the right API family. |
| 404 Not Found | Wrong endpoint or URL | Confirm the base URL and endpoint path match the documentation. |
| 429 Too Many Requests | The integration exceeded its rate limit | Queue the request and retry with backoff instead of sending repeated immediate retries. |

## What to capture

- The exact endpoint URL.
- The full request headers.
- The request body.
- The response body and status code.
- The workflow you were testing, such as order import, label generation, product sync, rates, or tracking.

## Confirm the fix

Re-run the request with a small test payload after you make a change. If it still fails, compare the request against the relevant product guide before retrying.