> For the complete documentation index, see [llms.txt](https://docs.neobanc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neobanc.com/authentication.md).

# Authentication

All API requests are authenticated with a Bearer token:

```
Authorization: Bearer nbapi_<64 hex characters>
```

## Getting a token

Create and manage tokens in your [API Partner Dashboard](https://app.neobanc.com/api-dashboard/api-keys). The token value is shown once at the creation — store it securely. Tokens can be deactivated and reactivated at any time without being deleted, and each token carries its own set of permission scopes.

Sandbox and production use separate tokens, issued from the respective dashboards (`sandbox.neobanc.com` and `app.neobanc.com`).

## Permissions

Each endpoint requires a specific permission scope on the calling token. If a token lacks the required scope, the request is rejected with `401`.

| Permission                           | Grants access to                                                              |
| ------------------------------------ | ----------------------------------------------------------------------------- |
| `public_api:payment_create`          | `POST /create-payment`                                                        |
| `public:credit_card_payment`         | `POST /create-credit-card-payment`, `PATCH /update-payment`                   |
| `public_api:payments_read`           | `POST /payment-history`                                                       |
| `public_api:payees_read`             | `POST /payees/search`, `POST /payees/validate-account`                        |
| `public_api:bank_accounts_manage`    | `POST /bank-accounts`, `GET /bank-accounts`, `POST /bank-accounts/deactivate` |
| `public_api:past_rent_report_create` | `POST /past-rent-reports`                                                     |

Scopes are assigned per token in the dashboard, so you can issue narrowly-scoped tokens — for example, a read-only token for a reporting service.

## Webhook signing secret

Webhook deliveries are authenticated in the opposite direction — Neobanc signs the requests it sends to you with a separate `whsec_...` signing secret. See [Webhooks](/api-reference/webhooks.md) for the verification guide. Your API token is never included in webhook requests.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neobanc.com/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.