> For the complete documentation index, see [llms.txt](https://docs.cuoral.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuoral.com/api-reference/customers/company/metrics/get-company-metric-values.md).

# Get Company Metric Values

GET /external/v1/external/v1/customers/companies/{company\_id}/metrics 

### Request 

#### Parameters

| **Name**    | **Type** | **Description**                            | **Location** | **Required** |
| ----------- | -------- | ------------------------------------------ | ------------ | ------------ |
| company\_id | `string` | Company ID (UUID) to retrieve metrics for. | Path         | Yes          |

Example Request URL:

```
/external/v1/external/v1/customers/companies/COMP-XYZ-789/metrics
```

***

### Responses 

#### Successful Response (200) (application/json)

Returns an array of metric value objects for the specified company.

| **Field**     | **Type**            | **Description**                                                |
| ------------- | ------------------- | -------------------------------------------------------------- |
| id            | `integer`           | The internal database ID of the metric entry.                  |
| company\_id   | `integer`           | The ID of the company (as an integer).                         |
| metric\_id    | `integer`           | The internal ID of the metric type.                            |
| metric\_name  | `string`            | The human-readable name of the metric (e.g., 'Monthly Users'). |
| data\_type    | `string`            | The data type of the stored value (e.g., `STRING`, `NUMBER`).  |
| value         | `string`            | The recorded value of the metric.                              |
| time\_created | `string` (datetime) | Creation timestamp of the metric entry.                        |
| time\_updated | `string` (datetime) | Last update timestamp of the metric entry.                     |

Example Response Body (200):

JSON

```json
[
  {
    "id": 101,
    "company_id": 501,
    "metric_id": 12,
    "metric_name": "Monthly Active Users",
    "data_type": "NUMBER",
    "value": "9500",
    "time_created": "2025-11-20T10:00:00.000Z",
    "time_updated": "2025-11-27T10:03:16.608Z"
  },
  {
    "id": 102,
    "company_id": 501,
    "metric_id": 5,
    "metric_name": "Last Contact Date",
    "data_type": "STRING",
    "value": "2025-11-25",
    "time_created": "2025-01-01T00:00:00.000Z",
    "time_updated": "2025-11-25T15:30:00.000Z"
  }
]
```

#### Validation Error (422) (application/json)

```json
{
  "detail": [
    {
      "loc": [
        "string",
        0
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cuoral.com/api-reference/customers/company/metrics/get-company-metric-values.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.