Retrieve a synchronous webhook list

Retrieve a list of synchronous webhook objects.

You can use this endpoint to see your different address validation endpoints registered to different locations.

Info

For more information about locations, see: Merchant API: Locations.

Request​

Header parameters
Header parameters

Example: "Bearer sk_1234567890ABCdefGHIjklMNOpqrSTUvwxYZ_1234567890-Ab_cdeFGHijkLMNopq"

This parameter accepts the Merchant API Secret key to authorise requests coming from the merchant's backend.

It ensures that ensures that each request is authenticated and authorised by verifying the secret key. The secret key should be included in all request headers as a Bearer token.

Info

For more information, see: Authentication

Response​

Synchronous webhook list returned

Response body
Body array of objects

The ID of the synchronous webhook object.

Pattern: Value must match regular expression ^swsk_[a-zA-Z0-9]{32}$

A randomly generated signing key, which can be used by merchants to authenticate requests from Revolut by verifying the signature. For more information, see: Payload Signature.

Possible length: <= 2000 characters
Pattern: Value must match regular expression ^https:\/{2}.+/gi

The valid URL of the endpoint, that uses HTTPS URL schema. Revolut sends the shipping address of the customer to this URL for validation.

Caution

Restrictions:

  • Must be a valid URI as defined by RFC 3986
  • URI scheme is required and must be https
  • URI host is required and cannot be localhost or an IP address
  • Max length: 2000
  • Reserved or invalid characters must be percent-encoded (for example, use %20 instead of a space)

Possible values: [fast_checkout.validate_address]

Type of event this synchronous webhook is configured for.

Note

At the moment, synchronous webhooks only support address validation events.

Unique ID representing the location where merchants sells products.

Info

For more information, see: Locations.