---
title: "List Objects"
method: POST
path: "/fetch/{TypeCode}"
tags: ["General"]
---

# List Objects

`POST /fetch/{TypeCode}`

Retrieves all objects (including details) of the specified type. A [filter](https://api.pricefx.com/rest-api/filtering-sorting-pagination/#advanced-filtering) can be applied.

<!-- theme: info -->
>**Information**: Certain data elements (e.g. lookup table values of any table, including JSON lookup tables / pricing params) should NOT be retrieved with the general fetch commands (**/fetch/{TypeCode}**). Always use the "**...manager.fetch**" API endpoints where they are available. The same applies to update/delete/integrate commands.

<!-- theme: info -->
>**Information**: The following [entities](https://pricefx.atlassian.net/wiki/spaces/KB/pages/99570616/Type+Codes) can intentionally be fetched by any user without any particular [user role](https://pricefx.atlassian.net/wiki/spaces/HELP/pages/3279194862/User+Roles): CN, BR, CS, CLLIAM, CTAM, CTT, CTTAM, C, CAM, CXAM, DMDC, DMF, DMDL, DMDS, DM, DMM, DMR, DMT, DCRAM, FN, IE, JST, JLTVM, MPLIT, MPLAM, MLTVM, MRAM, MT, PYRAM, PGIM, PRAM, PLIM, P, PAM, PXAM, QAM, RBAAM, RRAM, RRS, RRSC, RBT, RBTAM, SC, SCN, SCNAM, SIM, SIAM, UG.

You can choose fields to be returned in the response by employing the `resultFields` or `valueFields` filter:<br>
**resultFields**: returns key-value pairs as objects. This is the more friendly response compared to *valueFields* but the server fetches all fields from the database in the backend which might result in a slower performance. See the [List Product](https://api.pricefx.com/openapi/reference/pricefx/operation/post-productmanager.fetchformulafilteredproducts/)'s **listProductsResponseExample_resultFields** response example.<p>
**valueFields**: returns just an array of values. Use this option if a better performance is required. See the [List Product](https://api.pricefx.com/openapi/reference/pricefx/operation/post-productmanager.fetchformulafilteredproducts/)'s **listProductsResponseExample_valueFields** response example.

## Request body

- object
  - `endRow` integer — The number of the end row that defines the end of the result set's returned objects. Use this parameter if you want to implement paging for results.
  - `operationType` string
  - `startRow` integer — The number of the first row that defines the start of the result set's returned objects. Use this parameter if you want to implement paging for results.
  - `textMatchStyle` 'startsWith' | 'exact' | 'substring'
  - `data` object
    - `_constructor` string
    - `operator` string
    - `criteria` object[]
      - `fieldName` string
      - `operator` 'equals' | 'iEquals' | 'notEqual' | 'iNotEqual' | 'greaterThan' | 'greaterOrEqual' | 'lessOrEqual' | 'lessThan' | 'isNull' | 'notNull' | 'contains' | 'iContains' | 'containsPattern' | 'iContainsPattern' | 'notContains' | 'iNotContains' | 'startsWith' | 'iStartsWith' | 'notStartsWith' | 'iNotStartsWith' | 'endsWith' | 'iEndsWith' | 'notEndsWith' | 'iNotEndsWith' | 'iBetween' | 'iBetweenInclusive' | 'inSet' | 'notInSet' — Specify an operator of the filter criteria.
      - `value` string

## Response `200`

A general response that contains `data` property with a content depending on returned objects (e.g., Product master table fields when calling the `/fetch/P` endpoint). Can be `null`.

- object
  - `response` object
    - `node` string
    - `data` object, nullable
    - `status` integer
    - `startRow` integer
    - `endRow` integer

---

[API](https://skmtc.net/pricefx/apis/the-pricefx-backend-api.md) · [All operations](https://skmtc.net/pricefx/apis/the-pricefx-backend-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pricefx/the-pricefx-backend-api/versions/0850b5d6be73/schema)