Transactions postbacks

  1. Introduction
  2. Webservice / API setup
  3. CloudWalk Manager setup
  4. Testing and validation

Introduction

One way to collect transaction logs for analysis and reconciliation purposes is through the API, however, constantly reaching the API can make this process costly. Another option is the postback, where all transactions that go through the CloudWalk structure are automatically sent to your server, webservice, or API. On this page you will learn how to use the postback. Enjoy!

The format of the submitted information follows the same API standard

Webservice / API setup

Your server must meet the following requirements:

  • Be publicly accessible
  • Be able to receive HTTP POST requests (JSON)
  • Respond within 3 seconds

Host example: https://postback-test.herokuapp.com

CloudWalk Manager setup

Authenticated in CloudWalk Manager, access the option My account and then the option Settings:

CloudWalk Manager - My Account

On the settings screen, enter the URL of the webservice / API that will receive the postback:

CloudWalk Manager - Postback URL

Click the button Udpate information and you are done! The next transactions will be sent to your server!

The response from your webservice or API shouldn't exceed 100 characters or it will be truncated.

Testing and validation

After setting up your webservice and configuring the transactions postback, you can validate the setup through the API:

Successful postback transactions:

$ curl -X GET "https://api.cloudwalk.io/v1/transactions?access_token=$TOKEN&postback_status=success"

Failed postback transactions:

$ curl -X GET "https://api.cloudwalk.io/v1/transactions?access_token=$TOKEN&postback_status=failed"

We suggest using the parameters since and until to facilitate the analysis