> 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.md).

# API Integration methods, auth & endpoints

API Integration Basics: Methods, Authentication & Endpoints

Use this section to choose your environment, set up authentication, and collect the credentials required for API requests.

## Start here

Use the guide that matches the task in front of you:

* Need base URLs and environment details? Start with [Integration methods and environment endpoints](/online-payments/api-integration-methods-auth-and-endpoints/integration-methods-and-environment-endpoints.md).
* Need to understand how Verifone authenticates API calls? Go to [API authentication](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication.md).
* Need to create or manage credentials in Verifone Central? Use [Get your API Keys](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/get-your-api-keys.md) and [Manage your API Keys](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/manage-your-api-keys.md).
* Need the request header format for a specific auth scheme? Jump to [BasicAuth](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/basicauth.md) or [BearerAuth (JWT)](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/bearerauth-jwt.md).

### What you need before making requests

* Access to your Verifone account and the correct environment.
* The authentication method required by the API you are calling.
* Credentials created and stored securely before you send live traffic.

{% hint style="info" %}
The required authentication method depends on the API and flow you use. Confirm the auth scheme before building your request headers.
{% endhint %}

### Recommended order

1. Confirm whether you are working in test or production.
2. Create or collect the required credentials.
3. Apply the correct authentication header.
4. Move on to your payment or wallet integration flow.

{% content-ref url="/pages/4IWkYHr68OyWCGDPNJ6l" %}
[Integration methods and environment endpoints](/online-payments/api-integration-methods-auth-and-endpoints/integration-methods-and-environment-endpoints.md)
{% endcontent-ref %}

{% content-ref url="/pages/p8mnNem5zUF0ZaFIDn0p" %}
[API authentication](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication.md)
{% endcontent-ref %}

{% columns %}
{% column width="58.333333333333336%" %}
{% content-ref url="/pages/420e88d3fb8138dbadd8deca7cdec031f0e3b681" %}
[Get your API Keys](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/get-your-api-keys.md)
{% endcontent-ref %}

{% content-ref url="/pages/AbpiMhraex6bMbC5QsvP" %}
[Manage your API Keys](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/manage-your-api-keys.md)
{% endcontent-ref %}
{% endcolumn %}

{% column width="41.666666666666664%" %}
{% content-ref url="/pages/RO4zsRgh84XA56V4pKWS" %}
[BasicAuth](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/basicauth.md)
{% endcontent-ref %}

{% content-ref url="/pages/ipaeqGinh2n64tA7XCwL" %}
[BearerAuth (JWT)](/online-payments/api-integration-methods-auth-and-endpoints/api-authentication/authentication-methods-basic-and-bearer/bearerauth-jwt.md)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}

### Next steps

After authentication is in place, continue with the product flow you want to launch:

* [Checkout](/online-payments/checkout.md)
* [API Integration](/online-payments/api-integration.md)
* [Online Payments Getting Started](/online-payments/online-payments-getting-started.md)


---

# 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.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.