# 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 exclusively available to[ 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 Launch Support Engineer.&#x20;
{% 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**](/en/blynk.cloud/platform-https-api/authentication.md) 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: 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.blynk.io/en/blynk.cloud/platform-https-api.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.
