canonical: https://jentic.com/apis/rossum.ai/rossum

# Rossum Document Processing API

Rossum AI-powered document processing API for automated data extraction from invoices, receipts, and other documents. Provides intelligent document capture, classification, and data validation capabilities. The API exposes 22 endpoints secured with bearer authentication.

## For AI agents

Programmatically user login, exchange jwt token. Covers 22 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- User Login
- Exchange JWT Token
- List Organizations
- Get Organization
- Create Workspace

## Use cases

### Payments Operations

Use the Rossum Document Processing API to perform payments operations programmatically. The API provides 22 endpoints covering core functionality including user login, exchange jwt token, list organizations.

Example prompt: Call POST /v1/auth/login to user login

### Automated Authentication Management

Automate authentication operations by combining multiple Rossum Document Processing API endpoints. Agents can exchange jwt token and then list organizations in a single workflow.

Example prompt: Call POST /v1/auth/token to exchange jwt token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rossum Document Processing API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'user login', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/auth/login | User Login |
| POST | /v1/auth/token | Exchange JWT Token |
| GET | /v1/organizations | List Organizations |
| GET | /v1/organizations/{id} | Get Organization |
| POST | /v1/workspaces | Create Workspace |
| GET | /v1/workspaces | List Workspaces |
| GET | /v1/workspaces/{id} | Get Workspace |
| PATCH | /v1/workspaces/{id} | Update Workspace |

## Key resources

- **Authentication** — User authentication and token management
- **Organizations** — Organization management
- **Workspaces** — Workspace operations
- **Queues** — Document processing queues
- **Schemas** — Document schema definitions

## Why Jentic

- **Setup:** Wiring the Rossum Document Processing API by hand means holding its bearer token, pointing at your organization's subdomain host ({domain}.rossum.app), and handling the request plumbing yourself. Through Jentic you install once, import the Rossum Document Processing API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Rossum puts ids like the workspace in the URL path (/workspaces/{id}), so a rule can pin your agent to reading and updating a given workspace. You choose the operations it may call, so writes like creating workspaces are not included unless you add them.
- **Credential handling:** Your Rossum token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list organizations' or 'update a workspace', and Jentic returns the matching Rossum operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Rossum Document Processing API use?

The Rossum Document Processing API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I user login with the Rossum Document Processing API?

Yes. Use the POST /v1/auth/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rossum Document Processing API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I user login through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'user login'. Jentic returns the matching Rossum Document Processing API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rossum Document Processing API have?

The Rossum Document Processing API exposes 22 endpoints covering authentication, organizations, workspaces operations.

### Can I limit what my agent is allowed to do with the Rossum Document Processing API?

Yes. Jentic One is self-hosted, so your own rules decide which Rossum operations and credentials the agent may use. Because Rossum puts ids like the workspace in the URL path (/v1/workspaces/{id}), you can pin the agent to reading and updating a specific workspace while excluding write operations such as POST /v1/workspaces for creating new ones. You choose the exact operations it can call, so anything you do not grant stays off limits.