> **Description:** The Access Token API enables secure authentication for all Vipps MobilePay API requests through OAuth 2.0 token generation, supporting both standard and partner authentication flows.

# Access Token API

The Access Token API exchanges your API keys for a short-lived token that you include in every subsequent request to confirm your identity.

Use your
[API keys](https://developer.vippsmobilepay.com/docs/knowledge-base/api-keys.md#what-are-api-keys) to get the access token.

```mermaid
flowchart LR
    K[" API keys"] -->|"exchange for"| T[" Access token"]
    T -->|"include in every"| R[" API request"]
```

API keys are exchanged for an access token, which must then be included in every API request.

## Choose your authentication flow

Most merchants use [standard authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/standard-authentication.md) with sales unit API keys.

Use your [sales unit API keys](https://developer.vippsmobilepay.com/docs/knowledge-base/api-keys.md#what-are-api-keys) with
[standard authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/standard-authentication.md):

*  [Main and supporting APIs](https://developer.vippsmobilepay.com/docs/APIs/README.md#main-apis)
*  [Management API](https://developer.vippsmobilepay.com/docs/APIs/management-api/README.md)
*  [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md)

Use your [sales unit API keys](https://developer.vippsmobilepay.com/docs/knowledge-base/api-keys.md#what-are-api-keys)
or [partner keys](https://developer.vippsmobilepay.com/docs/partner/partner-keys.md) with
[standard authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/standard-authentication.md):

*  [Main and supporting APIs](https://developer.vippsmobilepay.com/docs/APIs/README.md#main-apis)
*  [Management API](https://developer.vippsmobilepay.com/docs/APIs/management-api/README.md)
*  [Donations API](https://developer.vippsmobilepay.com/docs/APIs/donations-api/README.md)

Accounting keys with [specialized authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/specialized-authentication.md) and give access to one API:

* [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md)

Merchant-level keys with [specialized authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/specialized-authentication.md).

* [Donations API](https://developer.vippsmobilepay.com/docs/APIs/donations-api/api-guide.md)
* [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/report-api-quick-start.md) *(for Donations reporting)*
* [Webhooks API](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/quick-start.md) *(for Donations webhooks)*

Partner keys with [standard authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/standard-authentication.md).

**Go straight to a quick start guide**

Each API's quick start guide covers authentication as part of the setup.

## Technical details

* [Standard authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/standard-authentication.md): Authenticate with
  sales unit API keys or partner keys.
* [Specialized authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/specialized-authentication.md): Authenticate with accounting or merchant-level keys.
* [API reference](https://developer.vippsmobilepay.com/redocusaurus/access-token-swagger-id.yaml): View the token endpoint specifications.

[atx]: https://developer.vippsmobilepay.com/redocusaurus/access-token-swagger-id.yaml
[mtx]: https://developer.vippsmobilepay.com/redocusaurus/access-token-swagger-id.yaml

> **Full site overview:** For every page in this documentation, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).