...
Code Block | ||
---|---|---|
| ||
{ "request_ref": "{{request_ref}}", "request_type": "benefits_intent", "auth": { "type": null, "secure": null, "auth_provider": "Benefits", "route_mode": null }, "transaction": { "mock_mode": "live", "transaction_ref": "{{transaction_ref}}", "transaction_desc": "A random transaction", "transaction_ref_parent": null, "amount": 0, "customer": { "customer_ref": "{{customer_id}}", "firstname": "Uju", "surname": "Usmanu", "email": "ujuusmanu@gmail.com", "mobile_no": "234802343132" }, "meta": { "a_key": "a_meta_value_1", "another_key": "a_meta_value_2" }, "details": { "message": "{{some kain text to trigger the intent or respond to a message}}", "callback_url": "{{a url to post the response to for long running proceses}}", "subsequent_messages": [], //An array of {{message}} elements. Such that if a developer already knowknows the EXACT set of questions that will follow in order to complete an intent, they can preload it, the provider will hold on their behalf and forward to OneChapp as each response is received. USE CASE: Making it possible to have one-shot API calls. e.g. We can then have Appsolute built a single USSD string to trigger pay4me in one shot when its time for retailer self-service "client_id": "{{app_code of the app}}", //optional "sender_id": "{{customer_ref}}", //optional "channel": "OnePipe", //optional } } } |
...