Goelett

Authentication

Authenticate user in Goelett

Cart

Views the cart.

Gets the cart.

Dictionary

Gets all currencies supported by maya sbt

Gets all countries supported by maya sbt

Gets all company custom fields defined in traveller context in maya sbt

Gets all company job positions defined in the maya sbt

Gets all loyalty programs supported in maya sbt

Gets all railway stations supported in maya sbt

Gets company structure

Healthcheck

Basic ping

Search

Initializes the search rail.

Initializes the search air.

Initializes the search car.

Initializes the search hotel.

Travellers

Create travellers bulk

Update travellers bulk

[Obsolete] Creates travellers' profiles in maya sbt

[Obsolete] Post update of users profiles

[Obsolete] Patch update of travellers profiles

Deletes travellers' profiles in maya sbt

Gets travellers' profiles in maya sbt

Gets travellers' list in maya sbt

Get All travellers

Updates travellers' pools in maya sbt

Workflowapproval

Approves trip.

Rejects trip.

MAYA SBT API

Goelett SBT API 1.1

Production

<p class="slate-p " >The Authentication section of the Goelett SBT API allows you to securely authenticate and access resources within the API. By making requests to the authentication endpoint, you can obtain an access token that will grant you authorized access to the API.</p><p class="slate-p " >Use this endpoint to authenticate your application and generate an access token. Once you have obtained an access token, you can include it in the header of subsequent API requests to authenticate and authorize access to protected resources.</p><p class="slate-p " >Authentication is a crucial step in integrating with the Goelett SBT API. It ensures that only authorized users and applications can interact with the API and perform actions on behalf of authenticated users.</p><p class="slate-p " >To authenticate, simply make a POST request to the authentication endpoint with your application credentials. The endpoint will validate your credentials and return an access token if the authentication is successful.</p><p class="slate-p " >Keep in mind that the access token has an expiration time. After the token expires, you will need to re-authenticate and obtain a new access token.</p><p class="slate-p " >It is important to securely store and handle the access token. Treat it as a sensitive piece of information and avoid exposing it to unauthorized individuals or storing it in an insecure manner.</p><p class="slate-p " >By successfully authenticating and obtaining an access token, you can seamlessly integrate with the Goelett SBT API and access its various resources, enabling you to build powerful applications and leverage the functionality provided by the API.</p><p class="slate-p " ></p>

The Authentication section of the Goelett SBT API allows you to securely authenticate and access resources within the API. By making requests to the authentication endpoint, you can obtain an access token that will grant you authorized access to the API.

Use this endpoint to authenticate your application and generate an access token. Once you have obtained an access token, you can include it in the header of subsequent API requests to authenticate and authorize access to protected resources.

Authentication is a crucial step in integrating with the Goelett SBT API. It ensures that only authorized users and applications can interact with the API and perform actions on behalf of authenticated users.

To authenticate, simply make a POST request to the authentication endpoint with your application credentials. The endpoint will validate your credentials and return an access token if the authentication is successful.

Keep in mind that the access token has an expiration time. After the token expires, you will need to re-authenticate and obtain a new access token.

It is important to securely store and handle the access token. Treat it as a sensitive piece of information and avoid exposing it to unauthorized individuals or storing it in an insecure manner.

By successfully authenticating and obtaining an access token, you can seamlessly integrate with the Goelett SBT API and access its various resources, enabling you to build powerful applications and leverage the functionality provided by the API.

<p class="slate-p " >The Cart API section provides functionality for managing shopping carts in the Goelett SBT system. With this API, you can retrieve information about a specific cart, including its contents and total price. You can also create new carts, update existing ones, and delete them when they are no longer needed. This API is essential for any application or system that requires shopping cart functionality, such as e-commerce platforms or order management systems. Additionally, the Cart API supports pagination, allowing you to retrieve carts in batches rather than all at once, which can be useful for optimizing performance.</p><p class="slate-p " ></p>

The Cart API section provides functionality for managing shopping carts in the Goelett SBT system. With this API, you can retrieve information about a specific cart, including its contents and total price. You can also create new carts, update existing ones, and delete them when they are no longer needed. This API is essential for any application or system that requires shopping cart functionality, such as e-commerce platforms or order management systems. Additionally, the Cart API supports pagination, allowing you to retrieve carts in batches rather than all at once, which can be useful for optimizing performance.

