Skip to main content

Error Codes

API Error Codes

Joe Caffrey avatar
Written by Joe Caffrey
Updated over a month ago

Status Codes

The TeleTracking API uses standard HTTP response status codes to indicate the outcome of each request. These codes help developers identify whether the request was processed successfully or failed due to invalid input, authorization issues, or server-side errors.

We do not currently provide custom error response headers or application-specific error formatting. For a comprehensive list of HTTP status codes and what they mean, refer to this resource:

Common Examples:

  • 200 OK — Request succeeded

  • 400 Bad Request — Malformed request or missing data

  • 401 Unauthorized — Missing or invalid authentication token

  • 403 Forbidden — Authentication was valid, but access is not allowed

  • 404 Not Found — Endpoint or resource does not exist

  • 500 Internal Server Error — Server encountered an unexpected error

Tip: When troubleshooting issues, ensure you are sending the correct headers, using the appropriate endpoint path, and verifying your access token is current and valid.


Handling Errors in Code

We recommend adding basic error handling to your integration to help identify and troubleshoot common issues programmatically.

try:
response = requests.post(
url=f"{baseUrl}/customdatareceiver/externalcustomdata",
headers={
"Content-Type": "application/json",
"Authorization": f"Bearer {accessToken}"
},
data=payload
)
response.raise_for_status() # Raises HTTPError for bad responses
print("Request successful:", response.json())

except requests.exceptions.HTTPError as http_err:
print(f"HTTP error occurred: {http_err}")
print("Response content:", response.text)
except Exception as err:
print(f"Other error occurred: {err}")


Persistent Errors

If you continue to experience issues, contact our support team via chat and provide them with the following information

  • The full endpoint you were calling

  • The exact error message and response code

  • The request headers and payload you sent. (Do not expose your accesstoken)

  • The timestamp and timezone of your request

  • Any other relevant context (e.g., environment)

Our team will review your request and assist you as quickly as possible.

Did this answer your question?