> 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/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/configure-sdk.md).

# Configure SDK

After importing the SDK, you’ll need to configure it with your project credentials.

### Step 1: **Open configuration file**

You can open configuration file either from **Coda Menu** or **Selecting a file via Project tab**

* **Coda Menu**: From the top menu bar in Unity, go to `Coda → Select Config` 
* Selecting a file via **Project Tab**: Navigate through the Project Tab in Unity, go to `Assets → Plugins → Coda → Resources -> CodaConfig.asset`

### **Step 2:** Enter API credentials

* Get in touch with the Coda team to get your API Key, Secret Key, and Partner Id.
* Get your Codapay API Key and Codapay Project Id from the Coda Publisher Portal (**Integration -> Codapay -> API Keys**)
* Enter your project credentials into the Inspector panel. **All fields are mandatory.**

{% hint style="info" %}
You can find your project credentials in Coda Portal. You can find it under *Integration*, look for API keys.
{% endhint %}

{% hint style="warning" %}
For the internal beta testing, you have to use the credentials shared with you separately.
{% endhint %}

### Step 3: **Set environment**

* **Sandbox** – for testing purchases (no real charges)
* **Production** – for live user payments

<figure><img src="/files/R88kTLM3W91rbGhmXDC3" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="warning" %}
For the internal beta testing, set Environment to QA.
{% endhint %}


---

# 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/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/configure-sdk.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.