<p class="slate-p " >The GET Dictionary API section provides access to the Goelett SBT API 1.1 dictionary endpoint. This endpoint allows you to retrieve information from the dictionary database.</p><p class="slate-p " >With this API, you can retrieve definitions, synonyms, antonyms, and other relevant information for words or phrases. It is a valuable resource for content creators, language learners, and anyone who needs to work with textual data.</p><p class="slate-p " >The GET Dictionary API supports various useful features such as searching for exact matches, fuzzy search, and wildcard search. These features enhance the flexibility and accuracy of your searches, ensuring you can find the information you need.</p><p class="slate-p " >Additionally, this API supports pagination, allowing you to retrieve large result sets in manageable chunks. This is particularly helpful when working with extensive dictionaries or when you need to limit the number of results returned.</p><p class="slate-p " >To use the GET Dictionary API, simply make a GET request to the designated endpoint. You can specify search parameters to filter the results based on your needs. The response will contain the requested information in a structured format, making it easy to parse and integrate into your application.</p><p class="slate-p " >Whether you are a developer looking to integrate word-related functionality into your application or a non-technical user in need of language resources, the GET Dictionary API section provides a straightforward and intuitive way to access and leverage the Goelett SBT API 1.1 dictionary endpoint.</p><p class="slate-p " ></p>

The GET Dictionary API section provides access to the Goelett SBT API 1.1 dictionary endpoint. This endpoint allows you to retrieve information from the dictionary database.

With this API, you can retrieve definitions, synonyms, antonyms, and other relevant information for words or phrases. It is a valuable resource for content creators, language learners, and anyone who needs to work with textual data.

The GET Dictionary API supports various useful features such as searching for exact matches, fuzzy search, and wildcard search. These features enhance the flexibility and accuracy of your searches, ensuring you can find the information you need.

Additionally, this API supports pagination, allowing you to retrieve large result sets in manageable chunks. This is particularly helpful when working with extensive dictionaries or when you need to limit the number of results returned.

To use the GET Dictionary API, simply make a GET request to the designated endpoint. You can specify search parameters to filter the results based on your needs. The response will contain the requested information in a structured format, making it easy to parse and integrate into your application.

Whether you are a developer looking to integrate word-related functionality into your application or a non-technical user in need of language resources, the GET Dictionary API section provides a straightforward and intuitive way to access and leverage the Goelett SBT API 1.1 dictionary endpoint.

<p class="slate-p " >The Healthcheck API endpoint in the Goelett SBT API 1.1 allows you to check the status and health of the SBT system. This endpoint can be used to ensure that the system is functioning properly and ready to process requests. It provides information about the overall health of the system, including its availability, performance, and any potential issues.</p><p class="slate-p " >By making a request to this endpoint, you can receive a response that indicates whether the system is healthy or not. This can be especially useful for monitoring purposes or when troubleshooting any issues that may arise during integration.</p><p class="slate-p " >The Healthcheck API endpoint does not require any specific parameters or additional input. Simply making a GET request to this endpoint will provide you with the necessary information about the system&apos;s health status.</p><p class="slate-p " >Please note that the response from this endpoint may vary depending on the current state of the system. It is important to handle different response scenarios appropriately in your application to ensure seamless integration with the Goelett SBT API 1.1.</p><p class="slate-p " >Overall, the Healthcheck API endpoint is designed to make API integration straightforward by providing a clear and concise way to check the health of the system. It allows you to quickly determine whether the SBT system is functioning properly and ready to handle requests, ensuring a smooth and reliable integration experience.</p><p class="slate-p " ></p>

The Healthcheck API endpoint in the Goelett SBT API 1.1 allows you to check the status and health of the SBT system. This endpoint can be used to ensure that the system is functioning properly and ready to process requests. It provides information about the overall health of the system, including its availability, performance, and any potential issues.

By making a request to this endpoint, you can receive a response that indicates whether the system is healthy or not. This can be especially useful for monitoring purposes or when troubleshooting any issues that may arise during integration.

The Healthcheck API endpoint does not require any specific parameters or additional input. Simply making a GET request to this endpoint will provide you with the necessary information about the system's health status.

Please note that the response from this endpoint may vary depending on the current state of the system. It is important to handle different response scenarios appropriately in your application to ensure seamless integration with the Goelett SBT API 1.1.

