In order to use the ZignSec APIs you need to authenticate using the access key given by ZignSec.

AuthorizationThis header parameter is the personal access token you received from ZignSec during the registration process. Example: Authorization: 12345678-e2a2-4968-b651-5352305c9fb0Required
Content-TypeSpecifies the media type of the request body data. Set to application/x-www-form-urlencoded. for post data and application/json if json object. Required
HostUse for test environment and for production environment. Example: api.zignsec.comRequired

  General REST call format, [service] and [method] needs to be enabled for user ‘00000000-e2a2-4968-b651-5352305c9fb0’:

POST[service]/[method] HTTP/1.1
Authorization: Your access token
Content-Type: application/x-www-form-urlencoded
Content-Length: 71

General configuration

To get started with any ZignSec integration you need to configure a few things. This is most easily done by telling us the below configuration options. Please note that you can set up multiple configurations for the same account. If that is the case, you will need a configid to use when calling the API.  

Return URLThis is the URL ZignSec sends back to the browser via the “redirect” when all is done. You can also put any request in the “target” field.
WebhooksThese are server-to-server calls that occur at various events. The easiest way to get started is to provide an URL. For this service only “api.success” is interesting. Read more about this in the section Webhooks.

IP whitelisting

IP whitelisting can be configured please contact Zignsec support and we will help you.

Example: Set allowed IP addresses

Use Allowed_IPs setting to set IP addresses. You can provide several IP addresses separated by semicolon.


IP ranges are also supported such as “” and “” and “”

Note: “newValue” string needs to be base64-encoded.

Content-Type: application/json; charset=UTF-8
Authorization: YOUR-KEY