> ## Documentation Index
> Fetch the complete documentation index at: https://developers.nateq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SDKs

> Official client libraries for the Nateq API.

Official SDKs wrap the REST API in idiomatic code for your language. They handle
authentication, retries, and error types, so you don't hand-roll HTTP.

<CardGroup cols={2}>
  <Card title="Node.js" icon="hexagon" href="/sdks/node">
    TypeScript-first, works with Next.js, NestJS, and Express.
  </Card>

  <Card title="PHP" icon="file-code" href="/sdks/php">
    Framework-agnostic, with first-class Laravel support.
  </Card>
</CardGroup>

## What they cover

Both SDKs currently support **outbound email** — send a message and look up what
happened to it. Everything else in the API is available over REST; see the
[API reference](/api-reference).

## What you get

* **Authentication handled** — the key is read from the environment, validated
  before any request, and sent only in the `Authorization` header.
* **Typed errors** — branch on an exception type instead of parsing status codes.
* **Safe retries** — reads retry with backoff; sends never replay a request that
  might already have delivered mail.
* **Secrets kept out of logs** — the client redacts your key when printed, and no
  error message ever carries it.

<Warning>
  Every SDK is **server-side only**. Your API key carries your organization's full
  scope grant — never ship it to a browser, a mobile app, or any client bundle.
</Warning>

## Using another language?

The API is plain REST with JSON, so any HTTP client works. Start with the
[quickstart](/quickstart), then browse the [API reference](/api-reference) for a
live console.