Overall, the Healthcheck API endpoint is designed to make API integration straightforward by providing a clear and concise way to check the health of the system. It allows you to quickly determine whether the SBT system is functioning properly and ready to handle requests, ensuring a smooth and reliable integration experience.

<p class="slate-p " >The Search API endpoint allows you to search for specific information within the Goelett SBT system. This feature is particularly useful when you need to locate specific data quickly and efficiently. With the Search API, you can easily find relevant information by providing search parameters such as keywords, filters, or specific criteria.</p><p class="slate-p " >This API endpoint supports a wide range of use cases, including searching for specific items, retrieving a list of matching results, or even narrowing down the search by applying filters. It is designed to provide flexible search options to meet your specific needs.</p><p class="slate-p " >One special feature of the Search API is the ability to perform advanced searches using complex queries. This allows you to combine multiple search parameters and apply logical operators to refine your search results. You can use operators such as AND, OR, and NOT to create more precise queries.</p><p class="slate-p " >Please note that the Search API may return a large number of results depending on the search parameters used. To optimize performance and minimize the response size, you can specify pagination parameters to retrieve results in smaller, manageable chunks.</p><p class="slate-p " >The Search API is an essential tool for integrating the Goelett SBT system with your own applications or services. Its versatility and powerful search capabilities make it easier to locate and retrieve the information you need efficiently.</p><p class="slate-p " ></p>

The Search API endpoint allows you to search for specific information within the Goelett SBT system. This feature is particularly useful when you need to locate specific data quickly and efficiently. With the Search API, you can easily find relevant information by providing search parameters such as keywords, filters, or specific criteria.

This API endpoint supports a wide range of use cases, including searching for specific items, retrieving a list of matching results, or even narrowing down the search by applying filters. It is designed to provide flexible search options to meet your specific needs.

One special feature of the Search API is the ability to perform advanced searches using complex queries. This allows you to combine multiple search parameters and apply logical operators to refine your search results. You can use operators such as AND, OR, and NOT to create more precise queries.

Please note that the Search API may return a large number of results depending on the search parameters used. To optimize performance and minimize the response size, you can specify pagination parameters to retrieve results in smaller, manageable chunks.

The Search API is an essential tool for integrating the Goelett SBT system with your own applications or services. Its versatility and powerful search capabilities make it easier to locate and retrieve the information you need efficiently.

<p class="slate-p " >The Travellers API section allows you to retrieve information about travellers. This API endpoint provides various functionalities related to travellers, including retrieving their profile information, contact details, and travel history.</p><p class="slate-p " >By using this API, you can easily integrate traveller-related functionality into your application or system. Whether you need to display traveller profiles, create custom reports based on travel history, or implement features related to contact information, the Travellers API endpoint has you covered.</p><p class="slate-p " >Additionally, this API section includes special features and considerations to enhance your integration experience. You can leverage filters and sorting options to retrieve specific subsets of travellers or organize the results according to your needs. The API also supports pagination, allowing you to efficiently handle large amounts of traveller data.</p><p class="slate-p " >Whether you&apos;re a developer or a non-technical user, integrating the Travellers API section into your project will enable you to seamlessly access and manage traveller information. With its clear documentation and straightforward functionality, integrating this API will be a breeze.</p><p class="slate-p " ></p>

The Travellers API section allows you to retrieve information about travellers. This API endpoint provides various functionalities related to travellers, including retrieving their profile information, contact details, and travel history.

By using this API, you can easily integrate traveller-related functionality into your application or system. Whether you need to display traveller profiles, create custom reports based on travel history, or implement features related to contact information, the Travellers API endpoint has you covered.

Additionally, this API section includes special features and considerations to enhance your integration experience. You can leverage filters and sorting options to retrieve specific subsets of travellers or organize the results according to your needs. The API also supports pagination, allowing you to efficiently handle large amounts of traveller data.

Whether you're a developer or a non-technical user, integrating the Travellers API section into your project will enable you to seamlessly access and manage traveller information. With its clear documentation and straightforward functionality, integrating this API will be a breeze.

Creates users. In the request you can send a list of users to create. Max per request: 50.

Field name

Type

Examples

