Migomail Email API API Reference
Full REST API for email sending, campaign management, subscriber management, and analytics.
Use the appropriate base URL for your environment. All requests must use HTTPS.
| Environment | Base URL | Default |
|---|---|---|
| Production | https://api.migomail.com/v1 |
✓ |
| Sandbox | https://sandbox.api.migomail.com/v1 |
Pass your API key in the X-API-Key request header.
X-API-Key: {your_api_key}
API key authentication and token management.
https://app1.migomail.net/api/v1/lists
https://api.migomail.com/v1/api/v1/user/login
Example
curl -X POST -H "accept:application/json" -G \ https://app1.migomail.net/api/v1/user/login \ -d email=user@example.com \ -d password=yourpassword
No response examples have been added for this endpoint.
curl -X POST -H "accept:application/json" -G \ https://app1.migomail.net/api/v1/user/login \ -d email=user@example.com \ -d password=yourpassword
Send transactional and bulk email.
Add, update, and manage email subscribers.
Create and trigger email campaigns.
Query campaign performance and subscriber metrics.
Configure and manage webhook endpoints.
All errors return a JSON object with a message field and, for validation errors, an errors object containing field-level details.
| Status | Name | Description |
|---|---|---|
| 200 | OK | Request succeeded. |
| 201 | Created | Resource created successfully. |
| 400 | Bad Request | The request body or parameters are invalid. |
| 401 | Unauthorized | Missing or invalid API key. |
| 403 | Forbidden | API key does not have permission for this action. |
| 404 | Not Found | The requested resource does not exist. |
| 422 | Unprocessable Entity | Validation failed. Check the errors field. |
| 429 | Too Many Requests | Rate limit exceeded. See Retry-After header. |
| 500 | Internal Server Error | An unexpected server error occurred. |
{
"message": "The given data was invalid.",
"errors": {
"email": ["The email field is required."]
}
}