Authentication
Artos API requests use an Okta-issued access-token JWT. Include the token as a Bearer token:Get an Okta access token
Sign in through your organization’s Okta application and request an access token for the Artos API. The exact sign-in experience depends on your organization’s Okta application and OAuth/OIDC configuration. Do not use an ID token as the API credential. Send the access token issued for the Artos API.Make an API request
Token requirements
The access token must:- Be issued by your organization’s Okta authorization server.
- Be intended for the Artos API.
- Be valid and unexpired.
- Identify a user who has access to the requested Artos organization and resource.
File access
File listings return an opaqueresource_id. They do not return S3 URLs. Source-file viewers use POST /source-file, which authorizes the source-file resource with the user’s Bearer token on every request:
POST /document-file-session with the same Bearer token:
Authorization header—not in the URL:
/open-document?session_token=... is not a valid ordinary download flow. The query form is reserved for the OnlyOffice server-to-server integration, which also requires a separately signed OnlyOffice request JWT.