<p class="slate-p " >[PUT] /api/travellers/bulk</p><p class="slate-p " >Updates users. In the request you can send a list of users to create. Max per request: 50.</p><p class="slate-p " >The request structure, required fields and all supported field are the same as in the <a href="6538d9b3d08d00bb91f85827/67d178261d32baf48150ee56" target=""><em class="slate-italic"><strong class="slate-bold">Create travellers bulk</strong></em></a> endpoint.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Updates users. In the request you can send a list of users to create. Max per request: 50.

The request structure, required fields and all supported field are the same as in the 

<h3 class="slate-h3 " >OBSOLETE. Use Create travellers bulk - [POST] /api/travellers/bulk</h3><p class="slate-p " >
The &quot;post /api/travellers/create&quot; API endpoint is used to create travellers profiles in the Goelett system. This functionality allows users to create new profiles for travellers with various information such as login credentials, personal details, addresses, contacts, loyalties, documents, flight preferences, rail preferences, nominated arrangers, nominated approvers, and more.</p><p class="slate-p " >The API request should include the necessary parameters to populate the travellers&apos; profiles. Upon successful creation of the profile, the API will return a status code of 200 along with the details of the created traveller, including their login, external ID, email, and other relevant information. The response also includes a message and status code from the system to indicate the success of the operation.</p><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

OBSOLETE. Use Create travellers bulk - [POST] /api/travellers/bulk


The "post /api/travellers/create" API endpoint is used to create travellers profiles in the Goelett system. This functionality allows users to create new profiles for travellers with various information such as login credentials, personal details, addresses, contacts, loyalties, documents, flight preferences, rail preferences, nominated arrangers, nominated approvers, and more.

The API request should include the necessary parameters to populate the travellers' profiles. Upon successful creation of the profile, the API will return a status code of 200 along with the details of the created traveller, including their login, external ID, email, and other relevant information. The response also includes a message and status code from the system to indicate the success of the operation.

AuthToken

The list of traveller profiles that were successfully created in Maya SBT.

CreatedTravellers

The state of the response, providing additional information about the status of the request.

ResponseState

<h3 class="slate-h3 " >OBSOLETE. Use Update travellers bulk - [PUT] /api/travellers/bulk</h3><p class="slate-p " >This API endpoint allows you to update the profiles of travellers in the Goelett system. By making a POST request to this endpoint, you can easily modify the information stored for each traveller. This functionality is especially useful when you need to keep traveller profiles up-to-date with the latest information.</p><p class="slate-p " >When using this API endpoint, it is important to ensure that the necessary body parameters are provided. These parameters should include the details of the travellers you wish to update and parameters you wish to keep unchanged. All existing data which won&apos;t be present in API request will be removed.  It is recommended to double-check the parameters list to ensure that all required information is included.</p><p class="slate-p " >Endpoint is recomended to be used for small packages. </p><p class="slate-p " >Overall, this API endpoint simplifies the process of updating traveller profiles in the Goelett system. It provides a straightforward solution for integrating your application or system with the necessary functionality to keep traveller information accurate and up-to-date.</p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

OBSOLETE. Use Update travellers bulk - [PUT] /api/travellers/bulk

This API endpoint allows you to update the profiles of travellers in the Goelett system. By making a POST request to this endpoint, you can easily modify the information stored for each traveller. This functionality is especially useful when you need to keep traveller profiles up-to-date with the latest information.

When using this API endpoint, it is important to ensure that the necessary body parameters are provided. These parameters should include the details of the travellers you wish to update and parameters you wish to keep unchanged. All existing data which won't be present in API request will be removed.  It is recommended to double-check the parameters list to ensure that all required information is included.

Endpoint is recomended to be used for small packages. 

Overall, this API endpoint simplifies the process of updating traveller profiles in the Goelett system. It provides a straightforward solution for integrating your application or system with the necessary functionality to keep traveller information accurate and up-to-date.

The updated information for the travellers' profiles in Maya SBT.

The updated details of the travellers' profiles in Maya SBT.

UpdatedTravellers

Any errors or issues encountered during the API request.

Errors

<h3 class="slate-h3 " >OBSOLETE. Use Update travellers bulk - [PUT] /api/travellers/bulk</h3><p class="slate-p " >This API endpoint allows you to update the profiles of travellers in Goelett. You can use this functionality to modify various aspects of a traveller&apos;s profile, such as their login details, contact information, preferences, and more. In contrast to post update method each request should include only data to be updated. If some data should be deleted from Goelett “null” should be placed in given field. </p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

