You can export your detected API data to a CSV file and share it with engineers within your organization for analysis. The CSV file contains lots of additional data you don’t see in the UI and can help you and your team decide whether to protect an API.
- In API Discovery, click and select Download CSV.
- If you want, in the same menu, click View legend to learn each field’s description in the downloaded CSV file.
Alternatively, the list of all descriptions is available below.
This table helps you understand the parameters that describe your detected API in an exported CSV file.
|The API’s hostname. For example:
|The base path where the API serves content. For example:
|The templatized paths for resources that include a wildcard. For example:
|The number of this API’s unique hostnames. For non-wildcard hostnames, this is always 1.
|The set of sample hostnames if a hostname includes a wildcard. For non-wildcard hostnames, this simply shows the hostname.
|The number of unique resource paths the API uses.
|The sample resource paths detected for resources that include wildcards.
|When the API was first detected in the Akamai network.
|When the API last served traffic in the Akamai network.
|The format of the data the API returns. For example:
JSON. For all available formats, see Data formats and content types.
|The value of the
Content-Type header the API returns. For example:
application/json. For all available content types, see Data formats and content types.
|The number of detected requests the API received through a browser. For details on how browser detections work, see User agents.
|The number of detected requests the API received through a mobile device. For details on how mobile detections work, see User agents.
|The number of detected GET requests the API received.
|The number of detected PUT requests the API received
|The number of detected POST requests the API received.
|The number of detected OPTIONS requests the API received.
|The number of detected success responses (2xx status codes) the API returned.
|The number of detected redirect responses (3xx status codes) the API returned.
|The number of detected client error responses (4xx status codes) the API returned.
|The number of detected server error responses (5xx status codes) the API returned.
|The number of detected requests sent to the API in the previous day.
|The trend of the current day’s detected requests versus the average number of detected requests in the last 30 days. Either HIGHER or LOWER.
|The number of detected requests sent to the API.
|The number of detected unique IP addresses that sent requests to the API.
|The percentage of detected requests sent to the API by clients with the reputation score greater than five.
|The percentage of detected web attackers among the bad reputation clients.
|The percentage of detected scanners among the bad reputation clients.
|The percentage of detected DoS attackers among the bad reputation clients.
|The percentage of detected web scrapers among the bad reputation clients.
|Whether you registered the API entry.
|Whether you associated an API match target with the API’s hostname.
|Whether you turned on the API request body and resource constraints for the API. Either OFF if the constraints are turned off, ALERT or DENY if they’re turned on.
Updated almost 2 years ago