Learn about .p12 Key-Pair and Usage

Ready

We recommend using the Key-Pair method. You will get the Private Key and Public Key from API Keys.zip. You can learn how to make them through the chapter "Make key pair format - create .p12 or jks for your server". Key-Pair in p12 format, usually .p12 will have a file-specific password.

CURL_SSL_BACKEND

• You may change the CURL_SSL_BACKEND if your local environment hanging on the TLS handshake stage, Please refer to document: https://curl.se/libcurl/c/curl_global_sslset.html For example of secure-transport:

export CURL_SSL_BACKEND="secure-transport"

For example of openssl:

export CURL_SSL_BACKEND="openssl"

Request Client Certificate - Submit your certificate for verification by Server

GTR's services require users to bring their own certificates before they can be used.

curl  --location --request GET "https://platform.globaltravelrule.com/integration_check/api/network/test/check" --cert-type P12 --cert ./certificate.p12:'[Your .p12 passphrase]'

CA Certificate Bundle - Verify Response's certificate

The following tests use the cURL program to demonstrate example requests. By default, we skip the response certificate check from GTR. If you have already obtained the client-truststore.pem from the API Keys application, you can manually set it as a trusted certificate.

For example, to skip all response certificate checks, add --insecure flag or -k flag to arguments:

curl  --location --request GET "https://platform.globaltravelrule.com/integration_check/api/network/test/check" \ -k --cert-type P12 --cert ./certificate.p12:'[Your .p12 passphrase]' \ --insecure

For example, to verify all response certificate, add --cacert filename.pem to arguments:

curl  --location --request GET "https://platform.globaltravelrule.com/integration_check/api/network/test/check" \ -k --cert-type P12 --cert ./certificate.p12:'[Your .p12 passphrase]' \ --cacert client-truststore.pem