This API endpoint allows you to update the profiles of travellers in Goelett. You can use this functionality to modify various aspects of a traveller's profile, such as their login details, contact information, preferences, and more. In contrast to post update method each request should include only data to be updated. If some data should be deleted from Goelett “null” should be placed in given field. 

An array of traveller profiles to be updated.

This parameter returns the updated information of the travellers' profiles in Maya SBT.

This parameter contains any errors or issues encountered during the update of the travellers' profiles in Maya SBT.

This parameter indicates the state of the response and can have values like "success" or "error".

<p class="slate-p" placeholder="Type / for widgets">This API endpoint allows you to delete travellers&apos; profiles in Maya SBT. By making a POST request to &quot;/api/travellers/delete&quot;, you can remove the profiles of travellers in the system.</p><p class="slate-p" placeholder="Type / for widgets">Please note that this API requires the following body parameters: &quot;TravellerLogin&quot; and &quot;CompanyCode&quot;. These parameters must be included in the request for successful profile deletion.</p><p class="slate-p" placeholder="Type / for widgets">After making the request, you will receive a response with a status code of 200. The response will include the following parameters: &quot;ResponseState.Message&quot;, &quot;ResponseState.Status&quot;, and &quot;ResponseState&quot;. These parameters provide information about the state and status of the deletion process.</p><p class="slate-p" placeholder="Type / for widgets">By utilizing this API endpoint, you can easily integrate profile deletion functionality into your application or system.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

This API endpoint allows you to delete travellers' profiles in Maya SBT. By making a POST request to "/api/travellers/delete", you can remove the profiles of travellers in the system.

Please note that this API requires the following body parameters: "TravellerLogin" and "CompanyCode". These parameters must be included in the request for successful profile deletion.

After making the request, you will receive a response with a status code of 200. The response will include the following parameters: "ResponseState.Message", "ResponseState.Status", and "ResponseState". These parameters provide information about the state and status of the deletion process.

By utilizing this API endpoint, you can easily integrate profile deletion functionality into your application or system.

The username or email associated with the traveller's account. This parameter is required to identify the traveller profile that needs to be deleted.

TravellerLogin

The code representing the company associated with the traveller profiles. This parameter is required to ensure that the correct company's traveller profiles are targeted for deletion.

CompanyCode

The state of the API response. This parameter is returned in the API response and indicates whether the delete operation was successful or encountered an error.

<p class="slate-p " >This API endpoint allows you to retrieve profiles of travellers in the Maya SBT system. By making a POST request to this endpoint, you can access detailed information about travellers, including their login details, profile ID, external ID, email, last name, first name, title, password, address, birth date, nationality, currency code, language code, company code, job position code, roles, custom fields, contacts, loyalty program details, payment card information, documents, flight preferences, rail preferences, nominated arrangers, nominated approvers, activity status, special assistance requirements, authentication mode, preferred approver, and the ability to update specific fields.</p><p class="slate-p " >With this API, you can easily integrate the retrieval of traveller profiles into your own systems or applications. This allows for seamless access to relevant traveller information and streamlines various processes such as booking, reporting, and managing traveller preferences.</p><p class="slate-p " >It&apos;s important to note that the response from this endpoint will include a status code, indicating the success or failure of the request, as well as various parameters containing the retrieved traveller profile details.</p><p class="slate-p " >Please refer to the other sections of the documentation for specific examples and details on how to use this API endpoint effectively.</p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

This API endpoint allows you to retrieve profiles of travellers in the Maya SBT system. By making a POST request to this endpoint, you can access detailed information about travellers, including their login details, profile ID, external ID, email, last name, first name, title, password, address, birth date, nationality, currency code, language code, company code, job position code, roles, custom fields, contacts, loyalty program details, payment card information, documents, flight preferences, rail preferences, nominated arrangers, nominated approvers, activity status, special assistance requirements, authentication mode, preferred approver, and the ability to update specific fields.

With this API, you can easily integrate the retrieval of traveller profiles into your own systems or applications. This allows for seamless access to relevant traveller information and streamlines various processes such as booking, reporting, and managing traveller preferences.

It's important to note that the response from this endpoint will include a status code, indicating the success or failure of the request, as well as various parameters containing the retrieved traveller profile details.

