Currents News API Documentation

Error Responses

All endpoints use a consistent error payload so clients can handle failures predictably.

{
  "status": "400",
  "msg": "Invalid parameters",
  "details": {
    "message": "Invalid parameters",
    "errors": {
      "page_number": "Must be >= 1"
    }
  }
}

For auth failures, payloads are typically:

{
  "status": "401",
  "msg": "Authentication required"
}

Common Error Codes

  • 400 Bad Request: Invalid or malformed query parameters.
  • 401 Unauthorized: Missing/invalid API key.
  • 403 Forbidden: Request blocked by policy or account restrictions.
  • 404 Not Found: Unsupported endpoint or resource.
  • 429 Too Many Requests: Daily or burst limits exceeded.
  • 5xx Server Errors: Temporary upstream/internal issue.

Handling Strategy

Retry Policy

Retry only idempotent requests on 5xx errors with exponential backoff and jitter.

Rate Limit Handling

On 429, inspect rate-limit headers and delay non-critical polling until quota resets.

Continue with endpoint docs: Latest News and Search.