canonical: https://jentic.com/apis/simplepdf.eu/simplepdf-eu

# SimplePDF API

The SimplePDF API allows you to retrieve, manage and update uploaded documents and submissions. API access is included in the PRO plan and all higher tiers: https://simplepdf.com/pricing. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically listdocuments, getdocument. Covers 7 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- listDocuments
- getDocument
- updateDocument
- deleteDocument
- listCompanyDocumentSubmissions

## Use cases

### Storage and Databases Operations

Use the SimplePDF API to perform storage operations programmatically. The API provides 7 endpoints covering core functionality including listdocuments, getdocument, updatedocument.

Example prompt: Call GET /documents to listdocuments

### Automated Documents Management

Automate documents operations by combining multiple SimplePDF API endpoints. Agents can getdocument and then updatedocument in a single workflow.

Example prompt: Call GET `/documents/{document_id}` to getdocument, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SimplePDF 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 'listdocuments', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/documents` | listDocuments |
| GET | `/documents/{document_id}` | getDocument |
| PATCH | `/documents/{document_id}` | updateDocument |
| DELETE | `/documents/{document_id}` | deleteDocument |
| GET | `/documents/{document_id}/submissions` | listCompanyDocumentSubmissions |
| GET | `/documents/{document_id}/submissions/{submission_id}` | getDocumentSubmission |
| DELETE | `/documents/{document_id}/submissions/{submission_id}` | deleteDocumentSubmission |

## Key resources

- **Documents** — Operations for documents

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 57 / 100
- **View full report:** https://jentic.com/apis/simplepdf.eu/simplepdf-eu/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SimplePDF by hand means resolving your company-specific host, setting up bearer auth, and carrying the token across every document and submission call yourself. Through Jentic you install once, import SimplePDF from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SimplePDF puts the document id in the URL path (`/documents/{document_id}/submissions/...`), so a rule can pin your agent to one document: it can list and read that document's submissions and nothing else. You choose the operations it may call, so destructive ones like deleting a document or a submission are not included unless you add them.
- **Credential handling:** Your SimplePDF 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 documents' or 'read a form submission', and Jentic returns the matching SimplePDF operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the SimplePDF API use?

The SimplePDF 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 listdocuments with the SimplePDF API?

Yes. Use the GET /documents endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SimplePDF 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 listdocuments through Jentic?

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

### How many endpoints does the SimplePDF API have?

The SimplePDF API exposes 7 endpoints covering documents operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which SimplePDF operations and credentials the agent may use. Since SimplePDF puts the document id in the URL path, such as `/documents/{document_id}/submissions`, a rule can pin the agent to a single document so it only lists and reads that document's submissions and nothing else. You choose the operations it may call, so destructive ones like deleting a document or a submission stay out of reach unless you add them.