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

# Visma Severa Public Rest API Documentation

The API uses OAuth2 client creadentials flow. To get the Bearer token for the resources you have to request the token by using route '/token', found from Authentication controller. You need to provide a Client_Id, client_secret and scope needed. The client_id and client_secret can be obtained from Severa UI Rest API settings section. After authentication, calls need to use the Bearer token as auth. The API exposes 518 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically get the addresses., get address by id.. Covers 518 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Get the addresses.
- Update (Patch) an address or a part of it.
- Delete an address.
- Insert an address.
- Monitor Severa Public Rest API Documentation operational status and events

## Use cases

### Identity and Authentication Operations

Use the Severa Public Rest API Documentation to perform identity auth operations programmatically. The API provides 518 endpoints covering core functionality including get the addresses., get address by id., update (patch) an address or a part of it..

Example prompt: Call GET `/v1/addresses` to get the addresses.

### Automated Activities Management

Automate activities operations by combining multiple Severa Public Rest API Documentation endpoints. Agents can get address by id. and then update (patch) an address or a part of it. in a single workflow.

Example prompt: Call GET `/v1/addresses/{guid}` to get address by id., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Severa Public Rest API Documentation 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 apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'get the addresses.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/addresses` | Get the addresses. |
| GET | `/v1/addresses/{guid}` | Get address by ID. |
| PATCH | `/v1/addresses/{guid}` | Update (Patch) an address or a part of it. |
| DELETE | `/v1/addresses/{guid}` | Delete an address. |
| POST | `/v1/customers/{customerGuid}/addresses` | Insert an address. |
| GET | `/v1/customers/{customerGuid}/addresses` | Get customer's addresses |
| GET | `/v1/contactpersons/{contactGuid}/addresses` | Get contact person's address |
| POST | `/v1/businessunits` | Insert a business unit. |

## Key resources

- **Activities** — Operations for activities
- **Activityparticipants** — Operations for activityparticipants
- **Activitytypes** — Operations for activitytypes
- **Addresses** — Operations for addresses
- **Bankaccounts** — Operations for bankaccounts

## Why Jentic

- **Setup:** Wiring the Severa Public REST API by hand means running its OAuth 2.0 client-credentials flow, mapping its read, write, and delete scopes to each call, and threading tokens across its large endpoint surface yourself. Through Jentic you install once, import the Severa Public REST API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Severa puts resource ids in the URL path (`/v1/customers/{customerGuid}/addresses` and `/v1/addresses/{guid}`), so a rule can pin your agent to one customer or address and the operations around it. You choose the operations it may call, so a destructive one like deleting an address is not included unless you add it.
- **Credential handling:** Your Severa OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. The client secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list a customer's addresses' or 'create a business unit', and Jentic returns the matching Severa operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Severa Public Rest API Documentation use?

The Severa Public Rest API Documentation uses apiKey, 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 get the addresses. with the Severa Public Rest API Documentation?

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

### What are the rate limits for the Severa Public Rest API Documentation?

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 get the addresses. through Jentic?

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

### How many endpoints does the Severa Public Rest API Documentation have?

The Severa Public Rest API Documentation exposes 518 endpoints covering activities, activityparticipants, activitytypes operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Severa operations and credentials your agent may use. Severa puts resource ids in the URL path, such as `/v1/customers/{customerGuid}/addresses` and `/v1/addresses/{guid}`, so a rule can pin your agent to a single customer or address and the operations around it. You also choose the exact operations it may call, so a destructive one like DELETE `/v1/addresses/{guid}` stays out of reach unless you add it.