How to connect to sevDesk

sevDesk authenticates with a single API token that you copy out of your own sevDesk account. There is no OAuth sign-in screen and nothing to authorize: you reveal one token in sevDesk and paste it into Vault.

The token is static — it does not expire and never needs refreshing, so once the connection is saved it keeps working until the token is deliberately regenerated. Entering it takes seconds. The two things worth reading before you start are the plan requirement and the choice of which sevDesk user the token belongs to — both are covered below.

Prerequisites

A sevDesk account on the Buchhaltung Pro plan or higher. This is an eligibility requirement rather than a step you can work around — see the Overview tab for the full plan breakdown. sevDesk states this in its own sevDesk API help article. If you are on a lower tier, upgrade in sevDesk — or ask whoever manages the subscription to — before continuing; see sevDesk pricing for the current plans. A free trial is available if you want to try the connection before committing to a plan.
A sevDesk user account that will stay in place. The token belongs to the individual user who reveals it and is lost permanently if that user is ever deleted. See the next section — this is the one decision that is awkward to undo later.

Choose the right sevDesk user first

A sevDesk API token is bound to the specific user it was issued to: if that user account is ever deleted, its token is permanently lost and the connection stops working. Deleting the user does not hand the token over to anyone else.

For an integration that runs unattended, prefer a durable administrator or shared service user over an individual employee's personal account, which may be removed when they leave.

1. Copy your API token from sevDesk

Sign in to sevDesk and open the API token screen. sevDesk's own help article, Wo finde ich meinen API Token in sevdesk, is the current reference for this navigation. It documents two routes, and which one you see depends on your plan:

Erweiterungen (Extensions) > Integrationen (Integrations) — the token sits in the API-Token für Integrationen section at the top of the page.
Erweiterungen (Extensions) > API

On either screen, click Einblenden ("Show") and enter your own sevDesk login password when prompted — that prompt asks for your account password, not for the API token. The token is then revealed as a 32-character hexadecimal string. Copy it exactly as displayed.

Treat the token like a password. Anyone holding it can read and write the accounting data in your sevDesk account.

2. Paste it into Vault

In Vault, open the sevDesk connection. You are prompted for a single value:

Field	What to paste
API Token	The token you copied from sevDesk in step 1

Paste the raw token on its own. Do not add a Bearer prefix or any other wrapper, and check that your copy did not pick up a leading or trailing space — sevDesk rejects a token that does not match exactly.

Save the connection. Once the token is accepted, the connection status switches to Connected.

Notes

Nothing to re-authorize. The token has no expiry and no refresh cycle, so there is no periodic reconnection to schedule. The connection only needs attention if the token itself is changed in sevDesk.
Regenerating the token invalidates the previous one immediately. If you or a colleague issues a fresh token in sevDesk, update the value in Vault straight away — the old token stops working at the moment the new one is created, with no grace period.
One token covers the whole sevDesk account. There is no subdomain, company id or region to supply alongside it: the token already scopes the connection to the sevDesk account it was issued in.

Troubleshooting

A 401 immediately after saving. The token was almost certainly altered in transit: re-copy it from sevDesk, and check for surrounding whitespace or an accidentally added Bearer prefix.
A connection that worked starts returning 401. A sevDesk token is only ever invalidated deliberately, so treat this as revoked rather than a temporary glitch — retrying will not clear it. The two usual causes are that the token was regenerated in sevDesk, or that the user who owned it was deleted. Reveal a fresh token following step 1 and update the connection with it.
No API token section appears in sevDesk. The account is most likely on a plan below Buchhaltung Pro. Check the plan first, then ask an administrator of the sevDesk account.

Still stuck? Apideck Support can help.