200
or 202
response code is expected. A webhook response should only be determined by your servers ability to receive the incoming notification. Any backend processing or handling of the actual event should not factor into the returned HTTP response.
All changes to API resources will generate webhooks. Your application may choose to react to the subset of events it finds relevant. For example, if your application creates ACH transfers, it may choose to react to webhook events notifying that the status of an ACH transfer was changed.
Webhook objects have a status
: if they are enabled
, then a notification will be issued to the URL. Any other status (error
, disabled
) will not issue a notification. To re-enable a webhook that is in error
or disabled
status, update the status
field to enabled
.
basic_user
and basic_secret
fields, notifications from Treasury Prime will include an additional Authorization
header that is the base64-encoded value of {basic_user}:{basic_secret}
. When the base64 header matches the value your application expects, the request is authentic.
error
statuserror
. No new webhooks will be issued on webhooks in error
status. This happens only for a high volume of failed responses, and is done to prevent other webhook notifications from slowing down.
A webhook can be changed back to enabled
status by updating the status
field to enabled
. This will reset the webhook and new webhooks will now be issued.