---
title: "Analytics | Subscription Usage"
description: "API Documentation"
url: "https://www.contentstack.com/docs/developers/apis/analytics-api/subscription-usage"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-06-02"
---

# Analytics | Subscription Usage

### Subscription Usage

**GET** `/analytics/v2/subscription?orgUid={organization_uid}&services={service}&from={YYYY-MM-DD}&to={YYYY-MM-DD}&date={YYYY-MM-DD}`

The Subscription Usage request returns the total number of resources, projects, environments, domains, and so on, created in your organization for a specific service. Pass the service you want data for in the services parameter: launch, cs-assets, or agents. For CMS and Automate figures, use the [Usage Analytics](/docs/developers/apis/analytics-api#usage-analytics) request.

**Note**: The shape of data differs by service. For launch, data is an array containing a single object. For cs-assets and agents, data is a single object.

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 with services set to launch.

```
{
    "data": [
        {
            "total_launch_project": 9,
            "total_launch_env": 11,
            "total_launch_domain": 2
        }
    ],
    "meta": {
        "orgUid": "blt**************87",
        "from": "2024-06-30",
        "to": "2024-09-12"
    },
    "uid": "0f****46-5ee9-4f38-9146-1f********87"
}
```

The response body provides an overview of the resources in the Launch section within your organization. Here’s a breakdown of the key elements:

*   total\_launch\_project: The total number of projects created within Launch.
*   total\_launch\_env: The total number of environments associated with the Launch projects .
*   total\_launch\_domain: The total number of domains configured within Launch.

This response gives a clear view of how Launch resources are utilized within the specified date range.

Here’s how your response body would look like with services set to cs-assets.

```
{
    "data": {
        "deleted_assets_total": 0,
        "workspace_total": 0,
        "asset_storage": 9932858,
        "asset_total": 14,
        "ai_assets_usage": 0,
        "spaces_total": 0,
        "fields_total": 0,
        "custom_asset_types": 0
    },
    "meta": {
        "orgUid": "blt**************cc",
        "date": "2026-05-19",
        "services": "cs-assets"
    },
    "uid": "cf****06-c2e4-48e6-a776-af********95"
}
```

Field reference:

*   custom\_asset\_types: Number of custom asset types defined in the organization.
*   workspace\_total: Total number of workspaces in the organization.
*   deleted\_assets\_total: Total number of assets deleted in the organization.
*   spaces\_total: Total number of spaces in the organization.
*   asset\_total: Total number of assets stored in the organization.
*   asset\_storage: Total storage consumed by assets.
*   ai\_assets\_usage: Total AI-assisted asset operations performed in the organization.
*   fields\_total: Total number of custom fields defined across asset types.

Here’s how your response body would look like with services set to agents.

```
{
    "data": {
        "agent_executions_completed": 0,
        "agent_total": 0,
        "total_tokens_consumed": 0,
        "agent_executions_failed": 0,
        "total_executions": 0,
        "total_active_agents": 0
    },
    "meta": {
        "orgUid": "blt**************74",
        "date": "2026-05-19",
        "services": "agents"
    },
    "uid": "dc****76-a481-4c7b-b944-63********fb"
}
```

Field reference:

*   agent\_total: Total number of agents in the organization.
*   total\_active\_agents: Number of agents currently in an active state.
*   total\_executions: Total number of agent executions, including completed and failed runs.
*   agent\_executions\_completed: Number of agent executions that completed successfully.
*   agent\_executions\_failed: Number of agent executions that failed.
*   total\_tokens\_consumed: Total number of LLM tokens consumed across all agent executions.

#### Query Parameters

- **orgUid** (required)
  Enter the UID of your Organization.
- **services** (required)
  Enter the service for which the subscription usage is required. Only one value is accepted, and it must be launch, cs-assets, or agents. If you pass an unrecognized value, or more than one value, the request does not fail — it is treated as launch. Launch data is also returned when this parameter is not passed.
- **from** (required)
  Specify the start date for the required data. Use the following date format: YYYY-MM-DD. It cannot be in the future. Required when services is launch; not used for cs-assets or agents.
- **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. Required when services is launch; not used for cs-assets or agents.
- **date** (optional)
  Provide the date for which the snapshot of subscription usage is required, in YYYY-MM-DD format. Applies when services is cs-assets or agents; ignored for launch. If you omit it, the value of to is used; if that is also absent, today’s date is used. A date older than 90 days does not return an error — the response comes back with empty or zero values.

#### 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
}
```