Customs Trade Record Count

API docs
https://api.sandbase.ai/v1/api/tendata/trade/record-count

Count the customs records that match a trade query before paying for rows, to check that filters are narrow enough.

Price
From $0.00USD / call
Method
POST
Response
Async JSON
Parameters
3 required · 20 optional

Playground

Input
Data-source side: customs import records or export records.
Query window end, YYYY-MM-DD.
Query window start, YYYY-MM-DD. The window may span at most three years.
Customs HS code, 4+ digits (e.g. '630492'). A 2-digit chapter code works only combined with productDesc or a company name.
Weight range in kilograms, as [min, max].
Exporter company name (min 2 chars). Drop company suffixes and special characters for better matching.
Importer company name (min 2 chars). Drop company suffixes and special characters for better matching.
Quantity range, as [min, max].
Total USD value range, as [min, max].
Set to FUZZY_SINGLE for single-keyword fuzzy matching; omit for the default smart search.
Product description keywords; separate multiple keywords with semicolons (e.g. 'electronics; home appliance').
Quantity unit filter (e.g. 'PCS', 'PKG').
Arrival port name.
Transport mode (e.g. sea, air, road).
Include producer companies (available on Russia/Kazakhstan sources).
Departure port name.
Drop records whose named party is blank (e.g. ["importer"]).
Prefer the vendor's optimized data sources.
USD unit price per kilogram range, as [min, max].
Origin country ISO3 code(s), semicolon-separated (e.g. 'CHN;USA').
Drop records whose named party is a logistics company (e.g. ["exporter"]). Buyers have reported forwarders still being returned, so screen party names yourself.
USD unit price per quantity range, as [min, max].
Destination country ISO3 code(s), semicolon-separated (e.g. 'USA;CHN').
OutputReady

Your output will appear here

Complete the inputs, then click Run.

API README

Customs Trade Record Count

Count the customs records that match a trade query before paying for rows, to check that filters are narrow enough.

Explore more

Related APIs

All APIs
APIPriceResponse
TendataFrom $0 per callAsync JSON
TendataFrom $0.016 per callAsync JSON
TendataFrom $0.0016 per callAsync JSON
TendataFrom $0.019 per callAsync JSON
TendataFrom $0.064 per callAsync JSON
TendataFrom $0.016 per callAsync JSON

Questions

FAQ

How do I use the Customs Trade Record Count API?

Send a POST request to https://api.sandbase.ai/v1/api/tendata/trade/record-count with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

How much does the Customs Trade Record Count API cost?

From $0 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.

What parameters does the Customs Trade Record Count API accept?

Required: catalog (one of imports, exports), endDate (string) and startDate (string). Optional: hsCode (string), weight (array), exporter (string), importer (string), quantity (array) and sumOfUSD (array) and 14 more. The Parameters table and the Playground on this page list every field.

What does the Customs Trade Record Count API return?

A JSON result. This endpoint runs asynchronously, so the response tells you how to fetch the finished result.

Do I need a Tendata developer account or API key?

No. Customs Trade Record Count runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Tendata API access separately.