Webhooks

​

Choose events

• For verification lifecycles, subscribe to the verifications.updated webhook and the verifications.creation_failed webhook.
• For Data API workflows, subscribe to the account and data webhooks that indicate when the records your application needs are available.
• For Item health changes, subscribe to Item webhooks explicitly.

​

Create a subscription

{
  "events": [
    "verifications.updated"
  ],
  "name": "verification-status",
  "url": "https://your-webhook-backend.com/argyle",
  "secret": "optional-secret",
  "config": {
    "include_resource": true
  }
}

• Item webhooks are not included.
• Partial-synchronization events cannot define their history window through the wildcard subscription.
• Events that support include_resource must be subscribed to individually when you need the resource object.

​

Receive deliveries

• 34.27.251.226
• 34.122.50.253
• 35.188.163.115
• 35.226.53.251

​

Verify signatures

1. Read the raw request body without parsing or reformatting it.
2. Create an HMAC-SHA512 digest using the subscription secret.
3. Compare the hexadecimal digest with X-Argyle-Signature using a timing-safe comparison.

const crypto = require('crypto')

function isValidArgyleWebhook(rawBody, receivedSignature, secret) {
  const expected = crypto
    .createHmac('sha512', secret)
    .update(rawBody)
    .digest('hex')

  const received = Buffer.from(receivedSignature, 'hex')
  const calculated = Buffer.from(expected, 'hex')

  return received.length === calculated.length &&
    crypto.timingSafeEqual(received, calculated)
}

​

Retry behavior

• 429
• 500
• 502
• 503
• 504

​

Manage subscriptions

• List subscriptions
• Retrieve a subscription
• Delete a subscription