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

# Getting Started

Welcome aboard! This section will guide you through the steps to quickly start using **SportsAPI360’s powerful sports data APIs**.

Whether you're building an app for live cricket scores, a football results tracker, or a sports analytics dashboard, we make it easy for you to integrate real-time and historical data.

#### ✅ Step 1: Sign Up

Go to [sportsapi360.com](https://sportsapi360.com/) and create a free developer account.\
You'll get access to your dashboard, where you can manage your subscription, usage, and API keys.

***

#### 🔐 Step 2: Get Your API Key

Once logged in, go to your **Dashboard > App > API Key** section.\
This unique key identifies your account and must be included in all API requests.

* Your key looks like this: `api_key=YOUR_API_KEY_HERE`
* Keep it secure and don’t expose it in the frontend code.

{% hint style="info" %}
The Api Key has no expiration date and will remain valid until you manually delete it yourself.
{% endhint %}

***

#### 📦 Step 3: Choose a Subscription Plan

We offer flexible pricing plans for developers, startups, and enterprises.

Visit the Pricing Page for full details.

***

API utilizes response codes to indicate successful and failed API requests.

When making a request, a code response will always be returned. See below for a short list of possible code responses:

|       |                                                                                                                        |
| ----- | ---------------------------------------------------------------------------------------------------------------------- |
| `200` | <sub>Successful request and data was returned</sub>                                                                    |
| `400` | <sub>Part of the request is malformed; the exact reason can be found in the response</sub>                             |
| `401` | <sub>The request is not authenticated</sub>                                                                            |
| `403` | <sub>Unauthorized request to access data from an ineligible plan</sub>                                                 |
| `404` | <sub>This recond is not found. It could be that the data you're trying to access is deleted due to rescheduling.</sub> |
| `429` | <sub>You have reached the response rate limit of your plan</sub>                                                       |
| `500` | <sub>Internal error with our servers</sub>                                                                             |


---

# 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://docsv3.sportsapi360.com/getting-started.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.