What authentication does the Docurex API use?

The Docurex API accepts a bearer token in the Authorization header, which uses the JWT format, and also supports an OAuth 2.0 flow, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I generate a download link with the Docurex API?

Yes. The Docurex API generates one-click download links for a document and sends them to recipients, and you can list and update the links you own. It also downloads documents directly and exports folders as zip files.

What are the rate limits for the Docurex API?

The OpenAPI spec does not specify rate limits for the Docurex API. Check the provider's documentation at https://docurex.com for the current limits that apply to your account.

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

Yes. Document and folder ids travel in the URL path, so a rule can pin your agent to specific folders or documents. Write a rule that allows only the read and download operations, so the agent can retrieve and share documents while deletion of documents, folders, and users stays out unless you add it, and every call it makes is logged.

How do I upload and share a document with the Docurex API through Jentic?

Search Jentic for 'upload a document to a data room' and it returns the matching Docurex operation with its input schema. Import the Docurex API from the Jentic API Directory, store your token once, and your agent can upload a file, place it in a folder, and generate a download link without hand-wiring the token on each request.

Is there a Docurex API MCP server?

You don't need an MCP server to give your agent the Docurex API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the document, folder, and link operations. Nothing extra loads into the agent's context until an operation is actually used.