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

# Adas A2b Services ADAS - A2B - Common - Services

Universelle Basisschnittstelle zur Anbindung eines externen Systems an die Warenwirtschaftssysteme (WaWi) deutscher Apotheken. The API exposes 1 endpoints secured with oauth2, openIdConnect authentication.

## For AI agents

Programmatically apotheke prüft die verfügbarkeit eines adas-a2b-webservices. Covers 1 operations with oauth2, openIdConnect authentication.

## Scope

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

## Capabilities

- Apotheke prüft die Verfügbarkeit eines ADAS-A2B-Webservices
- Manage developer tools data programmatically
- Integrate ADAS - A2B - Common - Services into automated workflows
- Query and filter ADAS - A2B - Common - Services records by parameters
- Monitor ADAS - A2B - Common - Services operational status and events

## Use cases

### Developer Tools Operations

Use the ADAS - A2B - Common - Services to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including apotheke prüft die verfügbarkeit eines adas-a2b-webservices.

Example prompt: Call POST /health to apotheke prüft die verfügbarkeit eines adas-a2b-webservices

### Data Retrieval and Monitoring

Query ADAS - A2B - Common - Services 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 - Common - Services endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call ADAS - A2B - Common - Services 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 oauth2, openIdConnect tokens manually.

Example prompt: Search Jentic for 'apotheke prüft die verfügbarkeit eines adas-a2b-webservices', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /health | Apotheke prüft die Verfügbarkeit eines ADAS-A2B-Webservices |

## Key resources

- **common** — Basis-Schnittstelle für einen Health-Check

## Why Jentic

- **Setup:** Wiring the ADAS A2B Common Services API by hand means setting up its NGDA OAuth2 and OpenID Connect flow and choosing between the SwaggerHub host and the portal.adas.de host just to run its health check. Through Jentic you install once, import the ADAS A2B Common Services API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** The Common Services API exposes a single health-check operation and takes its input in the request body, so scope by operation: limit the agent to the operations it needs, such as posting a service health check. Every operation the agent can run is one you have added to its allowed set.
- **Credential handling:** Your ADAS A2B Common Services OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check whether the A2B service is available', and Jentic returns the matching ADAS A2B Common Services 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 - Common - Services use?

The ADAS - A2B - Common - Services uses oauth2, openIdConnect 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 prüft die verfügbarkeit eines adas-a2b-webservices with the ADAS - A2B - Common - Services?

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

### What are the rate limits for the ADAS - A2B - Common - Services?

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 prüft die verfügbarkeit eines adas-a2b-webservices through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'apotheke prüft die verfügbarkeit eines adas-a2b-webservices'. Jentic returns the matching ADAS - A2B - Common - Services operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ADAS - A2B - Common - Services have?

The ADAS - A2B - Common - Services exposes 1 endpoints covering common operations.

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

Yes. Because Jentic One is self-hosted, you decide which operations and credentials the agent may use, and it can only call what you have added to its allowed set. This API exposes a single health-check operation, POST /health, which takes its input in the request body, so you scope by operation and grant the agent just the service health check it needs. Every operation the agent can run is one you have explicitly permitted.