Error Codes & Responses
The eStream uses consistent HTTP status codes for all responses.Each code includes a clear message and optional
error_code field for advanced integrations.
✅ Success Responses
| Code | Meaning | Example | Notes |
|---|---|---|---|
| 200 | OK | Request processed successfully. | Most GET endpoints. |
| 201 | Created | A new resource has been created. | Used for POST /recruitments |
| 202 | Accepted | Request queued or batch accepted. | Used for /batch calls. |
⚠️ Client Error Responses
| Code | Meaning | Example Message | Resolution |
|---|---|---|---|
| 400 | Bad Request | Invalid or missing parameters. | Check JSON format or query parameters. |
| 401 | Unauthorized | Invalid or expired token. | Log in again using /auth/login. |
| 403 | Forbidden | Access denied. | Verify IP allowlist or role permissions. |
| 404 | Not Found | Resource not found. | Ensure the requested ID or path exists. |
| 409 | Conflict | Duplicate or conflicting record. | Adjust your request payload. |
🚨 Server Error Responses
| Code | Meaning | Example Message | Resolution |
|---|---|---|---|
| 429 | Too Many Requests | Rate limit exceeded. | Wait before retrying or reduce call frequency. |
| 500 | Internal Server Error | Unexpected error occurred. | Contact support with the request ID. |
| 503 | Service Unavailable | API temporarily down. | Retry after a few minutes. |
