The Edith Service API enables seamless email configuration, sending, receiving, and tracking with high reliability and scalability. Designed for fault tolerance, it ensures smooth email communication by eliminating single points of failure while minimizing operational effort.
When registering your service or product with EDITH, you received a bearer token. Use this token for authentication in API requests.
curl --request GET \ --url https://api.sparrowmailer.com/v1/domains --header 'Authorization: Bearer your-edith-access-token'To call APIs, use the corresponding URL based on your account’s data center.
| Region | API URL |
|---|---|
| US | https://api.sparrowmailer.com |
We use the standard HTTP status codes like 2xx for success and 4xx for failure. Refer to the following table for status codes.
| Response Code | Description |
|---|---|
| 200 OK | The request was successfully processed. |
| 202 Accepted | The request has been accepted for processing, but the operation is not yet complete. |
| 204 No Content | The server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| 400 Bad Request | Request has missing required parameters or validation errors |
| 401 Unauthorized | The request lacks valid authentication credentials. |
| 403 Forbidden | The request is authenticated, but the user does not have permission to access the resource. |
| 404 Not Found | The requested resource could not be found. |
| 409 Conflict | The request conflicts with an existing resource, such as trying to create a duplicate entry. |
| 422 Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors. |
| 500 Internal Server Error | The server encountered an unexpected issue that prevented it from fulfilling the request. |
For any support or configuration assistance, contact the Hygiene team. We can help with: