canonical: https://jentic.com/apis/swaggerhub.bookaway/bookaway-supply-api

# Bookaway supply api

Bookaway supply API - every request should have a bearer authorization header as "bearer xxxxxxxxxxxxxx". The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically get all routes, get all routes. Covers 13 operations with bearer authentication.

## Scope

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

## Capabilities

- Get all routes
- Manage identity auth data programmatically
- Integrate Bookaway supply API into automated workflows
- Query and filter Bookaway supply API records by parameters
- Monitor Bookaway supply API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Bookaway supply API to perform identity auth operations programmatically. The API provides 13 endpoints covering core functionality including get all routes, get all routes, get all trips for specific date.

Example prompt: Call GET /routes to get all routes

### Automated partners Management

Automate partners operations by combining multiple Bookaway supply API endpoints. Agents can get all routes and then get all trips for specific date in a single workflow.

Example prompt: Call GET /routes.json to get all routes, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bookaway supply 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 'get all routes', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/routes` | Get all routes |
| GET | `/routes.json` | Get all routes |
| POST | `/trips` | get all trips for specific date |
| GET | `/trips` | get all trips for specific date |
| GET | `/stations` | get all stations |
| GET | `/stations.json` | get all stations |
| GET | `/stations/{stationId}` | get specific station |
| GET | `/cities` | get all cities |

## Key resources

- **partners** — partners of bookaway

## Why Jentic

- **Setup:** Wiring the Bookaway supply API by hand means learning its bearer-token auth, targeting the Bookaway supply host, and handling the routes, trips, and stations calls with retries yourself. Through Jentic you install once, import the Bookaway supply API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The API puts the station id in the URL path (`/stations/{stationId}`), so a rule can pin your agent to reading one station. You choose the operations it may call, so creating trips with POST /trips is not included unless you add it.
- **Credential handling:** Your Bookaway 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 'list transfer routes' or 'look up a station', and Jentic returns the matching Bookaway supply 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 Bookaway supply API use?

The Bookaway supply 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 get all routes with the Bookaway supply API?

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

### What are the rate limits for the Bookaway supply 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 get all routes through Jentic?

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

### How many endpoints does the Bookaway supply API have?

The Bookaway supply API exposes 13 endpoints covering partners operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Bookaway Supply operations and credentials the agent can use. You can restrict it to read-only calls like GET /routes, GET /trips, and GET /stations, and because the station id lives in the URL path (`/stations/{stationId}`) a rule can pin the agent to reading a single station. Write operations such as POST /trips are excluded unless you explicitly grant them.