curl --request POST \
--url https://product-api.thedatacity.com/api/v2/filters \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"rtics": [
"<string>"
],
"cics": [
"<string>"
],
"CompanyNumbers": [
"<string>"
],
"CompanyNumberSetId": "<string>",
"AllowLargeAnalysis": true
}
'{}Get filters with criteria
curl --request POST \
--url https://product-api.thedatacity.com/api/v2/filters \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"rtics": [
"<string>"
],
"cics": [
"<string>"
],
"CompanyNumbers": [
"<string>"
],
"CompanyNumberSetId": "<string>",
"AllowLargeAnalysis": true
}
'{}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Optional criteria. Full field list is under Schema (Example Value may be auto-generated).
Selected RTIC codes.
User CIC codes.
Inline company numbers (typically up to ~50k). Use a low returnCount for huge portfolios so the JSON response stays small — with ?insights=true, insights still aggregates the full matched set.
Use instead of CompanyNumbers when the list is too large to send inline (roughly >50k) — upload via POST /v2/company-number-sets first.
Required when using a large uploaded company number set.
Response
Filter metadata from the product API.
JSON object returned from the upstream product API with no extra shaping by this gateway. Exact properties depend on the operation. Fields may be omitted when the token lacks optional scopes (see config/api.php scope_field_map).