Skip to main content

​
Overview

The Axus integration lets your agents read trip itineraries and their bookings directly from Axus Travel App over the official Pull API. Agents fetch an itinerary by its numeric id and get the full booking spine — flights, lodging, tours, transfers, and activities — with travelers, dates, providers, and confirmation status. Because the integration reads by itinerary id, it works whether or not the client-facing share link has been published. This is the reliable way to audit or analyze trips, since published share links are often only created for a subset of trips.

​
Features

  • Get itinerary by id: Pull one itinerary’s full bookings, travelers, and dates by its numeric Axus id
  • List itineraries: Discover itineraries by created/updated date window or by advisor/traveler
  • Normalized bookings: A compact, agent-friendly booking spine by default (HTML notes and images stripped), with a raw option for the full payload

​
Prerequisites

  • An Axus Travel App account
  • Pull (read) API access enabled for your organization — this is a paid Axus add-on; contact Axus support to enable it and to receive your clientId (a UUID)
  • The Axus account login (username/email) and password the API access is tied to
Axus issues a single Pull-API clientId per organization, tied to a specific Axus login. Consider using a dedicated service login (rather than an individual’s account) so the connection doesn’t break when a personal password changes.

​
Setup Guide

1

Enable Pull API access with Axus

Contact Axus support and request Pull (read) API access. They will provision a clientId (UUID) for your organization and tie it to one of your Axus account logins.
2

Connect Axus in Aster

In Aster Agents, navigate to Control Hub > Integrations and locate the Axus Travel App card. Click Connect and provide:
  • Axus Client ID — the Pull-API clientId UUID from Axus support
  • Axus Username — the Axus login email the API is tied to
  • Axus Password — the password for that login
Aster validates the credentials against the Axus /token endpoint before saving. If the clientId is rejected, confirm with Axus that Pull access is actually enabled.
3

Grant the tools to an agent

Add the Axus Get Itinerary and Axus List Itineraries tools to any agent that needs trip data.

​
Available Tools

​
axus_get_itinerary

Fetch one itinerary by its numeric id.
  • itinerary_id (required) — the number in an Axus admin URL (https://axustravelapp.com/admin/itinerary/{id}). If you store Axus links in a CRM, this is typically the design/admin URL’s id.
  • raw (optional) — if true, returns the full unmodified Axus payload (~100KB, includes HTML notes/images). Default false returns a compact normalized booking spine.
Returns the itinerary title, status, dates, travelers, and a normalized list of bookings (type, provider, location, dates, confirmation number/status).

​
axus_list_itineraries

List itinerary summaries filtered by date window or advisor/traveler.
  • created_at_start / created_at_end — created-date window (inclusive, YYYY-MM-DD)
  • updated_at_start / updated_at_end — updated-date window (inclusive, YYYY-MM-DD)
  • advisor_id / traveler_id — filter to a single advisor or traveler
Keep date ranges tight — very wide windows can time out on the Axus side. Use axus_get_itinerary to pull full bookings for any id returned here.

​
Limitations

  • Read-only. The Pull API exposes itineraries, bookings, advisors, and travelers. There is no write/push capability — agents cannot modify Axus data.
  • Axus library tour templates (admin panel) are not exposed by this integration.