# Data Retrieval

_

## Report Data

 - [GET /{report}](https://apidocs.mediamath.com/apis/reporting-api-v1/data-retrieval/get_report.md): {% admonition type="danger" name="This API is deprecated and will be removed in July 2026" %}
  The new API docs can be found here: https://apidocs.mediamath.com/apis/reporting-api
{% /admonition %}

# Parameters

Parameter names are case sensitive, (see the table below).

Most parameters will fall under one of the following two formats.

*   enumeration of comma-separated items (used in aggregation, selection and sorting);
    *   example:
        *    (in other words, )
*   list of logically AND-ed expressions, joined by ampersand (used in dimension and metric filtering);
    *   examples:
        *    (in other words, )
        *    (in other words, filterhavingfilterhaving=filterhavingfilterhavingfilterhavinghavingdimensionsmetricsContent-Type: text/csvstart_dateend_datestart_dateend_datetime_rollupintervaldatetimeContent-Type: text/xml`) will contain, at the minimum (see examples below), the root element result, with at least one element named status, which in turn has an attribute named code, and a human readable text. Some error responses also contain an attribute reason, which adds more information regarding the error.

There are several types of errors:

### Authentication and authorization errors





### Parameter validation errors (malformed values, unknown fields, missing required parameters, etc)



### Non-existent entities



### Server errors (internal error, request timeout, scheduled maintenance, server overloaded)







## Validate Report Data Request

 - [GET /{report}/validate](https://apidocs.mediamath.com/apis/reporting-api-v1/data-retrieval/get_report-validate.md): {% admonition type="danger" name="This API is deprecated and will be removed in July 2026" %}
  The new API docs can be found here: https://apidocs.mediamath.com/apis/reporting-api
{% /admonition %}

### Validating Data Retrieval Requests

Data retrieval requests can be validated and authenticated without actually requesting data, by simply appending a  path segment to the URI.  The validation process takes into account the current user's permissions. The error responses that are returned in case of validation failure are the same as the ones that would have been returned by the regular API call.

The following shows an example validation request for a request with an erroneous  filtering parameter:





By contrast, this call shows a validation response for a valid call: