> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/online-payments/api-integration-methods-auth-and-endpoints/api-authentication.md).

# API authentication

Verifone is offering API Key authentication to help merchants maintain long-lasting integrations efficiently. 

The Verifone API Keys use both HTTP Basic Authentication and Bearer Authentication methods. 

{% hint style="warning" %}
**Important!** To process transactions through the [sandbox and production environments](/online-payments/api-integration-methods-auth-and-endpoints/integration-methods-and-environment-endpoints.md#sandbox-and-production-urls), you will be using different API keys. One key is used for sandbox, and one is used for production. Make sure your API key and secret are never stored on the client’s side; they are only intended for Server-to-Server API calls.
{% endhint %}

## Availability <a href="#availability" id="availability"></a>

To create an API key, your Verifone Central account must have one of the following roles:&#x20;

* Merchant Admin
* Merchant Supervisor

## :key: Authentication methods <a href="#authentication-methods" id="authentication-methods"></a>

There are two authentication methods provided by Verifone that can be used within the REST API calls:

<a href="/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/basicauth.md" class="button primary">Basic authentication</a>

<a href="/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/bearerauth-jwt.md" class="button primary">Bearer authentication</a>&#x20;


---

# 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.verifone.com/online-payments/api-integration-methods-auth-and-endpoints/api-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.