Skip to main content
All CollectionsIntegrationsSend data to Relayter
Connect a Webhook Producer to Relayter

Connect a Webhook Producer to Relayter

Simon Windt avatar
Written by Simon Windt
Updated over 2 months ago

If you want to send data to Relayter you can do so using Webhooks. In this article we will describe how to setup and send data to Relayter using a Webhook producer.

Setup a Webhook producer connection in Relayter

  1. Go to team settings

  2. Click the Connections tab

  3. Click Add Connection

  4. Fill in the name of your Producer

  5. Select Connection type: Webhook Producer

  6. Fill in the Authentication Token your producer will use when sending data to Relayter

  7. Fill in a Secret (optional, described below)

  8. Select if you want to use timestamp verification (optional, described below)

Add an endpoint

In the endpoint you can create mappings to map your JSON data that you send to data in Relayter. A mapping is a string to define the route to the property in the JSON. For example: body.data.title . You can also use array indexes like: body.data.products.0.ean

  1. In the Connection details page click add Endpoint

  2. Select if you want to send Briefing items or Products to Relayter

  3. Select upsert or delete action for this endpoint

    1. upsert: create or update briefing items based on identifier

    2. delete: delete briefing tiems based on identifier

  4. Select if you want to import to Master briefing

  5. When not importing to master briefing, setup your campaign details fields. This used by Relayter to automatically create the campaigns for you.

  6. Enter the path to the briefing item identifier.

  7. Select the identifier field in Relayter.

  8. Add mappings for your data.

Sending data

After creating the endpoint, Relayter will create an endpoint which you can use to send data to.

Authentication

We have 3 layers of security which you can use. The first is the Authentication token, which is a simple shared secret send via a http header. The next is using a secret, which is used to create a HMAC signature, preventing sending the secret over the internet. The last is timestamp verification. This prevents sending the same request more than once. The secret and timestamp are optional, but we strongly recommend using at least the HMAC signing using the secret.

For more information about HMAC signatures:

Request details for sending data

Method (for upsert & delete)

POST

JSON Data location

Request Body

Authentication token header

Authorization

Content type header

Content-Type: application/json

Signature header

Webhook-Request-Signature

Signature hashing algoritm

sha256

Signature encoding

hex

Timestamp header

Webhook-Request-Timestamp

Timestamp max age

300 seconds

Did this answer your question?