# Indoor API status codes

Source: [https://docs.qualcomm.com/doc/80-42204-2/topic/api-status-codes.html](https://docs.qualcomm.com/doc/80-42204-2/topic/api-status-codes.html)

The JSON API uses standard Hypertext Transfer Protocol (HTTP) status codes to provide
                high-level category of error and additional details as to the nature of the error in
                the response JSON object. You can use these details to provide appropriate feedback
                for user experience and debugging.

The following table provides a list of observable HTTP status codes for the
                Terrestrial Positioning Service (TPS) JSON API request.

Table : HTTP status codes

| Status code | Description |
| --- | --- |
| 200 | OK – The request was successful. |
| 201 | Created – The request has been fulfilled, and a new resource has<br>                                been created. |
| 202 | Accepted – The request has been accepted for processing, but the<br>                                processing hasn't been finished yet. |
| 400 | Bad Request – Invalid input parameters or validation<br>                                failure. |
| 401 | Unauthorized – Missing or invalid Skyhook-Auth-Key. |
| 403 | Forbidden – Valid API key but insufficient permissions for the<br>                                requested resource. |
| 404 | Not Found – Requested resources don't exist. |
| 409 | Conflict – Resource already exists or operation conflicts with<br>                                current state. |
| 413 | Request Entity Too Large – Request body or file size exceeds<br>                                limits. |
| 415 | Unsupported Media Type – Invalid Content-Type header. |
| 500 | Internal Server Error – Unexpected server error. |

Last Published: May 19, 2026

[Previous Topic
Introduction to TPS indoor APIs](https://docs.qualcomm.com/bundle/publicresource/80-42204-2/topics/introduction-to-tps-indoor-api.md) [Next Topic
Indoor API headers and authentication](https://docs.qualcomm.com/bundle/publicresource/80-42204-2/topics/indoor-api-headers-and-authentication.md)