canonical: https://jentic.com/apis/quaderno.io/quaderno

# Quaderno API

Quaderno helps you scale your business without stressing about taxes. Our powerful REST API solves all your tax compliance needs: - Accurate tax calculation on every sale, worldwide. - Billing with automatic invoices and credit notes. - Alerts for new tax obligations and registrations. - Tax reports by country or state. - Quaderno Checkout, if you don't have your own checkout. Here you can check o. The API exposes 89 endpoints secured with basic, oauth2 authentication.

## For AI agents

Programmatically retrieve a custom account, update a custom account. Covers 89 operations with basic, oauth2 authentication.

## Scope

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

## Capabilities

- Retrieve a custom account
- Update a custom account
- Create a custom account
- List all accounts
- Access Quaderno API payments resources via REST API

## Use cases

### Payments Operations

Use the Quaderno API to perform payments operations programmatically. The API provides 89 endpoints covering core functionality including retrieve a custom account, update a custom account, create a custom account.

Example prompt: Call GET `/accounts/{id}` to retrieve a custom account

### Automated API features Management

Automate API features operations by combining multiple Quaderno API endpoints. Agents can update a custom account and then create a custom account in a single workflow.

Example prompt: Call PUT `/accounts/{id}` to update a custom account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Quaderno 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 basic, oauth2 tokens manually.

Example prompt: Search Jentic for 'retrieve a custom account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts/{id}` | Retrieve a custom account |
| PUT | `/accounts/{id}` | Update a custom account |
| POST | `/accounts` | Create a custom account |
| GET | `/accounts` | List all accounts |
| POST | `/addresses` | Create an address |
| GET | `/addresses` | List addresses |
| GET | `/addresses/{id}` | Retrieve an address |
| PUT | `/addresses/{id}` | Update an address |

## Key resources

- **API features** — ## Authentication

Quaderno uses an API key to authorize all requests, allowing access to the API in
- **Changelog** — # 20241028

- **Backported breaking change**: Due to legal requirements, the `number` and `issue_dat
- **Registered Jurisdictions** — Registered jurisdictions refer to the locations where your business is registered to collect taxes a

## Why Jentic

- **Setup:** Wiring Quaderno by hand means resolving your account-specific quadernoapp.com host, handling its basic or OAuth2 auth, and shaping each request yourself. Through Jentic you install once, import the Quaderno API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Quaderno puts the account and address id in the URL path (`/accounts/{id}`, `/addresses/{id}`), so a rule can pin your agent to one account or address: it can read and update that record and nothing else. You choose the operations it may call, so ones like creating new accounts are not included unless you add them.
- **Credential handling:** Your Quaderno credential 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 'retrieve an account' or 'create a billing address', and Jentic returns the matching Quaderno 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 Quaderno API use?

The Quaderno API uses basic, oauth2 authentication. 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 retrieve a custom account with the Quaderno API?

Yes. Use the GET `/accounts/{id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Quaderno 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 retrieve a custom account through Jentic?

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

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

The Quaderno API exposes 89 endpoints covering API features, changelog, registered jurisdictions operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Quaderno operations and credential the agent may use. Quaderno carries the account and address id in the URL path, such as GET `/accounts/{id}` and PUT `/addresses/{id}`, so you can pin the agent to a single account or address and let it read and update only that record. You choose the operations it can call, so write actions like POST /accounts to create a new account stay off unless you explicitly add them.