# routes.get

Get email route details.

Returns routing configuration, destination, and webhook tap settings for a specific email address.

```ts
openemail.routes.get(address: string, options?: CallOptions): ApiPromise<Route>
```

It calls `GET /routes/{address}`: [Get email route details](/docs/api/routing/get_RouteGet) in the API reference.

## Example

```ts
const route = await openemail.routes.get(address)
```

## Arguments

| Argument | Type | Description |
| --- | --- | --- |
| `address` | `string` | Full email address (e.g. 'info@example.com'). The path's `{address}`. |

## Options

It takes no options of its own. Every call also takes `signal`, `timeout`, `retry` and `headers`, which say how that one call is sent ([call options](/docs/sdks/typescript/calling-methods#call-options)).

## Answer

Awaited, it is the API's JSON, [`Route`](/docs/sdks/typescript/types/route). It is an [`ApiPromise`](/docs/sdks/typescript/responses): `.withResponse()` gives the same with the `Response` it came in, for its headers.

## Errors

| Status | What it means |
| --- | --- |
| `401` | unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a `WWW-Authenticate: Bearer` challenge |
| `404` | Route not found or not accessible to this principal |
| `503` | temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description) |

A failed call rejects with a [`RequestError`](/docs/sdks/typescript/errors): its `status`, and its `code`, the API's `error`. Decide on the code: one status covers several.

## Types

It names these types of the API, each on a page of its own: [`Route`](/docs/sdks/typescript/types/route).
