Custom Program
Implementing

In order to integrate with the Events API, you'll need to host an API endpoint for Galileo to send messages to. The connection details of the endpoint will need to be registered with Galileo.

Messages are sent as standard HTTP POST requests over SSL. The collection of data that makes up the message is contained as name/value pairs within the POST body. Additionally, different message categories are posted to different paths on the configured endpoint.

Messages are posted to the base URL configured with Galileo plus the category. For example: with the base URL configured at https://example.gpsrv.com/alerts-endpoint/, 

  • AccountEvent messages would be posted to https://example.gpsrv.com/alerts-endpoint/AccountEvent
  • Authorization messages would be posted to https://example.gpsrv.com/alerts-endpoint/Authorization
  • Transaction messages would be posted to https://example.gpsrv.com/alerts-endpoint/Transaction
  • Settlement messages would be posted to https://example.gpsrv.com/alerts-endpoint/Settlement

 

Below is the sample POST of an Authorization message:

POST /alerts-endpoint/Authorization HTTP/1.1
Host: example.gpsrv.com
Encryption-Type: HMAC-SHA256
Content-Length: 348
User-Agent: python-requests/2.9.1
Connection: keep-alive
Signature: rINogDh6RL6EDw+XCiNMKiDCchfZ+kUNJhHJuThssYY=
Accept: */*
Date: 20170504:141752UTC
Content-Type: application/x-www-form-urlencoded
User-Id: galileo
Accept-Encoding: gzip, deflate
 
tran_type=auth&network=D&prn=199999999998&mcc=6011&prod_id=5043&otype=W&timestamp=2017-0504+14%3A17%3A51+MST

In the above example, the message is an Authorization with the message type of 'auth'. The customer's product ID and payment reference number (PRN) are included, as well as other details of the event.