Getting started
- Bókun app store
  - Introduction
  - Building apps
  - Requirements for Public Apps on Bókun App Store
  - Example app
API
- API
  - Access scopes
  - Authenticate with OAuth
  - GraphQL Reference
  - REST API
Webhooks
- Webhooks
  - Creating an endpoint for webhooks
  - Webhook Events
Booking API (REST)
- Documentation
  - Configuring the platform for API usage and authentication
  - Introduction to the data model of products
  - Get product details
  - Checking availability and pricing
  - Booking process
  - Booking questions and answers
  - Checkout
  - Edit booking
  - Cancel booking
  - Error codes
RESTful API for creating, updating and accessing Experience products
- Documentation
  - Introduction and concepts
  - Component overview
  - Component: ACTIVATION
  - Component: ALLOW_CUSTOMIZED_BOOKINGS
  - Component: ATTENTION
  - Component: AVAILABILITY_RULES
  - Component: BOOKING_LABELS
  - Component: BOOKING_QUESTIONS
  - Component: BOOKING_TYPE
  - Component: BOX_SETTINGS
  - Component: CAPACITY_TYPE
  - Component: CATEGORIES
  - Component: COMBO
  - Component: COMMISSION_GROUP_ID
  - Component: CREATED
  - Component: CUSTOM_INPUT_FIELD_VALUES
  - Component: CUTOFF
  - Component: DEFAULT_OPENING_HOURS
  - Component: DESCRIPTION
  - Component: DIFFICULTY_LEVEL
  - Component: DURATION
  - Component: EARLY_BOOKING_LIMIT
  - Component: EXCLUDED
  - Component: EXCLUSIONS
  - Component: EXTERNAL_ID
  - Component: EXTRAS
  - Component: FLAGS
  - Component: GUIDANCE_TYPE
  - Component: ID
  - Component: INCLUDED
  - Component: INCLUSIONS
  - Component: INVENTORY_SETTINGS
  - Component: ITINERARY
  - Component: KEYWORDS
  - Component: KNOW_BEFORE_YOU_GO
  - Component: LAST_MODIFIED
  - Component: LOCATION
  - Component: MAIN_PAX_INFO
  - Component: MEETING_TYPE_SETTINGS
  - Component: MIN_AGE
  - Component: ON_REQUEST_DEADLINE
  - Component: OTHER_PAX_INFO
  - Component: PASS_SETTINGS
  - Component: PHOTOS
  - Component: PRICING
  - Component: PRICING_CATEGORIES
  - Component: PRIVATE_EXPERIENCE
  - Component: RATES
  - Component: REQUIREMENTS
  - Component:RESERVATION_TIMEOUT
  - Component: RETURN_PRODUCT_ID
Channel Manager API
- Channel Manager API Documentation
  - Overview
  - Transport layer and general implementation guidelines
  - Transport / gRPC
  - Transport / REST
  - Channel manager plugin lifecycle
  - Step 1: Plugin registration
  - Step 2: Retrieval of plugin definition
  - Step 3. Plugin configuration
  - Step 4: Product mapping
  - Step 5: Shallow & deep availability searches
  - Step 6: Reservation and booking
  - Step 7: Booking cancellation
  - Step 8: Booking amendment
  - Handling booking failures
  - Security
  - Using the sample plugin
  - Running end-to-end tests
  - Options for reselling products through Channel manager
  - FAQs
  - Appendix
More

Step 3. Plugin configuration

Plugin configuration is actioned by the vendors themselves by going to Settings →Connections →Channel manager→Selecting your plugin from the provided list →Configure plugin on Bókun extranet.

Configuration action is the process of setting values to the parameters, specified in the plugin definition retrieved earlier.

When configuring, extranet UI will present the list of configuration parameters, expressed as form fields - as instructed by the plugin (see Step 2: retrieval of plugin definition for more details). Form field(s) may be left empty only if relevant configuration parameter has required attribute set to false. Fields should also comply to the specified data type.

There is no call made to the plugin upon configuration.

Every subsequent API client call (except getDefinition) will send the configured set of name/value parameters with each request.

This is the first step of getting the API integration done. Plugin can not be registered in Bókun (not even test environment) if getDefinition call is not implemented.

Did this answer your question?

😞

😐

🤩

Step 2: Retrieval of plugin definition Step 4: Product mapping