Server: https://[app key here]-[site_ID here]-apps.worldsecuresystems.com. Take a look at the Authorize your API calls document for more info on how this URL is formed.

Note: When building apps always use relative request URLs. Do not use the "full" URL above because you might have problems running your app on a different site as the site_ID parameter will be different.

Path: /webresources/api/v3/sites/current/news/[news_ID]/securezones

Alternatively, use siteID instead of 'current'

Authorization header: This should contain the authorization token. Here is how to obtain the token.

Response

An array of the first 10 securezones assigned to the news item; each object has the following properties:

id - the id of the secure zone (integer)

siteId - the id of the site (integer)

landingPageId - the ID of the secure zone's landing page (string)

name - the name of the secure zone (string)

sellAccess - whether you charge the customers who get access to the secure zone or not (boolean)

costPerPeriod - the membership cost amount (integer)

orderCountryCode - the currency to use when charging the customers for access(string)

cycleType - the frequency of membership renewal (integer)

"1" Once

"2" Daily

"3" Weekly

"4" Fortnightly

"5" Monthly

"6" Quarterly

"7" Half Yearly

"8" Yearly

createDate - the date the secure zone was created (string)

lastUpdateDate - the date the secure zone was last updated (string)

You can output additional fields to those listed above as default, see the API v3 Discovery APP for additional details.

Server: https://[app key here]-[site_ID here]-apps.worldsecuresystems.com. Take a look at the Authorize your API calls document for more info on how this URL is formed.

Note: When building apps always use relative request URLs. Do not use the "full" URL above because you might have problems running your app on a different site as the site_ID parameter will be different.

Path: /webresources/api/v3/sites/current/news/[news_ID]/securezones

Alternatively, use siteID instead of 'current'

Authorization header: This should contain the authorization token. Here is how to obtain the token.

Data: This should contain a stringified, valid json object containing an array of objects with key "zoneId" and value of a valid secure zone id

Server: https://[app key here]-[site_ID here]-apps.worldsecuresystems.com. Take a look at the Authorize your API calls document for more info on how this URL is formed.

Note: When building apps always use relative request URLs. Do not use the "full" URL above because you might have problems running your app on a different site as the site_ID parameter will be different.

Path: /webresources/api/v3/sites/current/news/[news_ID]/securezones

Alternatively, use siteID instead of 'current'

Authorization header: This should contain the authorization token. Here is how to obtain the token.