Provisioning

Device provisioning and activation

Get provision token

post

Generate a provision token for device activation

Required permissions, when user-scoped authentication is used: PROVISION_DEVICES. User-scoped tokens that set ownerId different from authenticated user ID also require ORG_VIEW_USERS.

Authorizations

bearerAuth

AuthorizationstringRequired

OAuth2 Bearer token obtained from authentication endpoint

Body

application/json

orgIdinteger · int32Required

Organization ID, in which device should be created.

Example: 101

ownerIdinteger · int64Required

User ID, to which device will be assigned.

Example: 101

Responses

200

Provision token

application/json

tokenstringRequired

Provision token value

Example: gSNIYf9l7vdaLEMWK0jRCHT9RKe5rDSO

deviceIdinteger · int32Required

ID of the device created with this token

Example: 101

400

Bad request

application/json

403

Forbidden

404

Organization/user not found or access denied

application/json

429

Too many requests

500

Internal server error

application/json

post

/api/v1/organization/device/provision/token

HTTPcURLJavaScriptPython

POST /api/v1/organization/device/provision/token HTTP/1.1
Host: blynk.cloud
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 27

{
  "orgId": 101,
  "ownerId": 101
}

{
  "token": "gSNIYf9l7vdaLEMWK0jRCHT9RKe5rDSO",
  "deviceId": 101
}