canonical: https://jentic.com/apis/swaggerhub.wunderbon-io/wunderbon-api

# Wunderbon Io wunderbon API

Welcome to our living wunderbon API documentation. Here you will find almost everything you need to connect to our platform. Start using the real <i>smart receipts</i>® with our value added service platform. With our API we provide you with easy access to the state of the art encrypted and blockchain based service network. Rethink your POS with wunderbon.<br /><br />Dig into our website to discove. The API exposes 34 endpoints secured with bearer authentication.

## For AI agents

Programmatically readfavorite, deletefavorite. Covers 34 operations with bearer authentication.

## Scope

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

## Capabilities

- ReadFavorite
- DeleteFavorite
- CreateFavorite
- ReadIdentifier
- UpdateIdentifier
- DeleteIdentifier

## Use cases

### Identity and Authentication Operations

Use the wunderbon API to perform identity auth operations programmatically. The API provides 34 endpoints covering core functionality including readfavorite, deletefavorite, createfavorite.

Example prompt: Call GET `/favorites/{id}` to readfavorite

### Automated Favorites Management

Automate favorites operations by combining multiple wunderbon API endpoints. Agents can deletefavorite and then createfavorite in a single workflow.

Example prompt: Call DELETE `/favorites/{id}` to deletefavorite, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call wunderbon 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 'readfavorite', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/favorites/{id}` | ReadFavorite |
| DELETE | `/favorites/{id}` | DeleteFavorite |
| POST | `/favorites` | CreateFavorite |
| GET | `/favorites` | ReadFavorites |
| GET | `/identifiers/{id}` | ReadIdentifier |
| PATCH | `/identifiers/{id}` | UpdateIdentifier |
| DELETE | `/identifiers/{id}` | DeleteIdentifier |
| POST | `/identifiers` | CreateIdentifier |

## Key resources

- **Favorites** — Operations for favorites
- **Identifiers** — Operations for identifiers
- **Locations** — Operations for locations
- **Networks** — Operations for networks
- **Ratings** — Operations for ratings

## Why Jentic

- **Setup:** Wiring the wunderbon API by hand means minting its bearer tokens through the /tokens endpoints, attaching them to every request, and managing its resource routes yourself. Through Jentic you install once, import the wunderbon API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The wunderbon API puts each resource id in the URL path (`/favorites/{id}`, `/identifiers/{id}`), so a rule can pin your agent to one resource: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a favorite or an identifier are not included unless you add them.
- **Credential handling:** Your wunderbon API bearer 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 'read a favorite' or 'create an identifier', and Jentic returns the matching wunderbon API 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 wunderbon API use?

The wunderbon 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 readfavorite with the wunderbon API?

Yes. Use the GET `/favorites/{id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the wunderbon 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 readfavorite through Jentic?

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

### How many endpoints does the wunderbon API have?

The wunderbon API exposes 34 endpoints covering favorites, identifiers, locations operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which wunderbon API operations and credentials the agent may use. The wunderbon API puts each resource id in the URL path, such as `/favorites/{id}` and `/identifiers/{id}`, so a rule can pin the agent to a single record and let it only read or update that one. You also choose the exact operations it may call, so destructive ones like DeleteFavorite or DeleteIdentifier stay off the list unless you add them.