OAuth 2.0 Client Credentials Authentication
The Moverse Remote Control API enforces strict 256-bit Bearer Token security for all local studio workstation actions, multi-view camera calibrations, and cloud motion synthesis jobs. Enterprise clients and automated scripts authenticate using the OAuth 2.0 Client Credentials Flow.
Authentication Header Requirement
Authorization: Bearer <YOUR_API_BEARER_TOKEN>
Bearer tokens can be provisioned directly from portal.moverse.ai or exchanged dynamically via POST /api/v1/oauth/token.
Token Exchange Payload (POST /api/v1/oauth/token)
| Field Name | Type | Requirement | Description & Constraints | Example |
|---|---|---|---|---|
| grant_type | string | REQUIRED | Must be set to 'client_credentials' | "client_credentials" |
| client_id | string | REQUIRED | Studio Application Client Identifier | "mov_client_99a8b7" |
| client_secret | string | REQUIRED | 256-bit Secret Key generated in portal | "sec_88x99z00a11b22" |
| scope | string | OPTIONAL | Requested access scopes (studio:write, mocap:read) | "studio:write" |