> 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/coda-webstore/web-store-integration-guides/getting-started-with-integration.md).

# Getting Started with Integration

## Step 1: Click on the ‘Integration’ tab from the side menu and select ‘Distribution’

<figure><img src="/files/Jrkh6a81mCbGyscR7Pk4" alt="" width="240"><figcaption></figcaption></figure>

## Step 2: Click on Submit New API Request

<figure><img src="/files/ga9YLartarg6OPFWGQJk" alt=""><figcaption></figcaption></figure>

## Step 3: Submit Title details

Select <mark style="color:purple;">**Title**</mark> from the dropdown menu.

<figure><img src="/files/tp6hxHf4WjF5LPnbEoK0" alt=""><figcaption><p>API credentials submission form</p></figcaption></figure>

## Step 4: Submit API Credentials

Enter all the required fields in the API credential form and Submit.

1. [Validate API](/codashop-and-distribution/integration-guides/validation-api-request.md)
2. [Top-Up API](/codashop-and-distribution/integration-guides/top-up-api-request.md)
3. <mark style="color:purple;">**Secret Key:**</mark> The partner defines this value and shares it with Coda. It is recommended that the length of the secret key not exceed 64 characters.
4. <mark style="color:purple;">**Service Provider:**</mark> Service Provider can be used in cases where there are different apps using the same API. If not used, the default value used should be “Coda”.
5. <mark style="color:purple;">**Merchant Transaction ID:**</mark> Partner's order ID in validating response. (*Optional*)
6. <mark style="color:purple;">**Role ID:**</mark> The role ID/character ID of this user account. If the Validate API response includes roleList, it is required.
7. [Serverlist API](/codashop-and-distribution/integration-guides/fetch-server-list-request-optional.md) (*Optional*)

<figure><img src="/files/ztx7hIHY2Z3drIw8MTM5" alt=""><figcaption></figcaption></figure>

## Step 5: Submission 'Under Review'

Once you successfully enter all the relevant fields and submit the API credential data, the submission will be <mark style="color:purple;">**Under Review.**</mark>

<figure><img src="/files/jHXnqGhqzMRuCtiuGLjI" alt=""><figcaption><p>API Submission 'Under review' status</p></figcaption></figure>

## Step 6: Submission 'Rejected'

If the Submission is rejected, the status will change to <mark style="color:purple;">**Rejected**</mark> and you need to re-submit by making the appropriate changes.

<figure><img src="/files/IKcvO4u4Jgob3k9V63Sc" alt=""><figcaption><p>API Submission 'Rejected' status</p></figcaption></figure>

Make all the necessary corrections/edits and re-submit the API for verification.

<figure><img src="/files/zuwQ8hQC99YASfvret4B" alt=""><figcaption></figcaption></figure>

## Step 7: API Submission 'Verified'

Once Coda's team verifies all the details, the status of the submission changes to <mark style="color:purple;">**Verified.**</mark>

<figure><img src="/files/iO6c6YE8FLSk6z4rhBDc" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/coda-webstore/web-store-integration-guides/getting-started-with-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.