canonical: https://jentic.com/apis/starbuero.de/starbuero

# starbuero.de External API

External API - BETA for starbuero.de office management platform. The API exposes 25 endpoints secured with bearer authentication.

## For AI agents

Programmatically create new contact, retrieve all contacts. Covers 25 operations with bearer authentication.

## Scope

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

## Capabilities

- Create new contact
- Retrieve all contacts
- Fetch specific contact
- Update contact
- Remove contact
- List all appointments

## Use cases

### Developer Tools Operations

Use the starbuero.de External API to perform developer tools operations programmatically. The API provides 25 endpoints covering core functionality including create new contact, retrieve all contacts, fetch specific contact.

Example prompt: Call POST `/external/api/v1/addon_contact/contact` to create new contact

### Automated Additional Resources Management

Automate additional resources operations by combining multiple starbuero.de External API endpoints. Agents can retrieve all contacts and then fetch specific contact in a single workflow.

Example prompt: Call GET `/external/api/v1/addon_contact/contact` to retrieve all contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call starbuero.de External 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/external/api/v1/addon_contact/contact` | Create new contact |
| GET | `/external/api/v1/addon_contact/contact` | Retrieve all contacts |
| GET | `/external/api/v1/addon_contact/contact/{contact}` | Fetch specific contact |
| PUT | `/external/api/v1/addon_contact/contact/{contact}` | Update contact |
| DELETE | `/external/api/v1/addon_contact/contact/{contact}` | Remove contact |
| POST | `/external/api/v1/appointment` | Create appointment |
| GET | `/external/api/v1/appointment` | List all appointments |
| GET | `/external/api/v1/appointment/{appointment}` | Retrieve specific appointment |

## Key resources

- **Additional Resources** — Operations related to Additional Resources
- **Addon Contact Management** — Operations related to Addon Contact Management
- **Appointment Management** — Operations related to Appointment Management
- **Employee Management** — Operations related to Employee Management
- **FAQ Management** — Operations related to FAQ Management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/starbuero.de/starbuero/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the starbuero.de External API use?

The starbuero.de External API uses a Bearer token in the Authorization header. 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 new contact with the starbuero.de External API?

Yes. Use the POST `/external/api/v1/addon_contact/contact` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the starbuero.de External 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 new contact through Jentic?

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

### How many endpoints does the starbuero.de External API have?

The starbuero.de External API exposes 25 endpoints covering additional resources, addon contact management, appointment management operations.

### Can I limit what my agent is allowed to do with the starbuero.de External API?

Yes. Jentic One is self-hosted by you, so your own rules decide which starbuero.de operations and credentials the agent may use. Because the contact id sits in the URL path (`/external/api/v1/addon_contact/contact/{contact}`), you can pin the agent to a single contact so it only reads and updates that one and nothing else. You also choose which operations are exposed, so destructive calls like DELETE on a contact stay out of reach unless you explicitly add them.