> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://api-docs.appeared.in/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://api-docs.appeared.in/_mcp/server.

The Appeared.in Public API is designed for read-only sponsor discovery workflows.

This page explains the current API limitations, rate limits, pagination limits, and the errors your application may receive.

### Current Scope

Public API access is currently available for:

* `GET /api/public/v1/sponsors`

Other public endpoints, such as newsletter, podcast, and filter metadata list endpoints, are currently disabled.

### Access Requirements

Requests must include a valid Bearer token:

```bash
Authorization: Bearer lh_<token>
```

The token must belong to an active user in an organization with Public API access enabled.

Some sponsor media access may also depend on your organization’s enabled features. For example, newsletter or podcast-related sponsor data may require the matching organization feature.

### Rate Limits

Rate limits are enforced per organization, not just per token.

Current limits:

* **60 requests per minute**
* **500 requests per hour**
* **1000 requests per day**

If your organization exceeds a rate limit, the API returns:

```text
429 Too Many Requests
```

To avoid rate limit errors, pace requests on your side and retry rate-limited requests with exponential backoff and jitter.

### Pagination Limits

Public API endpoints use page-based pagination.

The maximum `page_size` is **50**. If your request asks for a larger `page_size`, the response is capped at 50.

### Common Error Responses

```text
401 Unauthorized
```

Returned when the Bearer token is missing, invalid, belongs to a disabled user, or no longer has Public API access.

```text
403 Forbidden
```

Returned when the request requires an organization feature that is not enabled.

```text
400 Bad Request
```

Returned when the request includes invalid filter or query parameters.

```text
429 Too Many Requests
```

Returned when the organization-level rate limit is exceeded.

### Recommended Client Behavior

* Keep `page_size` at or below `50`.
* Avoid retries in tight loops.
* Use exponential backoff with jitter after `429` responses.
* Cache results where possible to avoid repeated identical requests.
* If repeated `401` or `403` responses occur, refresh credentials or contact your organization admin.