API Documentation
The edlcentral.com API, which firewalls use to obtain EDLs, follows a simple request structure:
For all EDL data sets for the common structure is:
https://api.edlcentral.com/edlfeeds/[provider]/[data]/[data]/[data]/{parameters}
where the [provider] [data] [data] [data] {parameters} select the EDL and the EDL specific query options to return the correct list / data to the firewall.
A full list of EDLs and their URL's.
Most EDL's have IPv4, IPv6, URL data, some have domain data, and some allow 'ipcombined' to be used to aggregate IPv4 and IPv6 into one list.
This website makes use of the same API to display list data in your browser.
Parameters:
You must specify a valid FW_Type as a parameter, if you do not, a default firewall type will be chosen. Some EDLs may require additional parameters as detailed above and in the examples below.
See Configuring EDLs on your Firewall for selecting a valid Firewall / FW_Type.
Some example valid API calls:
|
https://api.edlcentral.com/edlfeeds/cisco/webex/all/url/?FW_Type=paloalto Returns an EDL of the URL's used by Webex with format optimised for a Palo Alto Firewall. |
|
https://api.edlcentral.com/edlfeeds/cisco/webex/all/url/?list=FW_Type~paloalto As above, using an alternative parameter format, see note below. |
|
Returns an EDL of IPv4 and IPv6 addresses combined, for ASNs 7,9,6,0,999. |
Note: Some firewalls have issues with correctly encoding some EDL requests with multiple parameters and incorrectly encode the & character in the parameters section or the URL, causing a 500 error from the API. To resolve this we allow parameters to be specified in a single parameter "list=" with the desired parameters, replacing the "=" with a "~" and the "&" with a "." as in the example.
Note: If you use an IP combined EDL, or mix IPv4 and IPv6 EDLs in the same firewall policy line / rule, please double check that your firewall supports that and is actually enforcing those rules correctly.
API responses & HTTP response codes:
|
HTTP Response Code
|
Description
|
|
200
|
Success, the response body / attachment will contain the data / EDL.
In the case of invalid, reserved or unused / defunct AS numbers, a 200 is returned, with any valid data for valid AS numbers, invalid AS numbers or an empty AS parameter list silently return no data. |
|
4nn
|
Something was wrong with the request. The body may indicate more about what cause the error.
|
|
403
|
Forbidden, incorrect API key or similar error, incorrect tier, option or data keys, or invalid combination. The API will return a body attachment with more detail about the error.
|
|
404
|
Resource Not Found, incorrect API request structure.
|
|
429
|
Rate Limit Exceeded.
|
|
5nn
500 |
Something was wrong with the request and the server had an error processing that request, or there is a server fault.
Incorrectly encoded & in parameters is a common cause of this error. |