Visma Severa Public Rest API Documentation

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 isolation

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.

Intent-based discovery

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.