|
Templates for HTTP GET carriers tell PageGate what variables and data to declare in the URL passed to the API.
All variables are declared in the 'Text' section of the template as follows:
|<name1>|<value1>|
|<name2>|<value2>|
etc.
Each value you specify will need to correspond to a variable that the receiving API will recognize. For example, let's say we wanted to send a message to an API that looked for to, from, subject and text as variables. We would need to format the text template as follows:
|to|%RecipientId%|
|from|%Sender%|
|subject|%Subject%|
|text|%Message%|
NOTE: | a pipe character.
The following parameters can be specified in the 'Settings' section of an HTTP GET carrier
Variable
|
Possible Values
|
Example Statement
|
Description
|
ResponseRecipient
|
Recipient
Group
|
ResponseRecipient = A recipient or group's name as it exists in the PG Admin
|
When the HTTP GET transaction completes, the specified recipient or group will receive any responses from the receiving API/web host. For more information, please see the Two Way Messaging section of the documentation.
|
InterMessageDelay
|
Milliseconds
|
InterMessageDelay = 1000
|
This variable forces PageGate to delay for the specified number of milliseconds (1000 = 1 second) after delivering each message.
|
From
|
Text
|
From = CAD
|
This variable overrides the value passed to PageGate by the input modules/APIs. By specifying this variable, you're telling PageGate to use a single, standardized sender's name for all traffic controlled by this template.
|
To
|
Text
|
To = 7818290500
|
This variable overrides the ID/PIN or Email values. By specifying this variable, you're telling PageGate to send all traffic processed by this template to the specified ID or Email address instead.
|
|