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.
# Property apps v.s. Marketplace apps# Calling find API using property app integrationcurl --request GET \--header 'api-key: replace-with-your-property-api-key' \'https://api.stg.goki.travel/v1/travelers/[email protected]'# Calling find API using marketplace app integrationcurl --request GET \--header 'client-token: replace-with-your-marketplace-app-client-token' \--header 'access-token: replace-with-your-test-account-access-token' \'https://api.stg.goki.travel/v1/travelers/[email protected]'
You can build apps for your own property/property group. Each property has it's 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.
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.