# Hosted Authorization

> Coming soon, upon request — this feature is turned on for your tenant by the Aurea team. [Contact us](https://www.aureahub.com/contact)

Whether Aurea keeps the user's authorization at the bank ramp in one environment, and whether its last use failed.

## Overview

- `connected`: an authorization is kept; `customerId`: the customer it reads; `connectedAt`: when it was given.
- `lastError`: the code its last use failed with, or `null`. `BANK_RAMP_AUTHORIZATION_EXPIRED` means the bank ramp ended it: the user authorizes again ([Start Hosted Onboarding](https://docs.aureahub.com/docs/bank-customer-authorize.md)).
- Answers whatever your tenant's settings; `403` to a token without a tenant.

## Endpoint

### `GET /v1/ramp/bank/customer/authorize`

Authentication: bearer token required.

Says whether the user's hosted authorization is kept.

**Query parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `isTestnet` | boolean | no | `true` for the sandbox; `false` or omitted for production |

**Responses**

`200` Kept

```json
{
  "environment": "sandbox",
  "connected": true,
  "customerId": "5a9d3c71-2e4f-4b86-9c0a-7d1e3f5b8a24",
  "lastError": null,
  "connectedAt": "2026-10-14T10:12:00.000Z"
}
```

`200` None

```json
{
  "environment": "sandbox",
  "connected": false,
  "customerId": null,
  "lastError": null,
  "connectedAt": null
}
```

---

Web version: https://docs.aureahub.com/#bank-customer-authorization