Introduction

Mojro Webhooks are HTTP POST methods or the callback URLs. Many events that occur because of the actions by the Mojro users triggers the callbacks automatically. Callbacks contain detailed information about events. The information is sent in JSON format. Consumer needs to register a URL for a specific webbook event once. Every time that event occurs, the callback payload is sent to registered callback.

For example, you can register a webhook URL for the "Delivery Completion" event. Every time a delivery is completed, we will trigger the HTTP post request to the registered webhook URL with detailed json payload about that completed delivery. Likewise, you can register webhook URLs for automatic updates for events throughout the trip lifecycle. For a complete list of Mojro Webhook Events, see the List of Mojro Webhooks Events.

Security

Platform supports API request Signing and all major authorization mechanisms to establish the trust and ensure the data is not manipulated in transit. API key, which is used for request signing (AES 256 Key and HMAC SHA 256 based Request Signing), is available in the consumer portal for developer consumption. In case, API key is compromised, users can regenerate the key in the portal.

Authorization Supported

• No Auth

• API Key Based Auth

• Token Based Auth

• OAuth 2.0