--- updatedAt: 2026-03-01T18:24:52.000Z agentTools: siteIndex: https://techdocs.akamai.com/llms.txt projectIndex: https://techdocs.akamai.com/reporting/llms.txt --- # API Gateway reports API Gateway reports show various operational data about your registered API configurations. You can use this data to better understand your API traffic, fine-tune your API delivery settings, resolve various access and security issues, and troubleshoot errors effectively. You can access this report from the **Reports** menu. See [How to use reports](https://techdocs.akamai.com/reporting/docs/how-use-rpts). # Endpoints by Method or Status report The Endpoints by Method/Status report provides information about the HTTP methods that API consumers called on your API endpoints and the response codes that your API endpoints returned. **Filters**\ The Endpoints by Method or Status report lets you filter the data included in the report by the following criteria: * **CP code (required)**. Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code. * **Endpoint**. An API configuration registered with ​Akamai​. * **HTTP method**. A request method indicating the action performed on a resource. * **Response code**. An HTTP response status code, for example, `201`. **Metrics**\ This report displays one of the following statistics: * **Hits**. The number of egress and midgress hits. * **Egress bytes**. The bandwidth for the amount of API traffic that left the network. * **Midgress bytes**. The bandwidth for the amount of internal API traffic exchanged between edge servers. # Endpoints Usage by Identifier report The Endpoints Usage by Identifier report has information about the usage of your API endpoints over time and the API keys included in the incoming API requests. **Filters**\ The Endpoints Usage by Identifier report lets you filter the data included in the report by certain criteria: * **CP code (required)**. Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code. * **Endpoint**. An API configuration registered with ​Akamai​. * **API key**. A unique identifier of an API consumer. **Metrics**\ This report displays one of the following statistics: * **Hits**. The number of egress and midgress hits. * **Egress bytes**. The bandwidth for the amount of API traffic that left the network. * **Midgress bytes**. The bandwidth for the amount of internal API traffic exchanged between edge servers. # Errors by Key report The Errors by Key report provides information about error response codes (**4XX** and **5XX** ) that your API endpoints returned and the API keys that caused the error responses. **Filters**\ The Errors by Key report lets you filter data using several criteria: * **CP code (required)**. Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code. * **API key**. A unique identifier of an API consumer. * **Endpoint**. An API configuration registered with ​Akamai​. * **Response class**. A class of HTTP response status codes, such as **2XX**. * **Response code**. An HTTP response status code, such as **201**. **Metrics** * **HTTP error status frequency**. The number egress and midgress hits for each selected error response class. * **Errors by key**. The number egress and midgress hits for each selected error response code, API key, and endpoint combination. # JWT Denials report The JWT Denials report provides information about the API requests that failed the JWT validation, the denial reason for each rejected request, and the claim that caused the validation failure. **Filters**\ The JWT Denials report lets you filter using certain criteria: * **CP code (required)**. Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code. * **Endpoint**. An API configuration registered with ​Akamai​. * **Denial Reason**. A JWT-related reason for rejecting a request. * **Failed Claim**. A JWT claim that failed the validation. **Metrics** * **Hits by denial reasons**. The number of egress and midgress hits, shown for each selected denial reason, failed claim, and endpoint combination. # Quota Usage by Time report This report shows the quota usage by given API key by time. **Filters** * **API key**. API key for which to show quota usage. **Metrics** * **Quota used**. A number of API hits that have been counted towards quota. # Sibling pages * [Traffic reports](https://techdocs.akamai.com/reporting/docs/traffic-rpts.md) * [Edge DNS reports](https://techdocs.akamai.com/reporting/docs/edge-dns-rpts.md) * [Infrastructure Security Analytics reports](https://techdocs.akamai.com/reporting/docs/infrasec-analytics-rpts.md) * [Network Observability Analytics (NOA) reports](https://techdocs.akamai.com/reporting/docs/network-observability-analytics-noa-reports.md) * [Prolexic reports](https://techdocs.akamai.com/reporting/docs/prolexic-rpts.md) * [GTM reports](https://techdocs.akamai.com/reporting/docs/gtm-rpts.md) * [Web and mobile optimization](https://techdocs.akamai.com/reporting/docs/web-mobile-optimization.md) * [Data Products reports](https://techdocs.akamai.com/reporting/docs/data-products-rpts.md) * [Software as a Service (SaaS)](https://techdocs.akamai.com/reporting/docs/software-service-saas.md) * [Cloud Wrapper reports](https://techdocs.akamai.com/reporting/docs/cloud-wrapper-rpts.md) * [NetStorage reports](https://techdocs.akamai.com/reporting/docs/netstorage-rpts.md) * [Media Services Live reports](https://techdocs.akamai.com/reporting/docs/media-services-live-rpts.md)