Saved Successfully.

webcore latitude

NDC Sandbox & Auto Regression Testing

Shop, price, book, service and cancel real NDC orders against the airline's own test environment, with every request and response captured for inspection. Built for certification runs, integration work and day-to-day agent testing.

Book a Demo What It Covers

The full NDC lifecycle, pre-production

Booking Flows | Order Servicing | Message Logs | Auto Regression

The NDC standard is large, and the gap between "the call returned 200" and "the order is correct" is where integrations fail. webcore latitude closes that gap. It drives the complete order lifecycle through a real interface against the airline's sandbox, captures every NDC message alongside the step that produced it, validates it against the IATA 21.3 schema set, and keeps the whole run as an evidence trail you can hand to a certification programme.

  • AirShopping
  • OfferPrice
  • SeatAvailability
  • ServiceList & ServiceAdd
  • OrderCreate
  • OrderRetrieve & OrderList
  • OrderChange & re-shop
  • Split order
  • Name correction
  • OrderCancel & refund quote
  • OrderChangeNotification
webcore latitude NDC Sandbox home screen showing the booking tool, message logs, automated tests and administration tiles

Who it is for

Built for the people who have to make NDC actually work

Access is by invitation and every user is role-gated, so an airline can put agents, partners and its own engineers on the same deployment without them seeing each other's work.

  • Integration engineers building against an airline's NDC APIs
  • Certification and QA teams gathering evidence for a programme
  • Airline distribution teams onboarding new partners quickly
  • Support teams reproducing a live order problem safely
  • Agency developers validating a change before it ships

One tool, four jobs

Everything the NDC lifecycle needs, in one workspace

The booking tool, the message logs, the regression suite and the administration surface are one application sharing one set of connections — so the order you just created is the order the logs describe and the order the regression run services.

Flight search

AirShopping

Round trip, one way and multi-city open-jaw, with cabin and fare product per leg, airport type-ahead, passenger mix and calendar pricing. Corporate account selection where the connection carries more than one corporate ID.

Offers and pricing

OfferPrice

Filter and compare returned offers, shift the search dates without starting again, then price the chosen offer and see exactly what the carrier returned against what you asked for.

Seats and services

SeatAvailability, ServiceList, ServiceAdd

Work a real seat map, add and remove ancillaries before booking, and confirm what is held versus what is paid for. Cash seating can be enabled or disabled per deployment.

Passengers and payment

OrderCreate

Passenger details and APIS capture, then cash or card payment and order creation — ending in a real order on the airline's test environment, not a mock response.

Confirm a held booking

Re-quote and issue

Take a held order through re-quote and document issue, and see whether the price the carrier honours matches the price it held.

Change date or time

OrderChange, re-shop, re-quote

Re-shop a confirmed order, filter the replacement offers, re-quote and apply the change — per leg or across the whole journey.

Split and correct

SplitOrder, name change

Move passengers out of a multi-passenger order into their own order, or apply a name correction and see the quoted fee before committing to it.

Cancel with a refund quote

OrderCancel

Pull the refund quote first, then cancel — so the amount the carrier will actually return is visible before the order is given up.

Captured in context

Request and response per step

Every NDC request and response is stored next to the step that sent it, grouped by day and by session, so a message is never an orphan you have to correlate by timestamp.

Validated against the schema

IATA 21.3 XSD set

Validate any captured message against the shipped IATA 21.3 schema set and get the specific fault, rather than a generic parse failure.

Edit, replay, compare

Side-by-side viewer

Open request and response side by side, fold, search and wrap, then edit a request and post it to a chosen endpoint to test a theory without rebuilding the whole journey.

Export the evidence

Zip download

Select the messages that matter and download them as a zip — the format a certification reviewer or a carrier support desk will ask for.

Ten job types

The lifecycle, scripted

Order create, order servicing, cancel, date change, post-sale seating, post-sale services, APIS amendment, name correction, split order and confirm-held — each with its own parameters rather than a single generic script.

Chained journeys

Servicing follows the booking

A servicing job chains off the order its source job created and resolves that order at run time, so a suite exercises a real order's whole life instead of a series of disconnected calls.

Scheduled and parallel

Hourly, daily or weekly

Give a job a recurrence and it runs itself. Multiple agents run in parallel, chained work stays together on one agent, and a job can be pinned to a specific agent when you need it.

Evidence when it fails

Traces, errors, tickets

A failed run gives you the extracted NDC error code, the full message log, a replayable browser trace, and a one-click support ticket into the service desk.

Auto Regression

Catch the regression before your partners do

An NDC integration does not break loudly. It breaks when a carrier changes a response shape, an offer stops pricing, or a servicing path starts returning a fee where it used to return free. You find out from a partner, weeks later.

The Auto Regression tool runs the journeys you care about on a schedule, through the same interface a person would use, against the airline's own preprod environment. If a booking stops completing, you know the next morning — with the failing message, the error code and a replayable trace already attached.

Everything the tool can do from its own screens is also available over a REST API and through an MCP server, so an assistant or a build pipeline can define a test, schedule it, run it and read the errors back.

What a run gives you

  • Pass or fail per job, with error and warning counts
  • The extracted NDC error, not just "assertion failed"
  • Every NDC request and response for the run
  • A replayable browser trace of the whole journey
  • Live console output while the run is in progress
  • A support ticket raised straight from the failure
  • Optional NDC message validation alongside the result

Order Change Notifications

Know about the change before the passenger does

Schedule changes, cancellations and ancillary updates arrive as Order Change Notifications. The OCN viewer receives them in real time, pushes them to the right organisation the moment they land, and lets an agent search, open, acknowledge and resend any message.

Notifications are scoped per organisation, so partners see their own order changes and nobody else's.

  • Real-time push, with an alert only for genuinely new messages
  • Paged viewer with agency filter and free-text search
  • Open, acknowledge and resend any notification
  • Encrypted transport, per-organisation scoping

Run it as your own

White-labelled, role-gated and configurable per airline

latitude is deployed per airline and wears that airline's branding. Sign-in either rides your existing portal single sign-on or runs standalone with its own registration, password reset and multi-factor authentication — authenticator app or email one-time code. Optional Azure AD and OpenID Connect sign-in is supported where a carrier already federates its partners.

An administration surface covers NDC connections and API keys, lookup data, developer-log storage and retention, payload file locations, analytics and an on-demand diagnostics dashboard that verifies every configuration setting and probes database, NDC OAuth, service desk and notification connectivity — without ever returning a secret.

Works with

Part of the Webcore NDC toolchain

latitude is one of six Webcore products. These are the ones it shares real machinery with.

webcore certifi

An Auto Regression expectation uses the same contract as a certification use-case step, so an expectation written for one drops straight into the other.

NDC Certification Tool

webcore cmx

The developer portal your partners read — API documentation, capability, roadmap and FAQs — sitting alongside the sandbox they test against.

Content & Portals Platform

webcore fusion

Where latitude proves your integration works, FUSION asks whether the channel is safe to point an autonomous AI agent at.

Agent Readiness Suite

See latitude against your own NDC APIs

We will walk you through the booking flow, the message logs and a scheduled regression run on your own connection.
Trusted by Virgin Atlantic, LATAM Airlines and TAP Air Portugal.