Requests and responses
Learn how Livestorm's REST API accepts requests and sends back responses
Requests
Livestorm's REST API follows the JSON API conventions, which means that you'll have to encode your requests in JSON. Additionally, don't forget to add the Content-Type: application/json header to your HTTP requests. All requests must be sent over HTTPS.
Responses
Similarly, API responses will be JSON-encoded. Standard HTTP codes will apply:
2xxfor successful requests200for successful GET, PUT, and PATCH calls.201for successful POST calls (created).204for successful DELETE calls (no content).
4xxfor user-related errors:400errors when the payload (body/query params) is invalid or incorrectly formatted.401errors when your authentication isn't valid (missing or invalidAuthorizationheader value).402errors are related to your billing preferences and happen when you reached your monthly active contacts allowance. You need to upgrade your plan to unlock new active contacts.403errors when the resource you're trying to access isn't included in your scopes (API token scopes or OAuth2 access token scopes) or if your account hasn't been validated.404errors when the resource you're trying to access doesn't exist.409errors when the resource already exists (usually when someone is already registered to a session).422errors when the payload is valid but cannot be processed by Livestorm due to incorrect business logic.429errors when your API rate limits have been reached.
5xxfor unexpected server errors. Please get in touch with us if this happens.
Updated 8 months ago