Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
Swedavia Connector
Overview
The Swedavia connector provides access to real-time and historical flight information, airport details, and related services for Swedavia-operated airports. This connector supports endpoints for retrieving departure and arrival data, querying flights with filters, accessing airport information, and more. This documentation outlines each endpoint, its purpose, parameters, and expected outputs, mirroring the structure of the Swedavia Connector documentation for clarity.
Integration Overview
This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the Swedavia connector.
Supported Integration Action Points
- getDeparturesInfo: Retrieves departure information for a specific airport and date.
- getArrivalsInfo: Retrieves arrival information for a specific airport and date.
- getQuery:Queries flight information using an OData filter expression.
- getHeartbeat:Checks API availability (Swedavia internal use only).
- get-airports:Retrieves a list of Swedavia airports.
- get-language: Retrieves supported languages for airport information.
- get-iata-destinations: Retrieves destinations served by a specific airport.
- get-iata-parkinglots:Retrieves parking lot information for a specific airport.
- get-iata-shops: Retrieves shop information for a specific airport.
- get-iata-restaurants: Retrieves restaurant information for a specific airport.
- get-iata-services: Retrieves service information for a specific airport.
- get-airlines: Retrieves airline information for Swedavia airports.
- get-airports-airport: Retrieves projected wait times for a specific airport.
- get-airports-airport-flights:Retrieves flight-specific wait time information.
Detailed Endpoint Documentation
Latest Rates Retrieval
Action
Latest Rates Retrieval
Purpose
Retrieves a comprehensive list of departure flights for a specified airport and date, including flight details, statuses, and check-in information.
Parameters
- Required:
- airportIATA: IATA code of the departure airport (string, e.g., ARN).
- date: Date in RFC 3339 format (YYYY-MM-DD, e.g., 2025-05-09).
- Accept: Header specifying response format (string, default: application/json).
- Optional:
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON or XML object with:
- from: Object containing departure airport details (IATA, ICAO, Swedish/English names, departure date).
- numberOfFlights: Number of flights in the response (integer).
- flights: Array of flight objects, each including:
- flightId: Flight number (string).
- arrivalAirportSwedish/English: Arrival airport names (string).
- airlineOperator: IATA, ICAO, and name of the airline (object).
- departureTime: Scheduled, estimated, and actual UTC times (object).
- locationAndStatus: Terminal, gate, gate actions, and flight status (object).
- checkIn: Check-in status and desk range (object).
- codeShareData: Alternate flight IDs (array).
- flightLegIdentifier: Flight plan ID, callsign, aircraft registration, etc. (object).
- viaDestinations: Intermediate airports (array).
- remarksEnglish/Swedish: Remarks for FIDS screens (array).
- diIndicator: Domestic (D), International (I), or Schengen (S) indicator (string).
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error, etc.).
Workflow Example
1. Configure the API client with the base URL and subscription key (if required).
2. Execute getDeparturesInfo with airportIATA=ARN, date=2025-05-09, and Accept=application/json.
3. Process the response to display flight details in a dashboard or app.
Pair Conversion Retrieval
Action
getArrivalsInfo
Purpose
Retrieves a list of arrival flights for a specified airport and date, including flight details, statuses, and baggage information.
Parameters
- Required:
- airportIATA: IATA code of the arrival airport (string, e.g., ARN).
- date: Date in RFC 3339 format (YYYY-MM-DD, e.g., 2025-05-09).
- Accept: Header specifying response format (string, default: application/json).
- Optional:
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base UR
Output
- Successful: Returns a JSON or XML object with:
- to: Object containing arrival airport details (IATA, ICAO, Swedish/English names, arrival date).
- numberOfFlights: Number of flights in the response (integer).
- flights: Array of flight objects, each including:
- flightId: Flight number (string).
- departureAirportSwedish/English: Departure airport names (string).
- airlineOperator: IATA, ICAO, and name of the airline (object).
- arrivalTime: Scheduled, estimated, and actual UTC times (object).
- locationAndStatus: Terminal, gate, and flight status (object).
- baggage: Baggage claim details (estimated first bag, claim unit, etc.) (object).
- codeShareData: Alternate flight IDs (array).
- flightLegIdentifier: Flight plan ID, callsign, aircraft registration, etc. (object).
- remarksEnglish/Swedish: Remarks for FIDS screens (array).
- viaDestinations: Intermediate airports (array).
- diIndicator: Domestic (D), International (I), or Schengen (S) indicator (string).
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error, etc.).
Workflow Example
1. Configure the API client with the base URL and subscription key (if required).
2. Execute getArrivalsInfo with airportIATA=ARN, date=2025-05-09, and Accept=application/json.
3. Use the response to display arrival schedules or baggage claim information
Pair Conversion with Amount
Action
getQuery
Purpose
Queries flight information using an OData filter expression, allowing flexible retrieval of arrival or departure data based on airport, flight type, dates, or statuses.
Parameters
- Required:
- Accept: Header specifying response format (string, default: application/json).
- Optional:
- filter: OData filter expression (string, e.g., airport eq ‘ARN’ and flightType eq ‘D’).
- continuationtoken: Base64-encoded token for pagination (string, requires client-side escaping).
- count: Number of items to return (integer, default: 25, max: 1000).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL. Limit to one call per two seconds to avoid 429 (Too Many Requests) errors.
Output
- Successful: Returns a JSON or XML object with:
- flights: Array of flight objects, each containing:
- arrival: Arrival flight details (as in getArrivalsInfo) (object, nullable).
- departure: Departure flight details (as in getDeparturesInfo) (object, nullable).
- scheduledDate: Scheduled date of the flight (string).
- continuationtoken: Token for retrieving the next set of results (string).
- flights: Array of flight objects, each containing:
- Failure: Returns error codes (400: Bad Request, 429: Too Many Requests, 500: Internal Server Error).
Workflow Example
1. Execute getQuery with filter=airport eq ‘ARN’ and flightType eq ‘D’ and scheduled eq ‘20250509’.
2. Store the continuationtoken for pagination.
3. Process the response to display filtered flight data.
Historical Rates Retrieval
Action
getHeartbeat
Purpose
Checks the API’s availability (for Swedavia internal use only).
Parameters
- Required:
- Accept: Header specifying response format (string, default: application/json).
- Optional:
- evaluationId: Evaluation identifier (integer).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful: Returns a JSON object with heartbeat status detail
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute getHeartbeat with evaluationId=123 (internal use only).
2. Verify API availability based on the response.
Historical Conversion with Amount
Action
get-airports
Purpose
Retrieves a list of Swedavia-operated airports.
Parameters
- Optional:
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful: Returns data including CenterName, Services, AgeGroupsServed, and InsuranceAccepted.
- Failure: Returns error details.
Workflow Example
1. Execute get-airports with the subscription key (if required).
2. Use the response to populate an airport selection interface.
Supported Codes Retrieval
Action
get-languages
Purpose
Retrieves supported languages for airport information.
Parameters
- Optional:
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with supported languages.
- Failure: Returns a JSON object with supported languages.
Workflow Example
1. Execute get-languages with the subscription key (if required).
2. Use the response to configure language options in a UI.
Localization Data Retrieval
Action
get-iata-destinations
Purpose
Retrieves destinations served by a specific airport, filtered by date range and minimum departures.
Parameters
- Required:
- iata: IATA code of the airport (string, e.g., ARN).
- Optional:
- startMonth: Starting month (integer, default: 0).
- endMonth: Ending month (integer, default: 11).
- minimumDepartures: Minimum number of departures (integer, default: 0).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful: Returns a JSON object with destination details.
- Failure:Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-iata-destinations with iata=ARN, startMonth=0, endMonth=11.
2. Display destinations for travel planning or marketing.
Parking Lots Retrieval
Action
get-iata-parkinglots
Purpose
Retrieves parking lot information for a specific airport, filtered by date range.
Parameters
- Required:
- iata: IATA code of the airport (string, e.g., ARN).
- Optional:
- startDate: Start date in RFC 3339 format (string, e.g., 2025-05-09T00:00:00Z).
- endDate: End date in RFC 3339 format (string, e.g., 2025-05-10T00:00:00Z).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with parking lot details.
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-iata-parkinglots with iata=ARN, startDate=2025-05-09T00:00:00Z.
2. Use the response to display parking availability.
Shops Retrieval
Action
get-iata-shops
Purpose
Retrieves shop information for a specific airport, with language support.
Parameters
- Required:
- iata: IATA code of the airport (string, e.g., ARN).
- Optional:
- langcode: Language code (string, default: en).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful: Returns a JSON object with shop details.
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
Execute get-iata-shops with iata=ARN, langcode=en.
Display shop information for traveler convenience.
Restaurants Retrieval
Action
get-iata-restaurants
Purpose
Retrieves restaurant information for a specific airport, with language support.
Parameters
- Required:
- iata: IATA code of the airport (string, e.g., ARN).
- Optional:
- langcode: Language code (string, default: en).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with restaurant details.
- Failure: Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-iata-restaurants with iata=ARN, langcode=en.
2. Display restaurant options for travelers.
Services Retrieval
Action
get-iata-services
Purpose
Retrieves service information (e.g., lounges, Wi-Fi) for a specific airport, with language support.
Parameters
- Required:
- iata: IATA code of the airport (string, e.g., ARN).
- Optional:
- langcode: Language code (string, default: en).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with service details.
- Failure:Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-iata-services with iata=ARN, langcode=en.
2. Display available services for traveler convenience.
Airlines Retrieval
Action
get-airlines
Purpose
Retrieves airline information for Swedavia airports, filtered by airport or flight direction.
Parameters
- Optional:
- airport: IATA code of the airport (string, e.g., ARN).
- direction: Flight direction (string, e.g., arrival or departure).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful: Returns a JSON object with airline details.
- Failure:Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-airlines with airport=ARN, direction=departure.
2. Display airline information for operational or traveler use.
Airport Wait Times Retrieval
Action
get-airports-airport
Purpose
Retrieves projected wait times for a specific airport (e.g., security or check-in).
Parameters
- Required:
- airport: IATA code of the airport (string, e.g., ARN).
- Optional:
- ConcurrencyVersion: Version for concurrency control (string).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with wait time details.
- Failure:Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-airports-airport with airport=ARN.
2. Display wait times to inform travelers.
Flight-Specific Wait Times Retrieval
Action
get-airports-airport-flights
Purpose
Retrieves wait time information for specific flights at an airport.
Parameters
- Required:
- airport: IATA code of the airport (string, e.g., ARN).
- Optional:
- flightid: Flight number (string, e.g., SK007).
- date: Date in RFC 3339 format (string, e.g., 2025-05-09T00:00:00Z).
- subscription-key: API subscription key for authentication (string).
Configuration
Ensure the connector is configured with the correct base URL.
Output
- Successful:Returns a JSON object with flight-specific wait time details.
- Failure:Returns error codes (400: Bad Request, 500: Internal Server Error).
Workflow Example
1. Execute get-airports-airport-flights with airport=ARN, flightid=SK007.
2. Use the response to inform passengers of expected wait times.
Workflow Creation with the Swedavia Connector
Example Workflow: Airport Information and Flight Tracking
Retrieve Airport List
- Use get-airports to fetch Swedavia airports.
- Identify target airports (e.g., ARN).
Query Flight Information
- Execute the getDeparturesInfo action with airportIATA=ARN and date=2025-05-09 to fetch departure data.
- Execute the getArrivalsInfo action with airportIATA=ARN and date=2025-05-09 to fetch arrival data.
- Process the response to display flight schedules in a dashboard.
Perform Flight Query
- Execute the getQuery action with filter=airport eq ‘ARN’ and flightId eq ‘SK007’ to track a specific flight.
- Save the continuationtoken for retrieving updated flight data.
Enhance UI with Airport Details
- Execute the get-iata-shops, get-iata-restaurants, and get-iata-services actions with iata=ARN and langcode=en to fetch shop, restaurant, and service data.
- Integrate the data into a traveler app for improved user experience
Monitor Wait Times
- Execute the get-airports-airport and get-airports-airport-flights actions with airport=ARN to fetch wait time data.
- Use the data to inform travelers about expected wait times at the airport.
Pricing
iSolution logo - white - transparent 250 px