📄️ Authenticating requests
Each request to the Emogg REST API must be accompanied by an Authorization header containing a valid token. This token authenticates the request, linking it to your account and ensuring secure access to your data.
📄️ Errors
When interacting with the Emogg REST API, it's important to handle errors gracefully. The API uses conventional HTTP response codes to indicate the success or failure of requests. In case of an error, the API response will include a JSON object with detailed information to help diagnose and resolve the issue.
📄️ Expanding responses
By default, certain fields in response objects may contain only an ID of a related object. The expand parameter enables you to request the full details for these related objects directly within the initial response. For example, by default, a "session" object might have an associated user ID. However, with the expand parameter you can request the full user information to be included in the response.
📄️ Pagination
To ensure efficient data retrieval and manageability, the Emogg REST API implements cursor-based pagination for all endpoints that return lists of data. This system allows clients to fetch subsets of data, making it easier to handle large datasets and improve the responsiveness of applications using the API.
📄️ Rate limits
To ensure fair usage and protect the Emogg REST API from excessive requests, we implement rate limiting using a Token Bucket algorithm. This mechanism helps in controlling the rate at which user requests are processed, ensuring a consistent and reliable service for all users.
🗃️ Sessions
13 items