TABLE OF CONTENTS

We use various technologies and processes to secure the information stored on the DerbySoft servers. Data encryption, access limitation to system components and customer credit data, necessary tracking, and monitoring are used to ensure security. Based on AWS services, DerbySoft builds an isolated data environment that fully complies with PCI (Payment Card Industry) security compliance requirements, which can effectively reduce the risk of data theft, identity fraud, and unauthorized transactions.


The document is here for reference only and as an example of how DerbySoft is aware and staying on top of such things in the industry.

To connect to the DerbySoft Ticket APIs, you have to use AuthZ and have a client credential that includes Client ID and Client Secret.

Credentials Generation Flow

 

AuthZ Urls by Environments:

UAT Environment:

https://ticket-distributor-public.derbysoft-test.com/ticket-distributor-authorizer/token


Production Environment:

The URLs will be provided via Email 


REQUEST

Request Header

LevelField Name

Data Type

Required


Description
Example

1Authorization*StringYBase64 encoded client credential hereBasic base64(client_id:client_secret)
1Content-Type*StringYMust be form URL encoded application/x-www-form-urlencoded

2.3.2 Request Body(Form URL Encoded)

Level

Field Name

Data Type

Required

Description

Example

1grant_type*StringYMust be client_credentialsclient_credentials

Request Example

Request Example 
Post https://ticket-distributor-public.derbysoft-test.com/ticket-distributor-authorizer/token

RESPONSE

Response schema

Level

Field Name

Data Type

Required

Description

Example

1access_token*stringY

1scopestringNAll by defaultshop.all reservation.all product.all livecheck.all
1token_type*stringY
Bearer
1expires_in*stringY
 28800

Response Example

Response Example 
{
  "access_token": "***Token Here***",
  "scope": "shop.all reservation.all product.all livecheck.all",
  "token_type": "Bearer",
  "expires_in": 28800
}


Note: The “authorization” is made up of “Bearer” and “access_token”.  When you call the specific API, please add “Bearer” and space “ “ as the prefix of “access_token”.
For example: Bearer eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJURVNUIiwiYXVkIjoiVEVTVCIsIm5iZiI6MTc1NTIyNTA5MSwic2NvcGUiOlsic2hvcC5hbGwiLCJyZXNlcnZhdGlvbi5hbGwiLCJwcm9kdWN0LmFsbCIsImxpdmVjaGVjay5hbGwiXSwiaXNzIjoiaHR0cHM6Ly93d3cuZGVyYnlzb2Z0LmNvbSIsImV4cCI6MTc1NTI1Mzg5MSwiaWF0IjoxNzU1MjI1MDkxLCJqdGkiOiIwMWU0YzZhZi1iYTk2LTQxOWQtYWNlMy00MTcyNThmYjQ3YjciLCJkaXMiOiJURVNUIn0.hJRqIvPySbtlYLz4u6vtc5Vx_1Uz3hdrkabRU4dwoQfcUAmoRheN85vtqHE5J7L3uk-risfZCymrtRkJJu--JvgEm8Clj-jQuVqVys3S1f3zkzJVoBH6W1LhUxrRsB-9l6tya-tOJAzxMqtlX1ZeY1EgLKibTT3ZE-rKs20V2VzgyWKrr82iUG2hLfANdpFE9z2BAfUE9KcfbGbMg8MqhjVinHa4oFjXY7xw-QsTLq8WccXD6VFY_cIB98EJJ6bTJy6HPUFRQhNaEBo7SpW8LAZ8r6IfD-O0a1tYcJ6ULFsc9sBc0VZ8xhDb2pKZTqezviOf9T288UQIAJapQRMRaA