# SDKs

> Client libraries for the AY Inbox API, and how to generate one.

Source: https://docs.ayinbox.com/api/sdks/

AY Inbox does not publish official client libraries yet. Every surface an SDK would wrap is documented and stable: the REST API, the OAuth2 authorization flows, and the realtime gateway, all on the `v1` API.

Generate a client [#generate-a-client]

The REST API is described by an OpenAPI document, so a typed client for any language is one generator run away. See [OpenAPI](/api/openapi/) for where the document lives and how to generate from it.

Authentication [#authentication]

Any HTTP client works with a bearer credential, and both credential types run through the same permission gates:

* an **API key** for your own scripts (prefixed `aybox_`)
* an **OAuth access token** for apps acting on behalf of a workspace (prefixed `ayat_`)

```bash
curl https://api.ayinbox.com/v1/campaigns \
  -H "Authorization: Bearer aybox_..."
```

For the full authorization-code and client-credentials flows (PKCE and token refresh), see [OAuth](/api/oauth/). For key format, scoping, and rotation, see [Authentication](/api/authentication/).

No-code and automation [#no-code-and-automation]

Prefer a visual builder? See the [Zapier](/guides/zapier/) and [Make](/guides/make/) guides.

See also [#see-also]

* [API overview](/api/) for the base URL, versioning, and conventions
* [Authentication](/api/authentication/) and [OAuth](/api/oauth/)
* [Permissions](/api/permissions/) for the scopes each token can carry
* [Realtime](/api/realtime/) for the event gateway