Credentials

We use tokens in the request's header to authenticate the communications. Depending on your use case we have 2 types of authentication. Most of our APIs support both of the below authentication types but Property Apps can do more as they are developed by the property in-house development team.
1
# Property Apps v.s. Marketplace Apps
2
​
3
​
4
# Option 1 - Property Apps
5
# Calling find API using property app integration
6
curl --request GET \
7
--header 'api-key: replace-with-your-property-api-key' \
8
'https://api.stg.goki.travel/v1/travelers/[email protected]'
9
​
10
​
11
# Option 2 - Marketplace Apps
12
# Calling find API using marketplace app integration
13
curl --request GET \
14
--header 'client-token: replace-with-your-marketplace-app-client-token' \
15
--header 'access-token: replace-with-your-test-account-access-token' \
16
'https://api.stg.goki.travel/v1/travelers/[email protected]'
Copied!
Option 1 - Property Apps
You can build apps for your own property/property group. Each property has its own unique api-key to communicate with Goki. These apps are not listed in the Goki marketplace and can be used only in your properties.
Property Apps
Option 2 - Marketplace Apps
Most likely you want to use this type of integration, as you want your app to be listed in the marketplace and used by any property in the world. If you are a PMS integrating with Goki this is the option you need to read.
Marketplace Apps
​

Getting Started

Property Apps

Last modified 1mo ago

Export as PDF

Copy link

Contents

Option 1 - Property Apps

Option 2 - Marketplace Apps