# Build with ConversionLab

Integrate project data and reporting with your own systems using the REST API.

Use the REST API to read and update supported project data and retrieve experiment reports. Start with a team-scoped API key, then choose the endpoints your integration needs.

## Connect your application

[API keys and permissions](https://conversionlab.app/docs/developer/authentication)

Create a team-scoped key and understand authentication, token abilities, and
user roles.

[API conventions](https://conversionlab.app/docs/developer/api-conventions)

Understand pagination, filters, uploads, limits, and error responses.

[REST API reference](https://conversionlab.app/docs/developer/api)

Find supported methods, paths, request fields, response schemas, and examples.

## Supported public surface

REST covers projects, research collections and screen evidence, observations, insights, learnings, ideas, experiments and variations, definitions, prioritization, numbering, attachments, comments, survey management and responses, experiment reporting and approvals, activities, the current user, and reading today's brief.

Provider connection and synchronization, AI generation, team administration, billing, session authentication, and key management are configured through product workflows rather than the supported core REST contract. Public widget protocols and inbound provider callbacks are also separate from the customer integration reference.

The reference documents existing runtime paths. There is no new `/v1` prefix introduced by these docs. The [OpenAPI download](https://conversionlab.app/docs/openapi.json) provides the same published REST contract in a machine-readable form.

For HTTP conventions and recovery behavior see [API conventions](https://conversionlab.app/docs/developer/api-conventions).