Authenticate the Provider API

Provider API manages the provider account’s catalog and pricing. Create its credentials in Provider Settings. These credentials are separate from inference API keys and from tokens created for an individual device.

Create access#

1. Select the workspace that owns the provider in Console.
2. Open the provider’s settings and enable Remote Access.
3. Create a named provider access token and save the secret securely.
4. Use the provider UUID as the HTTP Basic username and the token as its password.

curl --fail-with-body --request GET \
  "https://api.shareai.now/api/v1/console/provider" \
  -u "$PROVIDER_UUID:$PROVIDER_ACCESS_TOKEN"

import json
import os
import urllib.request
import base64

credentials = os.environ["PROVIDER_UUID"] + ":" + os.environ["PROVIDER_ACCESS_TOKEN"]
headers = {"Authorization": "Basic " + base64.b64encode(credentials.encode()).decode()}
request = urllib.request.Request('https://api.shareai.now/api/v1/console/provider', headers=headers, method='GET')
with urllib.request.urlopen(request, timeout=60) as response:
    print(json.load(response))

const url = "https://api.shareai.now/api/v1/console/provider";
const credentials = `${process.env.PROVIDER_UUID}:${process.env.PROVIDER_ACCESS_TOKEN}`;
const headers: Record = {
  Authorization: `Basic ${Buffer.from(credentials).toString("base64")}`,
};
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
console.log(await response.json());

Named scopes#

Scopes are checked for the route and HTTP method. The currently issued provider token exposes its configured scopes; a token never grants ownership of a different provider. Keep the enabled state and token status in mind when diagnosing a 403 response.

Device control is another layer#

Starting or stopping a device requires a token created for that device relationship. Enabling Provider Remote Access is a prerequisite, but a provider catalog token alone is not a device-control credential. Continue with Device API authentication.

Revoke access#

Revoke a token when an automation stops needing it. Deleting or revoking one integration’s token lets you retire that integration without replacing unrelated tokens. Turning Remote Access off disables this provider’s remote access path.