starbuero.de External API

Setup

Wiring the starbuero.de External API by hand means setting up its bearer token, mapping the contact and appointment endpoints, and threading the contact and appointment ids through reads and updates yourself. Through Jentic you install once, import the starbuero.de External API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The API puts the contact id in the URL path (/external/api/v1/addon_contact/contact/{contact}), so a rule can pin your agent to one contact: it can read and update that contact and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.

Credential isolation

Your starbuero.de token 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a new contact' or 'book an appointment', and Jentic returns the matching starbuero.de External API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.