# Overview

The affiliate API enables you to integrate a one-click setup process for Tebex within your server management panel. A one-click setup process has the following benefits:

* Removes the complexity of your customers installing the Tebex Plugin
* Increases conversions which will result in more commission paid into your affiliate account.
* You will receive a percentage of any revenue the server earns from their players.

### Integration Example

1. Your customers click Install Tebex within your server management panel.
2. You send an API request to Tebex alerting us of the customers request.
3. We send an email to the customer with a link that allows them to create a webstore.
4. Once the customer has created a webstore we will send you a webhook that contains a download url of the plugin, along with a pre-made plugin config file that includes the customers authentication details (their secret key).
5. You install the provided plugin along with its config file and restart your customers game server.

A typical integration of this API will take a few hours depending on the experience of your development team.

### Requirements

Please note that the one-click setup process is only available to approved partners of the Tebex Checkout For Server Hosts program. Please [**contact**](https://www.tebex.io/contact) us for any additional questions or application information.

Once your application has been approved, your API key can be found towards the bottom of the [Settings page](https://affiliate.tebex.io/settings).

To ensure you receive JSON responses, please provide an `Accept: application/json` header with all API requests.


---

# Agent Instructions: 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:

```
GET https://docs.tebex.io/developers/affiliate-api/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.