API and OAuth

The method and parameter reference is at dev.streamvi.io. Follow the contract of the selected method. Application settings are under For developers → application → Settings.

Prepare an application

Create an integration, select its required permissions and configure allowed OAuth redirect URLs. The client ID and secret key are available in settings. Keep the secret and issued tokens out of public code and documentation.

The application starts authorization. In the Cabinet, the user selects an available project and clicks Continue, then reviews the requested permissions and allows or declines access. With a project supplied in the request, consent may appear immediately. Issued access is tied to the selected project and permissions.

When the request supplies no separate permission list, the Cabinet uses the application's configured permissions. Requests outside the application's allowed set are blocked. Authorization does not continue if permissions fail to load or the project is unavailable.

Check an integration

First verify reading accessible data in the intended project. Before a write request, separately check that the user granted the corresponding capability. Selecting the OAuth type alone does not grant permission to change or delete data.

On error, check the application ID, redirect URI, selected project and permissions. State and PKCE parameters, when used, are also checked during authorization; consult the API reference for exact requirements and code exchange. An incoming stream key is not an API token.

Configure webhooks for incoming application events. See connecting a plugin to check the consent flow.