Please refer to the other sections of the documentation for specific examples and details on how to use this API endpoint effectively.

TravellerLogins

The state of the response received from the API. It provides additional information about the outcome of the API request, such as success, failure, or any other relevant states.

<p class="slate-p " >This API endpoint allows you to retrieve a list of travellers in the Goelett SBT system. By making a POST request to /api/travellers/list, you can easily access the information you need. The response will include details such as the login information, company code, GDS profile locator, and active status of each traveller. Additionally, you will receive a response state containing a message and status. This API is designed to make integration straightforward, providing you with the necessary functionality to efficiently retrieve travellers&apos; data.</p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

This API endpoint allows you to retrieve a list of travellers in the Goelett SBT system. By making a POST request to /api/travellers/list, you can easily access the information you need. The response will include details such as the login information, company code, GDS profile locator, and active status of each traveller. Additionally, you will receive a response state containing a message and status. This API is designed to make integration straightforward, providing you with the necessary functionality to efficiently retrieve travellers' data.

The body parameter "CompanyCode" is used to specify the company code associated with the travellers' list retrieval. It helps to filter and retrieve the relevant travellers' list based on the provided company code.

The body parameter "IsFullStructure" is used to specify whether the response should include the full structure of the travellers' list. Set this parameter to "true" if the full structure is required, otherwise set it to "false" to receive only the essential information.

IsFullStructure

The response parameter "Travellers" provides the list of travellers retrieved from the Maya SBT API.

The response parameter "ResponseState" indicates the state of the response for the travellers' list retrieval from the Maya SBT API. It can have different values such as "success" or "error" to signify the outcome of the request.

<p class="slate-p " >This API endpoint allows you to retrieve the profiles of travellers in the Maya SBT system. By making a POST request to /api/travellers/getgds, you can fetch information such as the login details, company code, GDS profile locator, and active status for each traveller. The response will include the travellers&apos; profiles along with a message and status indicating the success of the request. This API is designed to simplify the integration process and provide easy access to traveller data within the Maya SBT system.</p><p class="slate-p " ></p>

This API endpoint allows you to retrieve the profiles of travellers in the Maya SBT system. By making a POST request to /api/travellers/getgds, you can fetch information such as the login details, company code, GDS profile locator, and active status for each traveller. The response will include the travellers' profiles along with a message and status indicating the success of the request. This API is designed to simplify the integration process and provide easy access to traveller data within the Maya SBT system.

The company code associated with the traveller's profile.

This parameter specifies the response containing the profiles of the travellers retrieved from Maya SBT.

This parameter signifies the state of the response received for the request to retrieve travellers' profiles from Maya SBT.

<p class="slate-p " >This API endpoint allows you to retrieve a list of travellers in the Goelett SBT system. By making a POST request to /api/travellers/getAll, you can easily access the information you need. </p><p class="slate-p " >The response will include details such:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Login</div></li><li class="slate-li " ><div style="position:relative">CompanyCode</div></li><li class="slate-li " ><div style="position:relative">LastName</div></li><li class="slate-li " ><div style="position:relative">FirstName</div></li><li class="slate-li " ><div style="position:relative">Email</div></li><li class="slate-li " ><div style="position:relative">IsActive</div></li><li class="slate-li " ><div style="position:relative">Custom fields</div></li><li class="slate-li " ><div style="position:relative">Roles</div></li><li class="slate-li " ><div style="position:relative">Nominated approvers</div></li></ul><p class="slate-p " ></p>

This API endpoint allows you to retrieve a list of travellers in the Goelett SBT system. By making a POST request to /api/travellers/getAll, you can easily access the information you need. 

The body parameter "CompanyCode" is used to specify the company code associated with the travellers.

The body parameter "BatchNumber" is used to specify the data package number to return. The size of a single package is 10000 users. If the company has less than 10000 users, you can skip this parameter. If the company has more than 10000 , e.g. 25000, then to get all of them we should send 3 requests with BatchNumber = 1, BatchNumber = 2, BatchNumber = 3

BatchNumber

BatchInfo

