The oauth app object

⚠️
Preview — this feature is being built; the design below is the spec.

The oauth_app object as the API returns it. Every field below appears in every response that returns this object; fields with no value are null rather than missing.

Example

{
  "id": "oapp_01JD79H1K3M5P7R9T1V3",
  "type": "oauth_app",
  "client_id": "oapp_01JD79H1K3M5P7R9T1V3",
  "name": "Acme Notes",
  "client_type": "confidential",
  "redirect_uris": [
    "https://notes.example.com/oauth/callback"
  ],
  "allowed_scopes": [
    "user:profile",
    "user:inference"
  ],
  "audience": "organization",
  "logo_url": "https://notes.example.com/logo.png",
  "status": "active",
  "created_at": "2026-11-05T10:00:00Z",
  "client_secret": "scs_live_Hn2…redacted"
}

Fields

FieldTypeDescription
idstringUnique id of this object.
typestringThe object type, always oauth_app.
client_idstringSee the endpoint pages below.
namestringName shown in the Console and in reports.
client_typestringpublic (no secret; PKCE required) for desktop, mobile and browser apps, or confidential (has a secret; PKCE still required) for server-side apps.
redirect_urisarrayExact HTTPS addresses. Loopback http://127.0.0.1 with any port is allowed for public desktop clients.
allowed_scopesarrayThe most the app can ask for. user:inference lets it call /v1 billed to the signing-in person’s organization.
audiencestringorganization: only your members can sign in. any: any Syntic user can, after Syntic reviews the app.
logo_urlstringSee the endpoint pages below.
statusstringCurrent state; see the values on the endpoint pages.
created_atstringWhen it was created, RFC 3339 UTC (some older objects use Unix seconds).
client_secretstringConfidential apps only; returned once.

Returned by

Was this page helpful?