wallet.linked
event. Certain API requests might create multiple events. For example, when a user first signs in to your environment, we create a user.created
event, and when a user successfully authenticates, we create a user.session.created
event.
userId
’s in the event payload. For instance, when creating users via developer APIs the triggerer will be the developer’s userId and the event payload will contain the id of the created user. This parameter will be undefined
if the event is triggered using an API key.
eventName{resourceType}.{action}
. For example with the event name of user.created
, user
is the resource type and created
is the action performed on the resource. The full list of event names can be retrieved by using the /eventTypes
endpoint in the API here.
environmentIdlive
and sandbox
events.
timestampuser.created
event
Source | Trigger |
---|---|
Developer Dashboard | When you call an API by modifying Dynamic resources in the Developer Dashboard. |
SDK | When a user action in your app or website integrating the SDK results in an API call. |
API | When you call an API directly. |
Events
Endpoint
Enable
x-dynamic-signature-256
header which has a hash signature value, generated from your secret token.
Each webhook has a unique secret token that is used to generate the message signature from the event object. This secret can be found on the webhook detail page in the Developer Dashboard.
ping
event.
messageId
attribute.
Below are the request retry intervals for live environments
messageId
attribute in the event object is a good way to handle this.
user
events, only select those event types. This will reduce the number of messages you receive and the number of messages you need to handle.
x-dynamic-signature-256
header to ensure the message is coming from Dynamic. This is a hash signature value, generated from your secret token.
2XX
HTTP status code the webhook will be automatically disabled. For live environments this is 6 failed attempts per message up to a maximum of 1500 failed messages, and for sandbox environments this is 3 failed attempts per message up to a maximum of 250 failed messages. Note that if any of the message retries are successful it is not counted against the failure limit. The webhook will remain disabled until it is re-enabled manually.
Messages in live environments will be available for 90 days and 30 days for sandbox environments.