Loading...

API docs by

Connect API for Activities (2.14.0)

The Activity Service API is a web service that provides access to a range of single day activities and multi day tours for users. It's primarily designed to allow users to search, view, book, and cancel activities in an efficient and user-friendly manner.

Here are the key functionalities of the API:

  1. Get List of Activities: This endpoint returns a list of all available activities. Each activity comes with basic information like name and description.
  2. Get Activity Description: This endpoint provides a detailed description of a specific activity. It requires the ID of the activity as input.
  3. Check Activity Availability: This feature is integrated within the activity description endpoint. Along with the description, it also shows the current availability status of the activity.
  4. Book an Activity: This endpoint allows users to book a specific activity. It requires the ID of the activity and user details for successful booking.
  5. Cancel Booking: This endpoint allows users to cancel their booking for a specific activity. It requires the ID of the booking to perform the cancellation.

This API is designed to be RESTful, using standard HTTP methods like GET, POST, and DELETE, and it primarily exchanges data in JSON format.

Change History

API VersionDocs VersionChanges
1.031.05.2023Initial version
2.001.03.2025Updated to support multi-day tours
2.128.08.2025Added metadata field to all request schemas
2.210.09.2025Added optional request body with metadata field to cancellation endpoint
2.329.10.2025Added room allocation support for multi-day tours
2.412.11.2025Added optional supplier field to ActivityOffer schema for offer source identification
2.524.11.2025Added forAllPax field to ActivityQuestion and paxRefId field to ActivityBookingActivityAnswer for per-pax questions support
2.627.11.2025Added subName2 through subName5 fields to ActivityServiceCategory for multi-level hierarchy support
2.718.02.2026Added requiredPassengerData and requiredContactData to ActivityOffer for dynamic supplier required data support
2.825.02.2026Added travelAgentEmail, travelAgentFirstName, travelAgentLastName, travelAgencyShortName, travelAgencyEmail to Metadata
2.920.04.2026Made Contract-Id optional, added Login and Password headers as alternative identification method
2.9.120.07.2026Added the missing availabilityStatus property definition to ActivityBookingAvailabilityCheckResponse (it was listed as required but not defined)
2.1005.08.2026Added optional minEndDate and maxEndDate fields to TimeCriteria in the activities search request (POST /v2/activities)
2.1107.08.2026Make availabilityStatus optional
2.1207.09.2026Added optional fareType to ActivityOffer
2.1319.10.2026Added optional nextDepartures to the offer details response (POST /v2/activities/details) for multi-day tours
2.1404.11.2026Added optional pricingPax (PER_PAX, PER_GROUP) to ActivityServiceCategory, stating whether a category price is per traveller or for the whole party

Authentication

All API requests must be made over HTTPS.

Identification can be provided via either:

  • A Contract-Id header identifying the contract configuration
  • Login and Password headers for login-based authentication

The identification method should be agreed with Nezasa before integration development starts. Both methods may be provided simultaneously if required by the integration.

Servers
production mock server
https://connectapi.stg.nezasa.com