> 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` | Successful request and data was returned |
| `400` | Part of the request is malformed; the exact reason can be found in the response |
| `401` | The request is not authenticated |
| `403` | Unauthorized request to access data from an ineligible plan |
| `404` | This recond is not found. It could be that the data you're trying to access is deleted due to rescheduling. |
| `429` | You have reached the response rate limit of your plan |
| `500` | Internal error with our servers |
---
# 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://docsv3.sportsapi360.com/getting-started.md?ask=&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.