<p class="slate-p " >This section of the Goelett SBT API allows you to update the pools for travellers in Maya SBT. By making a POST request to this endpoint, you can modify the pools associated with a particular traveller.</p><p class="slate-p " >The API parameters required for this request include the traveller&apos;s login, company code, and the desired pools. The login is used to identify the specific traveller, while the company code ensures the pools are updated for the correct organization. The pools parameter allows you to specify the new pool assignments for the traveller.</p><p class="slate-p " >Upon successful execution of the request, a response with a status code of 200 will be returned. The response will include a message indicating the outcome of the operation, as well as the status of the response itself.</p><p class="slate-p " >This API endpoint provides a straightforward method to update travellers&apos; pools in Maya SBT, making it easy to manage and maintain accurate pool assignments for your users.</p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

This section of the Goelett SBT API allows you to update the pools for travellers in Maya SBT. By making a POST request to this endpoint, you can modify the pools associated with a particular traveller.

The API parameters required for this request include the traveller's login, company code, and the desired pools. The login is used to identify the specific traveller, while the company code ensures the pools are updated for the correct organization. The pools parameter allows you to specify the new pool assignments for the traveller.

Upon successful execution of the request, a response with a status code of 200 will be returned. The response will include a message indicating the outcome of the operation, as well as the status of the response itself.

This API endpoint provides a straightforward method to update travellers' pools in Maya SBT, making it easy to manage and maintain accurate pool assignments for your users.

The TravellerRoles parameter is used to specify the roles of the travellers whose pools need to be updated in Maya SBT. It should contain an array of role IDs.

TravellerRoles

The ResponseState parameter is returned in the response and indicates the state of the response. It can be used to determine if the request was successful or if there were any errors.

<p class="slate-p " >The GET Workflowapproval API endpoint in the Goelett SBT API 1.1 project allows you to retrieve information related to workflow approvals. This endpoint is designed to provide a straightforward way to integrate with the Goelett SBT system and retrieve specific workflow approval details.</p><p class="slate-p " >By making a GET request to this endpoint, you can retrieve information such as the status of a particular workflow approval, the associated user or group responsible for the approval, and any relevant timeline or history related to the approval process.</p><p class="slate-p " >This API endpoint is especially useful for developers and non-technical roles who need to access and track the status of workflow approvals within the Goelett SBT system. Whether you are building a custom dashboard for managers to view approval statuses or integrating the workflow approval data into your own application, this endpoint provides a simple and efficient way to fetch the necessary information.</p><p class="slate-p " >It&apos;s important to note that the Workflowapproval endpoint only supports GET requests, so it is read-only and does not allow for any modifications or updates to the approval status. If you require functionality beyond retrieving approval information, please refer to the other sections of the API documentation for appropriate endpoints.</p><p class="slate-p " >To make the integration process even smoother, the Goelett SBT API 1.1 provides comprehensive documentation with detailed examples and explanations of the response structure, parameters, and any authentication requirements. This ensures that developers and non-technical roles can easily understand and implement the necessary code to interact with the Workflowapproval endpoint.</p><p class="slate-p " >By following the guidelines and resources provided in this documentation, you can confidently integrate with the Goelett SBT system and retrieve workflow approval information with ease.</p><p class="slate-p " ></p>

The GET Workflowapproval API endpoint in the Goelett SBT API 1.1 project allows you to retrieve information related to workflow approvals. This endpoint is designed to provide a straightforward way to integrate with the Goelett SBT system and retrieve specific workflow approval details.

By making a GET request to this endpoint, you can retrieve information such as the status of a particular workflow approval, the associated user or group responsible for the approval, and any relevant timeline or history related to the approval process.

This API endpoint is especially useful for developers and non-technical roles who need to access and track the status of workflow approvals within the Goelett SBT system. Whether you are building a custom dashboard for managers to view approval statuses or integrating the workflow approval data into your own application, this endpoint provides a simple and efficient way to fetch the necessary information.

It's important to note that the Workflowapproval endpoint only supports GET requests, so it is read-only and does not allow for any modifications or updates to the approval status. If you require functionality beyond retrieving approval information, please refer to the other sections of the API documentation for appropriate endpoints.

To make the integration process even smoother, the Goelett SBT API 1.1 provides comprehensive documentation with detailed examples and explanations of the response structure, parameters, and any authentication requirements. This ensures that developers and non-technical roles can easily understand and implement the necessary code to interact with the Workflowapproval endpoint.

By following the guidelines and resources provided in this documentation, you can confidently integrate with the Goelett SBT system and retrieve workflow approval information with ease.

Sections