canonical: https://jentic.com/apis/swaggerhub.iway.io/api-documentation-iway-transfer

# Iway API documentation i’way transfer

API documentation to external integration. The API exposes 16 endpoints secured with bearer authentication.

## For AI agents

Programmatically user authorization in i`way transfer booking system, method for checking whether coordinates are in polygons of places (available for. Covers 16 operations with bearer authentication.

## Scope

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

## Capabilities

- User authorization in i`way transfer booking system
- Method for checking whether coordinates are in polygons of places (available for
- Getting the list of offers on "Transfer" service
- Order creation
- Receive travel list

## Use cases

### Developer Tools Operations

Use the API documentation i’way transfer to perform developer tools operations programmatically. The API provides 16 endpoints covering core functionality including user authorization in i`way transfer booking system, method for checking whether coordinates are in polygons of places (available for, getting the list of offers on "transfer" service.

Example prompt: Call POST `/v3/auth/login` to user authorization in i`way transfer booking system

### Automated user Management

Automate user operations by combining multiple API documentation i’way transfer endpoints. Agents can method for checking whether coordinates are in polygons of places (available for and then getting the list of offers on "transfer" service in a single workflow.

Example prompt: Call POST `/v3/places/check-location-from-places` to method for checking whether coordinates are in polygons of places (available for, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API documentation i’way transfer 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 'user authorization in i`way transfer booking system', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v3/auth/login` | User authorization in i`way transfer booking system |
| POST | `/v3/places/check-location-from-places` | Method for checking whether coordinates are in polygons of places (available for |
| GET | `/v3/prices` | Getting the list of offers on "Transfer" service |
| GET | `/v3/prices/rent` | Getting the list of offers for "Rent with driver" service |
| POST | `/v3/orders` | Order creation |
| POST | `/v3/orders/approve/{transaction}` | Order Confirmation |
| GET | `/v3/orders/trips` | Receive travel list |
| PUT | `/v3/orders/trips` | Trip information update |

## Key resources

- **user** — Users
- **place** — Places
- **transport node** — TransportNode
- **price** — Prices
- **order** — Orders

## Why Jentic

- **Setup:** Wiring the i'way transfer API by hand means implementing its JWT bearer flow, logging in at `/v3/auth/login` to get a token, attaching it to the pricing and order requests, and handling refresh and retries yourself. Through Jentic you install once, import i'way transfer from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** i'way transfer puts the transaction id in the URL path for order approval (`/v3/orders/approve/{transaction}`), so a rule can pin the agent to approving one transaction. You choose the operations it may call, so pricing lookups and read-only trip listings can be allowed while order approval stays out of the set unless you add it.
- **Credential handling:** Your i'way transfer 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 'authorize a user in the i'way transfer booking system' or 'get transfer prices', and Jentic returns the matching i'way transfer 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 API documentation i’way transfer use?

The API documentation i’way transfer 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 user authorization in i`way transfer booking system with the API documentation i’way transfer?

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

### What are the rate limits for the API documentation i’way transfer?

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 user authorization in i`way transfer booking system through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'user authorization in i`way transfer booking system'. Jentic returns the matching API documentation i’way transfer operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API documentation i’way transfer have?

The API documentation i’way transfer exposes 16 endpoints covering user, place, transport node operations.

### Can I limit what my agent is allowed to do with the i'way transfer booking API?

Yes. Because Jentic One is self-hosted, your own rules decide which i'way transfer operations and credentials the agent can use, so you can allow read-only calls like getting transfer offers from GET `/v3/prices`, rental offers from GET `/v3/prices/rent`, and trip lists from GET `/v3/orders/trips` while keeping order creation and approval out of scope. Since the transaction id lives in the URL path for order approval at POST `/v3/orders/approve/{transaction}`, a rule can pin the agent to approving a single transaction. Order creation at POST `/v3/orders` stays unavailable unless you explicitly add it to the allowed set.