# SureDocs developers

> SureDocs collects the documents insurers issue and files them with the insurance brokerage they belong to. Its
> public API lets a partner's server send documents (PDF, JPEG or UTF-8 text) to a brokerage's SureDocs account,
> on that brokerage's behalf, with an OAuth 2 access token obtained from a rotating refresh token.

To build an integration, read [the brief for coding agents](https://developer.suredocs.ie/agents.md) first, then the pages it
links to. The docs and the brief are Markdown, the reference is JSON. [llms-full.txt](https://developer.suredocs.ie/llms-full.txt) is the brief and every page in one file.

## Brief

- [Building a SureDocs integration](https://developer.suredocs.ie/agents.md): the steps, in order, and the rules that are most often got wrong.

## Docs

- [Overview](https://developer.suredocs.ie/index.md): What SureDocs does, where to start, and the conventions every API follows.
- [Getting started](https://developer.suredocs.ie/getting-started.md): The whole flow with curl, from a refresh token to a PDF filed with a brokerage, and the duplicate answer.
- [Authentication](https://developer.suredocs.ie/authentication.md): The token exchange, refresh-token rotation, grants, scopes, every error, and how to store a refresh token.
- [Versioning and deprecation](https://developer.suredocs.ie/versioning-and-deprecation.md): What may change within a version, what may not, and how a version is retired.
- [Rate limits](https://developer.suredocs.ie/rate-limits.md): The limits, the RateLimit headers, and what to do on a 429.

## API reference

- [SureDocs files API, version 1](https://developer.suredocs.ie/openapi-files-v1.json): the OpenAPI 3.1 document, generated from the code that serves it.
- [SureDocs authorization server](https://developer.suredocs.ie/openapi-oauth.json): the OpenAPI 3.1 document, generated from the code that serves it.

## Optional

- [Developer portal](https://developer.suredocs.ie/portal/): where a developer signs in to register an integration and issue its refresh token. It needs a person; a tool cannot use it.