canonical: https://jentic.com/apis/sellsy.com/sellsy

# Sellsy API

Find out the [Postman collections](dist/postman/CollectionsApiV2.json) with the required [environment variables](dist/postman/Environment.json) Find out the [Changelog](changelog.html) Errors The errors are returned in JSON with the following format: The `details` field can contain an object that details the error. It is used in particular during validation to return the invalid fields | HTTP Code. The API exposes 351 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create a comment, comments list. Covers 351 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Create a comment
- Comments List
- Get comment details
- Update a comment
- Delete a comment
- Search comments

## Use cases

### Communications Operations

Use the Sellsy API to perform communications operations programmatically. The API provides 351 endpoints covering core functionality including create a comment, comments list, get comment details.

Example prompt: Call POST /comments to create a comment

### Automated Invoices Management

Automate invoices operations by combining multiple Sellsy API endpoints. Agents can comments list and then get comment details in a single workflow.

Example prompt: Call GET /comments to comments list, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'create a comment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/comments` | Create a comment |
| GET | `/comments` | Comments List |
| GET | `/comments/{id}` | Get comment details |
| PUT | `/comments/{id}` | Update a comment |
| DELETE | `/comments/{id}` | Delete a comment |
| POST | `/comments/search` | Search comments |
| POST | `/companies` | Create a company |
| GET | `/companies` | Companies List |

## Key resources

- **Invoices** — Invoices documents
- **Opportunities** — Opportunity Management
- **Credit Notes** — Operations related to Credit Notes
- **Companies** — Client, prospect and supplier management
- **Individuals** — Individuals management

## Why Jentic

- **Setup:** Wiring the Sellsy API by hand means running its OAuth2 flow, choosing between the authorization-code and client-credentials grants, refreshing tokens, and building each request across a large surface yourself. Through Jentic you install once, import Sellsy from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** The Sellsy API puts the comment and company ids in the URL path (`/comments/{id}` and `/companies/{id}`), so a rule can pin your agent to one comment: it can read and update that comment and nothing else. You choose the operations it may call, so destructive ones like deleting a comment are not included unless you add them.
- **Credential handling:** Your Sellsy OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a comment' or 'search companies', and Jentic returns the matching Sellsy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Sellsy API use?

The Sellsy API uses OAuth 2.0 for authorization. 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 create a comment with the Sellsy API?

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

### What are the rate limits for the Sellsy 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 create a comment through Jentic?

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

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

The Sellsy API exposes 351 endpoints covering invoices, opportunities, credit notes operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sellsy operations and OAuth credentials the agent may use. Since the Sellsy API carries the comment and company ids in the URL path, such as `/comments/{id}` and `/companies/{id}`, a rule can pin the agent to a single comment or company so it only reads and updates that record. You also choose exactly which operations are exposed, so destructive calls like DELETE `/comments/{id}` stay unavailable unless you add them.