ROroutable
Receivables

Receivable Creation Failed

A receivable.creation_failed event is fired when creation of a Receivable fails during processing, for example, due to a failure to sync with your accounting software.

postWebhookreceivable.creation_failed

Headers

Routable-Signaturestring

An HMAC-SHA256 hash of the value of Routable-Signature-Timestamp, a period, and the raw JSON webhook request body. See https://developers.routable.com/docs/webhooks for details and code samples describing how to decrypt and validate this value.

Routable-Signature-Timestampstring date-time

A timestamp in GMT. Webhook events where the timestamp is more than five minutes old, or in the future, must be rejected by your code with a 401 Unauthorized.

Payload

event_namestring required

The event that triggered the webhook.

event_resource'company' | 'item' | 'payable' | 'payment_method' | 'receivable' | 'risk_report' | 'tax_form' | 'test' required

The type of resource a webhook references:

ValueResource
companyCompany
itemdeprecated
payablePayable
payment_methodPaymentMethod
receivableReceivable
risk_reportComplianceCheck
tax_formTaxForm
testN/A
object_idstring uuid required

The ID of the resource associated with this event.

Response

Return a 200 OK status with no body to indicate that the webhook was processed successfully.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.