Skip to main content
POST
Connect an app

Authorizations

Authorization
string
header
required

An API key from your Devic console, sent as Authorization: Bearer <key>. An embedded front end sends a tenant-session token instead, so no API key reaches the browser, and an OAuth integration sends its access token. Missing, invalid or expired credentials get a 401. See Authentication.

Headers

X-Devic-User
string

Only with an API key: the userUID or email of a person of the key's account to act as, with that person's permissions. Without it, an API key acts as the account integration ("API"), which sees shared workspaces only. A person's token cannot name someone else.

Path Parameters

wid
string
required

Workspace id (home workspace of the automation)

Body

application/json
integration
string
required

App slug

scope
enum<string>
required
Available options:
workspace,
user
name
string

Label for this account

authScheme
string

Authentication method when the app offers several

Response

Success — wrapped as { success: true, data }