> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.cloud/platform-https-api.md).

# Platform API

The Platform API provides comprehensive access to all features of the Blynk IoT Platform through a secure HTTPS API. It enables you to perform Create, Read, Update, and Delete (CRUD) operations on a wide range of entities. These entities include devices, users, organizations, automations, webhooks, tags, templates, and more, giving you extensive control and flexibility.

{% hint style="info" %}
Platform API is available to Prototype, Production, and [Enterprise Plan](https://blynk.io/iot-platform-for-business) clients. If you're interested in utilizing this API for your business needs, consider upgrading. If you are already an Enterprise Plan customer, please reach out to your Account Manager.
{% endhint %}

### Authentication

The API uses OAuth2 for authentication. Obtain an access token via the `POST /oauth2/token` endpoint using your OAuth2 client credentials, then include it as a Bearer token in the `Authorization` header of every API request:

```
Authorization: Bearer {access_token}
```

See the [**Authentication**](broken://pages/f8e96e44e05b776f5094809b107bb591bd994393) section for the available grant types and detailed usage.

### Rate Limiting

The API enforces rate limiting of **10,000 requests per minute** per organization. Exceeding this limit returns a `429 Too Many Requests` response.

### Pagination

List endpoints support pagination via `page` (0-indexed) and `size` (max 1000) query parameters.

### Parameter Passing

All resource identifiers (deviceId, organizationId, userId, templateId, etc.) are passed as **query parameters**.


---

# 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://docs.blynk.io/en/blynk.cloud/platform-https-api.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.