972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Travel and tourism

AVLRSP Availability response

The UN/EDIFACT interactive message a service provider sends in response to an availability request for a travel, tourism or leisure service.

Sent by
Travel service provider
Received by
Customer, travel agent or booking system
Standard
UN/EDIFACT · Interactive (I-EDI) message
X12 equivalent
No direct equivalent

What is the EDIFACT AVLRSP message?

AVLRSP is the UN/EDIFACT interactive travel, tourism and leisure availability response. The directory defines it as a message sent by a service provider in response to an availability request (AVLREQ) for a travel, tourism or leisure service.

The response lists what is available that matches the request, such as room types, seats or service options, often with rates and conditions. The requester uses it to present options and then reserves one with a reservation request (RESREQ). Because the exchange is interactive, the response returns in the same dialogue as the request, so the booking system can show results while the traveler or agent waits.

How the EDIFACT AVLRSP message worksDiagram of the UN/EDIFACT AVLRSP Availability response message. Travel service provider sends it to customer, travel agent or booking system. It usually follows AVLREQ. It is usually followed by RESREQ. Inside the UIB and UIH envelopes, the directory D.21A requires, in the . 5 conditional segment groups are listed by their trigger segment.How the EDIFACT AVLRSP message worksAvailability response: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSAVLREQAvailability requestAVLRSPSENDERTravel service providerRECEIVERCustomer, travel agentor booking systemUSUALLY FOLLOWED BYRESREQReservation request2 WHAT DIRECTORY D.21A REQUIRESInteractive interchangeUIB … UIZMessage AVLRSPUIH … UITBODY AND SEGMENT GROUPS+ 5 conditional groups, starting with:ERIODSPRDTVLODIBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for AVLRSP. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT AVLRSP message worksDiagram of the UN/EDIFACT AVLRSP Availability response message. Travel service provider sends it to customer, travel agent or booking system. It usually follows AVLREQ. It is usually followed by RESREQ. Inside the UIB and UIH envelopes, the directory D.21A requires, in the . 5 conditional segment groups are listed by their trigger segment.How the EDIFACT AVLRSPmessage worksAvailability response: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSAVLREQAvailability requestAVLRSPSENDERTravel serviceproviderRECEIVERCustomer, travelagent or bookingsystemUSUALLY FOLLOWED BYRESREQReservation request2 WHAT DIRECTORY D.21A REQUIRESInteractive interchange (UIB … UIZ)Message AVLRSP (UIH … UIT)BODY AND SEGMENT GROUPS+ 5 conditional groups, starting with:ERIODSPRDTVLODIBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for AVLRSP.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends AVLRSP, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around AVLRSP and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Returning available rooms, seats or services
  • Returning rates and conditions for options
  • Reporting that nothing matches the request

Where it fits in the message flow

Usually follows AVLREQ Availability request
This message AVLRSP Availability response
Usually followed by RESREQ Reservation request

Structure

Mandatory segments in AVLRSP (directory D.21A)

In UN/EDIFACT directory D.21A, the AVLRSP message has 97 segment positions arranged in 20 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes. This structure comes from one published copy of the directory and has not been independently verified: confirm it before you build a map.

  • UIH
  • UIT

Practical example

AVLRSP in practice

A hotel receives an AVLREQ for three nights. Its system returns an AVLRSP listing two available room types with nightly rates, breakfast options and cancellation conditions. The travel agent presents both to the client, who chooses one.

Implementation

Implementation considerations for AVLRSP

  • Return rates and conditions with each option.
  • Reflect current inventory to avoid failed bookings.
  • Respond within the timeout the requester's system allows.
  • Keep availability consistent across distribution channels.

How ECOM helps

Automate AVLRSP with ECOM

Industry

Hospitality

Procurement, invoicing and supplier integration for hotels, restaurant groups and foodservice suppliers.

Solution

Batch and Real-Time Integration

Scheduled batch processing and real-time, API-driven integration on one platform.

Solution

API Integration

Connect partner and application APIs to your systems and bridge them with EDI processes.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related travel and tourism messages

All 16 travel and tourism messages

Need help with AVLRSP?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us