# SuprLogs API

> Integration API for changelog data: health check and GET /v1/projects with published entries for custom UIs.

## Docs

- [Authentication](https://docs.suprlogs.com/api-reference/authentication.md): Use API keys to call the documented read endpoint from your own stack
- [Get a published changelog entry](https://docs.suprlogs.com/api-reference/changelog/get-a-published-changelog-entry.md): Returns a single published changelog entry for the given project slug.
- [List published changelog entries](https://docs.suprlogs.com/api-reference/changelog/list-published-changelog-entries.md): Returns published changelog entries for a project slug.
- [Health check](https://docs.suprlogs.com/api-reference/health-check.md)
- [API Reference](https://docs.suprlogs.com/api-reference/introduction.md): SuprLogs integration API — health check and read-only changelog data for custom UIs
- [List your projects and published changelog entries](https://docs.suprlogs.com/api-reference/projects/list-your-projects-and-published-changelog-entries.md): Returns all projects the caller can access, each with a slice of published changelog entries (newest first). Use this to sync or render changelogs in your own UI. Authenticate with an API key (Bearer or X-API-KEY). Optional `X-Clerk-User-Id` lists personal (user-owned) projects only — API keys are r…
- [Introduction](https://docs.suprlogs.com/index.md): SuprLogs — changelog data you can treat as source of truth for your own UI
- [Quickstart](https://docs.suprlogs.com/quickstart.md): Verify the API and pull projects with published changelog entries

## OpenAPI Specs

- [openapi](https://docs.suprlogs.com/openapi.json)