Clients provide a base URL, hosted by a server in the client's system. Paths are relative to that URL.
As mentioned in the Overview, events are grouped into categories, and posted to the webhook for that category:
- Account Events:
/AccountEvent - Authorization Events:
/Authorization - Settlement Events:
/Settlement - Transaction Events:
/Transaction
Galileo can send the event information as JSON or form data, and Galileo can receive the client response as JSON or XML.
All fields are sent as strings. For example, $500 is sent as "500.00".
Default and optional fields
The fields to include with each event webhook are defined by a template. The fields in the default template are marked as Default in the Fields table on every event page. As you work with Galileo to set up your event webhooks, you start with the default template; then, if necessary, you can add optional fields or remove default fields.
Empty fields
When there is no data to return for a field, the key is still included in the webhook with an empty value. For example, if you receive a BADJ: adj event webhook for a non-ACH transaction, then "ach_trans_id": "" is returned in the webhook.