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.