# Startwave API brief

Public integration context for Native 6.0.43 / schema 259.
The supplied release is TEST. This brief does not probe a live service.
This is a short orientation. Use the exact reference and OpenAPI below for every request, response, permission and limit.

## Sources

- Current reference: https://startwave.io/docs/api/
- Complete reference as Markdown: https://startwave.io/docs/api.md
- OpenAPI: https://startwave.io/docs/customer-api.openapi.json
- Synthetic response examples: https://startwave.io/docs/customer-api-examples.json
- Guide: https://startwave.io/guide.md
- Public documentation index: https://startwave.io/llms.txt

OpenAPI SHA-256: 5556f70fc6dbd5161f5ee289375ecd7d99ea0fe3ac470a66a2ec0ae7b31852a2
Examples SHA-256: 5a3e2216ff1c99b7b2d04f8c8d2b22fb0233582a8304fe3593a4850569b21646
These selected files describe the supplied release. They are not an observation of a deployed service. Check advertised capabilities before using a feature.

## Authentication and first read

Base URL: https://api.startwave.io
Use Authorization: Bearer <workspace-key> from a server or terminal. A key belongs to one workspace. Grant only the endpoint's declared scopes. Never paste a real key into an assistant, URL, browser code or source control.

Start with GET /v1/lists and contacts:read. Collection results include items and next_cursor. Pass a returned cursor unchanged with the same filters. An empty page can still have a next cursor. Search and exports have their own continuation contracts; consult the endpoint.

The signed-in workspace uses a separate browser-session contract and CSRF. Do not mix browser endpoints with the public API-key contract.

## Changes and recovery

Review the proposed request before executing it. Persist the operation identity and intent before a write; reuse its Idempotency-Key when required. If the response is lost, read the documented original or by-key endpoint. Do not create a new identity to repeat an uncertain effect.

A receipt records an original outcome. Current state and background progress are separate. Save does not launch a campaign. A pending operation is not a successful send. Reads and this brief do not authorize a purchase, launch or message.

## Integration guidance

Use the declared models, scopes, limits and originals. Do not invent endpoints or fill unknown counts with zero. Keep credentials and recipient records out of shared prompts. Prepare a reviewable change first; the workspace owner decides whether to execute it.