In this article we discuss how to set up the API tokens needed for authentication of HTTP GET Methods, as well as determining the corresponding subdomain.
The ChaseData solution provides the ability to import or update information using HTTP GET Methods. They can be used as wrappers for FORM actions, for example, when integration using PHP is not viable.
These methods are accessed via https://api.chasedatacorp.com/HttpImport/ and are explained in the following article:
The ChaseData solution allows you to create multiple tokens for the case when you need a different one for each of your vendors, for example, when you have them injecting leads independently.
To create an API Token, click on the 3-dot icon on the right side of the top area of the GUI (a.k.a. the “Tools menu”), above the Search field, which will open a menu; click on Settings, and then on Integrations on the expanded menu. Next select the API Tokens tab. Refer to the following picture.
To add a new one, click on Click here to add new item on the grey bar on top of the list, under Token. This allows you to provide a Description or label for your token. Save your change and the new Token with its Description and corresponding dates are shown. Refer to the following pictures.
When using a GET method, in addition to the API Token, you are required to provide the accid, which corresponds to the FQDN prefix (e.g. if customer/vendor FQDN is test.chasedatacorp.com, accid = test).