🔀Webhooks

Getting started

Webhooks are automated messages sent from apps when something happens. They have either payload or message which are sent to a unique URL, essentially the app's phone number or address.

Webhooks VS APIs

Webhooks are event-based. They will run when a specific event occurs in the source app.

APIs are request-based. They operate when requests come from other 3rd party apps.

Ottu Webhooks

Currently, available webhooks for Ottu are only for operation. Webhooks for Ottu have atuo-trigers HTTP calls to configure webhooks when certain event happen, then operation webhooks will start.

Ottu webhooks operations URL

From Ottu dashboard ➡️ administration panel ➡️ Config ➡️ Configuration.

Scroll down to webhooks / URL.

Ottu webhooks operations

There are three Ottu webhooks operation are working:

• Voided

• Captured

• Refunded

Voided operation payload example

Disclosed data

{
"operation": "void",
"amount": "None",
"success": true,
"initiator_pk": null,
"pymt_txn_pk": 4921,
"source": "input",
"is_sandbox": false,
"pg_code": "ottu_pg_auth",
"pg_response": {response from the pg}
}

Captured operation payload example

Disclosed data

{
   "operation":"capture",
   "amount":"7.000",
   "success":true,
   "initiator_pk":null,
   "pymt_txn_pk":4917,
   "source":"input",
   "is_sandbox":false,
   "pg_code":"ottu_pg_kwd",
   "pg_response":{response from the pg}
}

Refunded operation payload example

Disclosed data

{
   "operation":"refund",
   "amount":"6.000",
   "success":true,
   "initiator_pk":null,
   "pymt_txn_pk":4917,
   "source":"input",
   "is_sandbox":false,
   "pg_code":"ottu_pg_kwd",
   "pg_response":{response from the pg}
}