> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/archived-tokenization-api-2.0/getting-started.md).

# Getting Started

## <mark style="color:purple;">Step 1: Get your credentials</mark>

Before you start integrating, your merchant support engineer will need to generate a Partner ID, a Partner Secret Key, and an X-API-Key for you to be able to authenticate in each environment (staging and production). You can also get your unique apiKey from our portal on the “API keys” page. By already using our other services (Codapay), you’ll be able to use the same apiKey you use for Codapay.

To get these credentials for each environment, you need to send the information below to your support engineer:

1. The IP Address(es) you will be using to make API calls, so that we can allow them.
2. The URL you will be using to receive the Charge notifications.
3. You will also need to provide a redirect URL. This is the URL Payment channels will redirect your users to after the account linking is successful.

## <mark style="color:purple;">Step 2: Learn about authentication</mark>

Check out the [authentication section](/codapay/archived-tokenization-api-2.0/security-and-authentication.md) to learn about how to use credentials to authenticate a request.

## <mark style="color:purple;">Step 3: Go through the Codapay Integration guides and make a test payment</mark>

[Learn about the flow and how to make a charge](/codapay/archived-tokenization-api-2.0/business-use-cases.md) for any payment methods we have partnered with.

## <mark style="color:purple;">Support</mark>

For any support or questions that are not addressed in this document, you can reach out to your support engineer who will be able to help you.


---

# 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.coda.co/codapay/archived-tokenization-api-2.0/getting-started.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.