What authentication does the Onna Platform API use?

Onna uses OAuth 2.0. The integration calls POST /oauth/token to exchange credentials for an access token and then includes that token on every other call. The account must be on an Enterprise plan and the calling user must have the Developer role assigned. Through Jentic, the OAuth credential is held in the vault and injected at execution time.

How do I upload large files into Onna?

Use the tus resumable upload protocol exposed at POST /upload/{id}/tus, then PUT and PATCH the same path to stream chunks. This is the recommended path for any file larger than a few MB and is robust against network drops. POST /resources/files is used to register the file as a resource against a workspace once the upload completes.

What are the rate limits for the Onna Platform API?

Onna does not publish a global rate limit in the OpenAPI spec. The platform applies per-tenant throttling and signals it through 429 responses, so integrations should back off on Retry-After. Bulk ingestion should use tus chunking and limit parallel uploads per workspace to avoid unnecessary throttling.

How do I ingest documents into Onna through Jentic?

Install the SDK with 'pip install jentic', search for the operation with the query 'upload file to onna', then load the POST /resources/files operation, and execute it with the workspace onna_id and file metadata. Jentic handles the OAuth refresh and the tus upload sequence.

Can I attach custom metadata to ingested resources?

Yes. Define the schema with POST /customFields and PATCH /workspaces/{onna_id}/customFields/{field_id}, then set the values on each resource at ingest time. This is how compliance teams tag matter, retention class, and review status without modifying the file payload.

Can I limit what my agent is allowed to do with the Onna Platform API?

Yes. Because you run Jentic One yourself, your own rules decide which Onna operations and credentials the agent may use, so you can allow just the calls it needs, such as reading workspaces with GET /workspaces or uploading a file with POST /resources/files and the tus upload endpoints. Since Onna passes workspace, folder, and file targets in the request body rather than the URL path, you scope access at the operation level rather than by path. Operations like creating a workspace with POST /workspaces or defining metadata with POST /customFields stay excluded unless you add them to the allowed set.