# API introduction

> Base URL, conventions, and object ids for the Inboundr REST API.

The Inboundr REST API is a small, predictable JSON API. Every endpoint is
authenticated with a bearer token, returns JSON, and uses standard HTTP status
codes.

## Base URL

```
https://inboundr.net/api/v1
```

## Conventions

- **Requests** — send JSON with `Content-Type: application/json`.
- **Auth** — every request needs an `Authorization: Bearer inb_…` header. See
  [Authentication](/api-reference/authentication).
- **Responses** — always JSON. List endpoints wrap results in `{ "data": [...] }`;
  paginated lists also include `nextCursor`.
- **Errors** — non-2xx responses carry an `error` field. See
  [Errors](/api-reference/errors).
- **Timestamps** — ISO 8601 UTC strings (e.g. `2026-07-20T10:30:00.000Z`).

## Object ids

Ids are prefixed by type, so they're self-describing:

| Prefix | Object |
| --- | --- |
| `dom_` | Domain |
| `ep_` | Endpoint |
| `em_` | Email |
| `thr_` | Thread |
| `inb_` | API key |
| `whsec_` | Endpoint signing secret |

## Resources

<CardGroup cols={2}>
  <Card title="Domains" icon="globe" href="/api-reference/domains/list" />
  <Card title="Addresses" icon="at" href="/api-reference/addresses/list" />
  <Card title="Endpoints" icon="webhook" href="/api-reference/endpoints/list" />
  <Card title="Emails" icon="envelope" href="/api-reference/emails/list" />
  <Card title="Threads" icon="comments" href="/api-reference/threads/get" />
  <Card title="Attachments" icon="paperclip" href="/api-reference/attachments/download" />
</CardGroup>