For the complete documentation index, see llms.txt. This page is also available as Markdown.

API Usage Requirements

This article lists requirements for using the NATS API.

Restrict Access by IP

hand-holding-star

To use the NATS API, you will need to provide a list of IP addresses that will be granted access to the NATS API.

In the Security section of the Configuration Admin, this information is stored as a comma-separated list of IP addresses set in the Admin Allowed IPs setting.

Enable REST API

hand-holding-star

In addition to allowing API access to IP addresses, you will need to enable the NATS API itself.

In the Security section of the Configuration Admin, enable the API by clicking the checkbox for the Enable REST API configuration setting and changing the setting to Yes.

This configuration is disabled by default and is available to quickly turn off the NATS API for all users should the need arise.

API Users per System or Server

hand-holding-star

An example of this type of setup would be creating an account for API use in your members area, and creating a separate account for API use on an external Adtool system. If you have members areas on separate servers, it would be best to create a separate account for each server as well.

API Permissions

hand-holding-star

For each account able to access the API system, we provide the ability to restrict the resources or functions available to them.

For example, if an account is to be used for membership authentication, set the account's API permissions to only allow them access to the member search function.

REST API Permissions

By Default, an account does not have access to any of the available REST API resources.

Click the Details button associated with the corresponding admin area to select which of the collection, method, and resource combinations you would like to enable for the account.

Save the configuration by clicking the Save button at the bottom of the modal.

API OverviewAPI Endpoints

Last updated

Was this helpful?