API
Sso
Botyard REST API endpoints for sso.
16 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.
- Get Sso Availability:
GET /v1/orgs/{org_id}/sso/availability - List Sso Connections:
GET /v1/orgs/{org_id}/sso/connections - Create Sso Connections:
POST /v1/orgs/{org_id}/sso/connections - Update Sso Connections:
PATCH /v1/orgs/{org_id}/sso/connections - Delete Sso Connections:
DELETE /v1/orgs/{org_id}/sso/connections - List Scim Connections:
GET /v1/orgs/{org_id}/scim/connections - Create Scim Connections:
POST /v1/orgs/{org_id}/scim/connections - Update Scim Connections:
PATCH /v1/orgs/{org_id}/scim/connections - Rotate Scim Tokens:
POST /v1/orgs/{org_id}/scim/connections/rotate-tokens - Revoke Scim Connections:
POST /v1/orgs/{org_id}/scim/connections/revoke - List Scim Groups:
GET /v1/orgs/{org_id}/scim/groups - List Group Role Mappings:
GET /v1/orgs/{org_id}/scim/group-role-mappings - Delete Group Role Mappings:
DELETE /v1/orgs/{org_id}/scim/group-role-mappings - Upsert Group Role Mappings:
PUT /v1/orgs/{org_id}/scim/group-role-mappings - Get Sign In Policy:
GET /v1/orgs/{org_id}/sign-in-policy - Update Sign In Policy:
PATCH /v1/orgs/{org_id}/sign-in-policy
Spend Top Conversations
Conversations by spend; a purged one keeps its cost. A conversation's title and bot are shown only if the caller passes the very guard that gates reading its metadata (``require_conversation_read_access``: scope, owner and the bot's usability). Any other conversation keeps its cost and is returned as ``private_conversation``. The guard runs once per listed conversation, so at most ``limit`` times, each a primary-key read plus the cached bot-access check.
Get Sso Availability
Whether SSO self-service is on for this org, and what its plan includes.