Admin/Start Connector Onboarding
POST /v1/admin/connectors/onboarding

Start Connector Onboarding

Begin embedded signup through the chosen provider. Core asks nexus for the provider's signup URL + a server-side `state` nonce (no secrets touch core) and relays nexus's descriptor verbatim. The shape is provider-type specific — Meta carries `app_id`/`config_id`/ `api_version`; other providers carry their own fields. The browser opens the URL and posts the resulting `code` back to the complete step.

Base URL https://api.{cluster}.{platform}.voiger.io
Request · cURL
curl -X POST https://api.{cluster}.{platform}.voiger.io/v1/admin/connectors/onboarding \
  -H "Cookie: sid=$VOIGER_SESSION" \
  -H "x-workspace-code: your-workspace-code" \
  -H "x-csrf-token: $CSRF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "provider_id": "6d1f2a3b-4c5d-6e7f-8091-a2b3c4d5e6f7"
     }'

Parameters

x-workspace-code string required in header
x-csrf-token string required in header

Response

state
string
provider_type
string
data
object Provider-specific signup fields. URL-based providers (e.g. Meta) carry `onboarding_url` here plus their config (`app_id`, `config_id`, `api_version`); non-URL providers carry their own fields instead.