Developers may want to receive updates from LinkMoney in the form of ‣s. Some developers, like those coming from Plaid, can configure and create webhooks entirely through their authentication calls (See Plaid 1:1 Migration Guide). Others, however, must make API calls to view, configure, delete, and edit their subscribed events.

For information on the actual content of various LinkMoney webhooks, see Webhooks. This documentation only covers how to interact with webhook endpoints.

Subscribe to a Webhook.

POST /configuration/webhooks

Subscribe to a new webhook event. For details on different kinds of webhook events, see Webhook Endpoints.

Parameters

For the POST Body.

Example Requests

For a Specific Webhook Event

Some webhook flows require a new subscription to be created for each type of webhook. These events can each have different callback URLs for different callback handling, though there is no restriction on using the same callback URL for multiple webhooks, provided that your endpoint's logic can handle multiple kinds of payload.

curl -X POST /configuration/webhooks \\
	-H 'Authorization: Bearer {YOUR_BEARER_TOKEN}'
	-d '{
		"eventName": "DATA_UPDATES",
		"callbackURL": "<https://example.com/link-money/data-update-callback>"
	}'

For a Generic Webhook Event

Some webhook flows (like Plaid) default to sending the full variety of their webhook events to a single callback URL.

curl -X POST /configuration/webhooks \\
	-H 'Authorization: Bearer {YOUR_BEARER_TOKEN}'
	-d '{
		"callbackURL: "<https://example.com/link-money/callback>"
	}'

Response

{
	"webhook": {
		"id": "{new_webhook_id}",
		"eventName": "DATA_UPDATES",
		"callbackURL": "<https://example.com/link-money/data-update-callback>",
		"lastEvent": "{last_event_id}",
		"lastEventTime": "2021-02-05" // note that this field will conform to the dateFormat specified in your developer configuration.  
	}
}

Unsubscribe from a Webhook.