Resident Price Integration
Overview
Target Group: Legal residents of the Canary Islands, Balearic Islands, Ceuta, and Melilla in Spain (residency proof is required, such as DNI/NIE).
Applicable Routes: Only domestic routes in Spain, and must include "designated regional airports". The specific rules are as follows:
Resident's Region
Allowed Route Range
Examples
Canary Islands
Any airport in Spain ↔ Any airport in the Canary Islands
Madrid (MAD) → Tenerife (TFS), Las Palmas (LPA) → Barcelona (BCN)
Balearic Islands
Any airport in Spain ↔ Any airport in the Balearic Islands
Valencia (VLC) → Mallorca (PMI), Ibiza (IBZ) → Seville (SVQ)
Ceuta
Ceuta (JCU) ↔ Seville (SVQ) / Jerez (XRY) / Málaga (AGP)
JCU→AGP, SVQ→JCU
Discount Coverage: Only applicable to "base fare, first piece of baggage per passenger per segment, infant fee, mandatory seat selection fee". Government taxes and fees are not subject to discounts.
Discount Types:
Discount Type
Discount Strength
Applicable Group
Core Requirements
Family Discount
5%
Ordinary families (domestic routes in Spain)
Family-related proof is required; applicable only to any domestic route in Spain
Large Family Discount
10%
Large families in Spain (meeting the "large family" certification standards)
Large Family Certificate is required (format varies by Spanish autonomous community); applicable only to any domestic route in Spain
SARA Resident Discount
75%
Residents of designated regions in Spain (Canary Islands, Balearic Islands, Ceuta, Melilla)
Residency verification (DNI/NIE, etc.) is required; applicable only to routes of "designated regional airports ↔ airports within Spain"
SARA + Family Discount
80%
Residents of the above-mentioned designated regions and ordinary families
Must meet both SARA residency verification and family proof
SARA + Large Family Discount
85%
Residents of the above-mentioned designated regions and large families
Must meet both SARA residency verification and large family proof
Supported Airlines: FR, VY
Integration Method
Query of Resident Fare
In the Search process, a Resident Code needs to be passed to obtain the resident fare. The mapping relationship between Resident Code and discount type is as follows:
Discount Type
Resident Code
Discount
Family Discount
DSC2
5%
Large Family Discount
DSC3
10%
SARA Resident Discount
DSC1
75%
SARA + Family Discount
DSC4
80%
SARA + Large Family Discount
DSC5
85%
Request example:
{
"tripType": "1",
"adultNum": 1,
"childNum": 0,
"infantNum": 0,
"fromCity": "SVQ",
"toCity": "OVD",
"fromDate": "20251103",
"retDate":"20250603",
"includeMultipleFareFamily": true,
"currency": "",
"requestSource": "",
"residentCode":"DSC2"
}2. If a Resident Code is passed in the inquiry, the resident fare discount will be automatically applied to the price in the return result.
Ticketing for Resident Fare
If a ResidentCode is passed in the inquiry process, the resident fare will be applied to the inquiry process and all subsequent processes. In the ticketing process, resident information needs to be passed for verification of the resident fare.
Parameter Name
Description
DocType
Document type. The document types supported by the resident fare are detailed in the Instructions for Accessing resident Fare. The enumeration values are D: DNI, E: NIE, U: underage
DocNum
Document number. Required if DocType is D or E; not required if DocType is U
Municipality
Municipality code. Required when ResidentCode is DSC1, DSC4, or DSC5
LargeFamilyCert
Large family discount certificate. Required when ResidentCode is DSC2, DSC3, DSC4, or DSC5
Community
Autonomous community code. Required when ResidentCode is DSC2, DSC3, DSC4, or DSC5
Request example:
{
"cid": "******",
"sessionId": "5475cdb2-ce22-4e52-8c2f-8ef2e81e462c",
"passengers": [
{
"name": "TEST/ONE",
"passengerType": 0,
"birthday": "19900101",
"gender": "M",
"cardNum": "00000000",
"cardType": "PP",
"cardIssuePlace": "SG",
"cardExpired": "20301231",
"nationality": "SG",
"ancillaries": [],
"residentInfo": {
"docType": "D",
"docNum": "99999999Z",
"municipality": "",
"largeFamilyCert": "06-9999-99",
"community": "502973"
}
}
],
"contact": {
"name": "TEST/TEST",
"address": null,
"postcode": null,
"email": "[email protected]",
"mobile": "0086-13928109091"
},
"requestSource": ""
}2. The municipality and community fields need to pass codes. I have provided two mapping relationships between names and codes, which can be found in the following documents:
municipality: The code is a 6-digit number composed of CPOR + CMUN + DC.
25codmun.xlsx
community:
community.xlsx
3. Different discount types have different requirements for resident fare information, please refer to the following table:
Resident Code
docType
docNum
municipality
largeFamilyCert
community
DSC2
✅
Required when docType is D or E
❌
✅
✅
DSC3
✅
Required when docType is D or E
❌
✅
✅
DSC1
✅
Required when docType is D or E
✅
❌
❌
DSC4
✅
Required when docType is D or E
✅
✅
✅
DSC5
✅
Required when docType is D or E
✅
✅
✅
Verification of Resident Fare
Atlas will pass the resident fare information provided by the customer during the ticketing process to the airline for verification. Due to the different verification processes of different airlines, the interaction with the customer will be responded to, as shown in the following table:
Airline
Verification Method
FR
The resident information will be directly passed to the airline for verification during the Order process. If the verification is passed, the order will be created; if the verification fails, the Order response will directly return a failure.
VY
The airline will verify the resident fare information only after ticketing. Moreover, if the verification fails, the airline will not cancel the order but will require the passenger to present relevant documents on site. Therefore, if a customer books the VY resident fare, Atlas will not cancel the order regardless of whether the verification passes or not. Please ask the passenger to prepare relevant documents for the airline's inspection at the airport.
Last updated