canonical: https://jentic.com/apis/swaggerhub.adas-a2b-services/adas---a2b---business---objects

# Adas A2b Services ADAS - A2B - Business - Objects

Standardisierte Geschäftsobjekte zur Übertragung als Datenpakete über den Datenhub Changelog * 0.9.5 -> Erweiterung epa_version um neuen Wert epa4all30. The API exposes 2 endpoints.

## For AI agents

Programmatically apotheke / anbieter übergibt einen nachweis der unterstützen ti-services, apotheke / anbieter übergibt eine erste vorauswahl an detailinformationen einer . Covers 2 operations.

## Scope

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

## Capabilities

- Apotheke / Anbieter übergibt einen Nachweis der unterstützen TI-Services
- Manage developer tools data programmatically
- Integrate ADAS - A2B - Business - Objects into automated workflows
- Query and filter ADAS - A2B - Business - Objects records by parameters
- Monitor ADAS - A2B - Business - Objects operational status and events

## Use cases

### Developer Tools Operations

Use the ADAS - A2B - Business - Objects to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including apotheke / anbieter übergibt einen nachweis der unterstützen ti-services, apotheke / anbieter übergibt eine erste vorauswahl an detailinformationen einer .

Example prompt: Call POST /nnf/pos to apotheke / anbieter übergibt einen nachweis der unterstützen ti-services

### Data Retrieval and Monitoring

Query ADAS - A2B - Business - Objects resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary ADAS - A2B - Business - Objects endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call ADAS - A2B - Business - Objects 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 none tokens manually.

Example prompt: Search Jentic for 'apotheke / anbieter übergibt einen nachweis der unterstützen ti-services', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /nnf/pos | Apotheke / Anbieter übergibt einen Nachweis der unterstützen TI-Services |
| POST | /erx/pre/rsp | Apotheke / Anbieter übergibt eine erste Vorauswahl an Detailinformationen einer |

## Key resources

- **objekte** — standardisierte Geschäftsobjekte
- **uebergeben** — übergeben
- **abrufen** — abrufen
- **meta** — Metadaten

## Why Jentic

- **Setup:** Wiring the ADAS A2B Business Objects API by hand means choosing between the SwaggerHub host and the portal.adas.de host and building the point-of-sale and prescription-response payloads yourself. Through Jentic you install once, import the ADAS A2B Business Objects API from the API Directory, store any required credential once, and your agent calls it.
- **Permission scoping:** The Business Objects API takes its targets in the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as posting a point-of-sale record or a prescription response. Every operation the agent can run is one you have added to its allowed set.
- **Credential handling:** Any ADAS A2B Business Objects credential 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 'submit a point-of-sale record' or 'post a prescription response', and Jentic returns the matching ADAS A2B Business Objects 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 ADAS - A2B - Business - Objects use?

The ADAS - A2B - Business - Objects uses no authentication. 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 apotheke / anbieter übergibt einen nachweis der unterstützen ti-services with the ADAS - A2B - Business - Objects?

Yes. Use the POST /nnf/pos endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the ADAS - A2B - Business - Objects?

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 apotheke / anbieter übergibt einen nachweis der unterstützen ti-services through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'apotheke / anbieter übergibt einen nachweis der unterstützen ti-services'. Jentic returns the matching ADAS - A2B - Business - Objects operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ADAS - A2B - Business - Objects have?

The ADAS - A2B - Business - Objects exposes 2 endpoints covering objekte, uebergeben, abrufen operations.

### Can I limit what my agent is allowed to do with the ADAS A2B Business Objects API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because this API takes its targets in the request body rather than the URL path, you scope by operation: you can allow the agent to post a point-of-sale record via POST /nnf/pos while withholding the prescription-response call at POST /erx/pre/rsp, or the reverse. Every operation the agent can run is one you have added to its allowed set.