HTTP response codes

Service version: 1

Last edit: 2022.08.30

Decommission notice

December 16, 2025

This service will be decommissioned on January 31, 2027.

All endpoints will be withdrawn following a 12 months deprecation period.

There is no recommended migration path.

Purpose

The HTTP response codes in the following table describe data returned as a response from an API server after a RESTful request has been made. It includes success and failure codes and their descriptions.

Code	Meaning & possible causes
`200`	OK Deleted
`201`	Created
`400`	Malformed request : Malformed syntax. Possible causes include: The requested syntax is not available.
`400`	Bad request : Parameters out of range. Possible causes include: Group name is too long. Emails amount has been exceeded. WebhookUrls amount has been exceeded. Phone numbers amount has been exceeded. All ways of sending notifications are empty.
`404`	Not Found : Possible causes include: Group id does not exist.
`500`	Internal Server Error : There is a problem with the TomTom Notifications API service.