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
Go to team settings
Click the Connections tab
Click Add Connection
Fill in the name of your Producer
Select Connection type: Webhook Producer
Fill in the Authentication Token your producer will use when sending data to Relayter
Fill in a Secret (optional, described below)
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
In the Connection details page click add Endpoint
Select if you want to send Briefing items or Products to Relayter
Select upsert or delete action for this endpoint
upsert: create or update briefing items based on identifier
delete: delete briefing tiems based on identifier
Select if you want to import to Master briefing
When not importing to master briefing, setup your campaign details fields. This used by Relayter to automatically create the campaigns for you.
Enter the path to the briefing item identifier.
Select the identifier field in Relayter.
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) |
|
JSON Data location | Request Body |
Authentication token header |
|
Content type header |
|
Signature header |
|
Signature hashing algoritm |
|
Signature encoding |
|
Timestamp header |
|
Timestamp max age | 300 seconds |