Handle LoudCrowd API responses and retries safely.
Response formats and authentication failures differ by API surface. Follow the endpoint-specific contract rather than assuming every LoudCrowd API returns the same error shape.
HTTP status guide
Endpoints use the applicable statuses from this table. Refer to an endpoint's documentation for its response fields.
| Code | Summary | Description |
|---|---|---|
200 | OK | The request succeeded or was accepted for processing. |
400 | Bad Request | A parameter, header, or request payload is invalid. |
401 | Unauthorized | Authentication is missing or invalid, or the request is not authorized. |
403 | Forbidden | The authenticated caller is not permitted to perform the action. |
404 | Not Found | The requested endpoint or resource does not exist. |
429 | Too Many Requests | The request was rate limited. Follow Retry-After when present. |
500 | Server Error | LoudCrowd encountered an unexpected error. |
503 | Service Unavailable | The service is temporarily unavailable. Retry with bounded backoff. |
Rate limits
If an API returns 429 Too Many Requests, honor Retry-After when present. Otherwise, retry with bounded exponential backoff and jitter.
For the Attribution Events API, verify that each request returns status 200 with the plain-text body success before treating the event as accepted.
Retry guidance
Retry transient 429 and 5xx responses with a capped exponential delay and jitter. Do not automatically retry 400 or 401 responses without changing the request. When retrying Attribution Events requests, reuse the same order and refund IDs.