# List Technology Target Values

Get list of technology target values. Can be sorted by:
- `id`,
- `dimension`,
- `parent_id`,
- `name`,
- `full_path`,
- `value`,
- `code`,
- `sortable_name`
and queried (with `q=`) by:
- `id`,
- `parent_id`,
- `name`,
- `full_path` (if provided parameter `full_path` will be ignored),
- `value`,
- `code`,
- `sortable_name`.

Endpoint: GET /technology_target_values
Version: 3.0.1807
Security: Auth0

## Query parameters:

  - `name` (string)
    Case insensitive name contains search. Example: `name=target1`

  - `full_path` (string)
    Case insensitive full_path contains search. Example: `full_path=target1`

  - `dimension_code` (string, required)
    Comma separated list of dimension codes. Example: `dimension_code=BRLG,BSER`. Supported values:
 - `BRLG` - Browser Language,
 - `OSXX` - Operating System (extended),
 - `BSER` - Browser,
 - `CSPD` - Connection Speed,
 - `DVMD` - Device Model,
 - `DVCE` - Device,
 - `INVT` - Inventory (supply source/publisher),
 - `ISPX` - ISP (Internet Service Provider),
 - `VAUD` - Video: Audibility,
 - `VCON` - Video: Context,
 - `VLIN` - Video: Linearity (linear vs non-linear),
 - `VPLC` - Video: Placement,
 - `VPSZ` - Video: Player Size,
 - `VSKP` - Video: Skippability,
 - `DMAX` - Designated Market Area,
 - `REGN` - Region (geographic region),
 - `COUNTRY` - Country,
 - `CITY` - City.

  - `sort_by` (string)
    The field to sort by. You can use any field name in ascending or descending order.
For ascending order, use the field name directly, e.g., `id`. 
For descending order, prefix the field name with a hyphen (`-`), e.g., `-id`.

  - `q` (string)
    Query search for filtering. This parameter can be used to filter results based on various fields.
Supported operators:
- `==` - numeric equality or case-sensitive string identity, 
- `==(1,2,3)` - IN query (only works for integers),
- `!=` - numeric inequality or case-sensitive string non-identity,
- `=:` - case-insensitive match, allows substring using * wildcards,
- `<` - less than,
- `<=` - less than or equal to,
- `>` - greater than,
- `>=` - greater than or equal to.
Examples: 
- `q=name=:{search}*` to find all results with names starting with {search}.
- `q=status==true` to find all active entities.
- `q=id>=1000` to find all entities with id greater than or equal to 1000.
- `q=id==(1,2,3)` to find specific entities by ID.
- `q=created_on>1999-02-02` or `q=created_on>1999-02-02T00:00:00Z` to find entities created later than date.
- `q=id>5&status==true` to find all active entities with id greater than 5.

## Response 200 fields (application/json):

  - `data` (array)

  - `data.id` (number)

  - `data.dimension` (string)

  - `data.name` (string)

  - `data.sortable_name` (string)
    Field equals formatted name for `OSXX, DVMD` dimensions and `name` for other dimensions.
Example: `name=WURFL/OS/Android/OS Version/2.0, dimension=OSXX` then `sortable_name=Android » 2.0`.

  - `data.full_path` (string)

  - `data.value` (number)

  - `data.code` (string)

  - `meta` (object)

  - `meta.status` (string, required)
    The status of the response, indicating success or failure.
    Example: success

  - `meta.count` (integer, required)
    The number of items returned in the current response.
    Example: 10

  - `meta.total_count` (integer)
    The total number of items available in the dataset.
    Example: 100

  - `meta.offset` (integer)
    The offset from the start of the dataset, used for pagination.
    Example: 0

  - `meta.next_page` (string)
    The URL to fetch the next page of results.

  - `meta.prev_page` (string)
    The URL to fetch the previous page of results.

## Response 400 fields (application/json):

  - `errors` (array, required)

  - `errors.code` (string)

  - `errors.sub_code` (string)
    Optional identifier that refines the generic `code` category (e.g. `html5-noscript-tag`). Present on HTML5 upload/preview validation errors; absent otherwise.

  - `errors.field` (string)
    Optional when it is a schema error

  - `errors.message` (string)

  - `meta` (object, required)

  - `meta.status` (string, required)

## Response 401 fields (application/json):

  - `errors` (array, required)

  - `errors.code` (string)

  - `errors.sub_code` (string)
    Optional identifier that refines the generic `code` category (e.g. `html5-noscript-tag`). Present on HTML5 upload/preview validation errors; absent otherwise.

  - `errors.field` (string)
    Optional when it is a schema error

  - `errors.message` (string)

  - `meta` (object, required)

  - `meta.status` (string, required)

## Response 403 fields (application/json):

  - `errors` (array, required)

  - `errors.code` (string)

  - `errors.sub_code` (string)
    Optional identifier that refines the generic `code` category (e.g. `html5-noscript-tag`). Present on HTML5 upload/preview validation errors; absent otherwise.

  - `errors.field` (string)
    Optional when it is a schema error

  - `errors.message` (string)

  - `meta` (object, required)

  - `meta.status` (string, required)