Overview
Client-mode REST API connectors for Blynk.Cloud: read and write device datastreams, upload timestamped data, raise events and manage devices, templates, webhooks and automations from MQTT, plus an opt-in webhook receiver. This is one of the templates in the Blynk REST API app (blynk). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Blynk device auth token or OAuth2 client on the factory box; the ready gate needs an authenticated live GET + POST (or broker MQTT round-trip).
Auth
Device connector: device auth token in the query string token={value.json.token} (Blynk has no header form for the Device HTTPS API); suggested secret BLYNK_DEVICE_TOKEN. Platform connector: OAuth2 client credentials (Developers > OAuth2) as HTTP Basic {value.json.basic_auth} on GetAccessToken / RefreshAccessToken, then Authorization: Bearer {value.json.access_token}; suggested secrets BLYNK_CLIENT_BASIC, BLYNK_ACCESS_TOKEN. Platform API needs a Prototype / Production / Enterprise plan. Never commit real tokens.Template parameters
BASE_ADDRESS default: https://fra1.blynk.cloud.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallIsDeviceConnected by publishing a JSON payload to its request topic, and read the reply on the response topic:

