--- title: "Analytics | Usage Analytics" description: "API Documentation" url: "https://www.contentstack.com/docs/developers/apis/analytics-api/usage-analytics" product: "Contentstack" doc_type: "guide" audience: - developers - admins version: "current" last_updated: "2026-06-02" --- # Analytics | Usage Analytics ### Usage Analytics **GET** `/analytics/v2/usage?from={YYYY-MM-DD}&to={YYYY-MM-DD}&orgUid={organization_uid}` The Usage Analytics request gives a quick usage overview of your bandwidth and API utilization over a particular period of time. Here’s how your response body would look like when you pass the jobId in the [Retrieve Data](/docs/developers/apis/analytics-api#retrieve-data) endpoint. ``` { "data": [ { "total_api_bandwidth": 0, "total_api_count": 0, "total_cdn_bandwidth": 0, "total_cdn_count": 0, "date": "2024-03-02" }, { "total_api_bandwidth": 0, "total_api_count": 0, "total_cdn_bandwidth": 10110, "total_cdn_count": 4, "date": "2024-02-12" }, { "total_api_bandwidth": 0, "total_api_count": 0, "total_cdn_bandwidth": 0, "total_cdn_count": 0, "date": "2024-02-22" }, { "total_api_bandwidth": 0, "total_api_count": 0, "total_cdn_bandwidth": 0, "total_cdn_count": 0, "date": "2024-03-25" }, { "total_api_bandwidth": 94685, "total_api_count": 26, "total_cdn_bandwidth": 0, "total_cdn_count": 0, "date": "2024-03-04" }, { "total_api_bandwidth": 0, "total_api_count": 0, "total_cdn_bandwidth": 0, "total_cdn_count": 0, "date": "2024-02-28" } ], "meta": { "orgUid": "blt**************87", "includeCount": "true", "from": "2024-01-31", "duration": "day", "to": "2024-03-31", "services": "[\"cdn\",\"cma\"]" }, "uid": "0f****46-5ee9-4f38-9146-1f********8"} ``` The response body provides detailed insights into your organization's API and CDN usage over a specified period. Here’s a breakdown of the key elements: * total\_api\_bandwidth: The total bandwidth consumed by API requests on the specified date. * total\_api\_count: The number of API requests executed on the specified date. * total\_cdn\_bandwidth: The total bandwidth consumed by CDN requests on the specified date. * total\_cdn\_count: The number of CDN requests made on the specified date. * date: The specific date for the reported statistics. This data helps monitor and analyze the usage patterns of API and CDN resources, aiding in efficient resource management and planning. **Note** * The apiKey parameter cannot be combined with the automations, launch, or cs-assets services. Doing so returns a 400 error. * The projectUid and environmentUid parameters are only applicable to the \["launch"\] service. Combining either one with cs-assets returns a 400 error. * space\_uid and subService can only be used when services is set to \["cs-assets"\] on its own. * When services is cs-assets, you must pass duration. Without it the response returns an empty data array rather than an error. Here’s how your response body would look like with services set to cs-assets. ``` { "data": [ { "date": "2026-03-01", "asset_api_usage": 0, "asset_bandwidth_usage": 0 }, { "date": "2026-05-01", "asset_api_usage": 2783, "asset_bandwidth_usage": 19438120 } ], "meta": { "orgUid": "blt**************cc", "from": "2026-03-31", "to": "2026-05-25", "services": "[\"cs-assets\"]", "duration": "month" }, "uid": "a1****69-2fd7-4912-a213-4f********d4"} ``` Field reference: * asset\_api\_usage: The number of Assets API requests made in the period. * asset\_bandwidth\_usage: The bandwidth consumed by Assets requests in the period. * date: The start of the period the row covers. #### Query Parameters - **orgUid** (required) Enter the UID of your Organization. - **from** (required) Specify the start date for the required data. Use the following date format: YYYY-MM-DD. It cannot be in the future. - **to** (required) Enter the end date for the required data. The date format should be: YYYY-MM-DD. It must be on or after the from date and cannot be in the future. - **services** (optional) Specify the array of services for which you want statistics, such as: \["cma", "ui", "cdn", "graphql", "images", "assets", "automations", "launch", "cs-assets"\]. Pass either a JSON array of service names, for example \["cdn","cma"\], or a single service name on its own, for example automations. A comma-separated list is not supported and returns no data. - **duration** (optional) Determines the granularity of the data. Accepted values are sec, minute, hour, day, week, month, year, and historic; any other value returns a 400 error. If you omit duration, the response is not broken down by date. - **apiKey** (optional) Enter the API key of the stack. - **projectUid** (optional) Enter the Launch project UID to retrieve data from that specific project. - **environmentUid** (optional) Enter the environment UID of the Launch project. - **space_uid** (optional) Enter a space UID to filter the response to that space, or all to include every space. The value is not case-sensitive. Only available when services is set to cs-assets on its own — passing it alongside any other service returns a 400 error. - **subService** (optional) Enter all, delivery-api, or management-api to filter the response to one part of the cs-assets service. The value is not case-sensitive; any other value returns a 400 error. Defaults to all. Like space\_uid, it can only be used when services is set to cs-assets on its own. #### Headers - **authtoken** (required) Enter your authtoken. Default: `your_authtoken` #### Sample Response ```json { "jobId": "job_7******a-c**f-4**9-9**0-c**********6", "paginated": false } ```