Using the Enzoic API
Last updated
Was this helpful?
Last updated
Was this helpful?
The Enzoic APIs are implemented as a series of RESTful web services with JSON payloads. All APIs must be accessed via HTTPS and require You can request a key.
As is standard for REST APIs, API call parameters for GET requests are submitted in the query string for GET requests. For POST requests, parameters are submitted in the body as a JSON payload. The Content-Type header should always be set to application/json.
The API endpoint is:
All API endpoints require an HTTP basic authentication header. Your API Key is the username and your API Secret is the password portion of the header. The authentication header value is constructed in the standard fashion:
So, for example, if your API Key is b38f5a609f01442fb8ceb1aa02474903 and your Secret is 8e8a185dfa3e437f85afba165ce407b4, the resultant authentication header would be
Enzoic uses HTTP status codes to indicate success/failure conditions for API calls. Below is a listing of the response codes used for all Enzoic API calls along with their meaning.
200
Success. Body will contain appropriate response.
400
Required parameters were either missing or invalid.
401
Authentication header either missing or API key/Secret were not valid. Check the response body for more information.
403
Either the rate limit or monthly quota have been exceeded. Check the response body for more information.
404
For GET calls, indicates the requested entity was not found.
500
Unexpected error. Check the response body for more information.
Individual API calls may have additional response codes listed in the documentation for that call.
If your firewall requires explicit rules for outbound traffic on port 443, please whitelist the following IP addresses:
13.235.194.196 13.48.121.56 13.48.96.148 15.206.40.21 18.196.181.48 3.10.99.236 3.124.25.136 3.231.37.171 3.24.50.155 3.24.93.121 3.9.236.117 34.214.110.33 35.153.27.185 35.163.59.86 35.168.85.109 35.180.249.238 35.181.124.196 52.192.30.99 52.199.52.28 52.212.218.163 52.48.142.122 52.51.10.65 52.79.68.108 52.89.197.157 54.172.238.226 54.180.42.79 54.233.211.111 54.233.236.93 75.2.9.104 99.83.177.145
There isn’t a facility for specifically setting an HTTP proxy in our Client Libraries, but this can be done via command line parameters. For example :