> For the complete documentation index, see [llms.txt](https://connect.socios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connect.socios.com/partner-api/prerequisites.md).

# Prerequisites

Before you get started...

Prior to working on integrating the Socios.com API into your project, there are a few requirements to address.&#x20;

Here's a checklist to help you get started.

## **1. Get Your Free Access**

{% hint style="info" %}
We advise you to reach out to your account manager or key point of contact at Socios.com. \
They will guide you through the process of getting your access to the Socios.com API Manager tool.&#x20;
{% endhint %}

To obtain your Socios.com API access:

1. Access the [Chiliz Help Centre](https://mediarex.atlassian.net/servicedesk/customer/portal/5).
   1. Submit your email to create an account on the platform.

      <figure><img src="https://31329255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMDcaoJLMj5Y3jzFMTONF%2Fuploads%2FB81ginkPWuA37ONm5frf%2Fimage.png?alt=media&amp;token=cc01d7d7-d948-4bf9-9fb3-b52991f22103" alt="" width="375"><figcaption></figcaption></figure>

      *If you already have an Atlassian account, click "Continue with Atlassian account".*
   2. Choose either "Companies" or "Individuals", depending on your situation.

      <figure><img src="https://31329255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMDcaoJLMj5Y3jzFMTONF%2Fuploads%2FaATYTW4wq9mhI7dwTgw2%2Fimage.png?alt=media&amp;token=510e5204-7d94-44e5-b953-40debe75b6fd" alt="" width="563"><figcaption></figcaption></figure>
2. Click on "Complete API Due Diligence" and fill in the form.
3. Click on "API Terms & Conditions" and fill in the form.&#x20;

The Socios.com team will contact you shortly.

## **2. Create Your Application**

Once you have your API access, you need to create a new OAuth 2.0 application in your API settings. You can do this by visiting the [Socios.com Developer Portal](https://partner.socios.com/devportal/apis). Log in, navigate to your API settings, and create a new application. See our [Quick Start](/partner-api/quick-start.md) for more.

{% hint style="danger" %}
Make sure to use our production environment since the sandbox is under construction.
{% endhint %}

## **3. Familiarise Yourself With Our URLs**

You should be aware of the following URLs to smoothly operate with the Socios.com  API:

* **API Base URL**\
  [https://api-public.socios.com](<https://api-public.socios.com >) \
  This is the base URL that you'll use to interact with our APIs.
* **Authorisation URL**\
  [https://partner.socios.com/oauth2/authorize ](<https://partner.socios.com/oauth2/authorize >)\
  This is the URL used for authorising your application with OAuth2.&#x20;
* **Access Token URL**\
  [https://partner.socios.com/oauth2/token ](<https://partner.socios.com/oauth2/token >)\
  This is the URL to use when requesting an access token. \
  The access token is used to authorise your API requests.
* **Revoke Token URL**\
  [https://partner.socios.com/oauth2/revoke ](<https://partner.socios.com/oauth2/revoke >)\
  This is the URL to use when needing to revoke your token, for any reason.

With these prerequisites in place, you should be ready to begin using the Socios.com API. If you have any questions or need any further information, feel free to reach out to your point of contact.


---

# 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://connect.socios.com/partner-api/prerequisites.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.
