China Export Licence Catalogue API

Enter an HS code or product name to check whether a product needs an export licence, which type, the regulatory document code and the declaration unit.

We continuously compile the Export Licence Goods Catalogue and the catalogue of 300 steel products subject to export licensing issued by MoC and GAC, cleaning, standardising and relationship-modelling HS codes, export licence types and regulatory document codes, delivered uniformly through a REST API.

No need to check catalogues and notices line by line yourself.

View API Docs

Enterprise solution enquiryJSON APIAnnual catalogue sync

OverviewLicence typeRegulatory codeUnitSource

Goods search key 3

1 0102900000 Exact HS code matching

Data sources: Export licence catalogue
Code: 10 digits valid

2 Live cattle Product name

Data sources: Catalogue entries
Resolve: Normalised

3 Live cattle Goods category

Data sources: Catalogue category
Classification: Classified

Master goods entity parsed

Live cattle
HS 0102900000

Goods category: Live cattle
Goods name: Live cattle
Licence type: Export licence
Regulatory document code: 4
Declaration unit: head
Effective date: 2026-01-01
Source notice: No. 89 of 2025

43Export licence goods categories (2026)

300Steel product export licences (Notice No. 79)

10 digitsHS codes listed item by item

Annual updateContinuous catalogue notice sync

The catalogues are free to look up, but they are far from being "ready for a customs system".

The real problem isn't whether the catalogue exists, but how to turn public data scattered across catalogues, notices and HS code tables into export licence results your business systems can fetch in one call and track over time.

Raw data scattered across multiple sources MoC / GAC public catalogues

001Export licence catalogueNotice No. 89 of 2025

002Steel product export licencesNotice No. 79 of 2025

003Customs HS code tableProduct code

004Regulatory document code tableCode 4

Export licence record aggregation One call · four data categories Aggregated, normalised and delivered

01
Data is scattered
The export licence catalogue, the steel product export licensing catalogue, the HS code table and regulatory document codes live in different files with different naming and definitions, so your systems have to stitch them together.
02
Annual catalogue updates
The catalogue is issued and superseded by notice each year; product codes and regulatory codes change with tariff revisions, so companies must keep tracking whether their export goods are affected.
03
Hard to query programmatically
The official catalogues are published as notice PDFs and tables; judging export licence requirements in bulk by HS code means doing your own parsing and modelling, with no direct system integration.
04
Maintenance costs keep piling up
Tariff revisions, notice supersessions and code changes all require long-term engineering effort, and missed updates easily cause declaration errors.

From scattered public catalogues to a directly callable export licence record

An HS code passes through six auditable stages to become stable, structured, linkable JSON.

Collect

Continuous sync with MoC and GAC public catalogues

source.capture()

Clean

Normalises product codes, units and note formats

parse · dedupe

Normalize

Unifies export licence type and regulatory document code naming

schema.map()

Relate

Links HS codes to export licence types and source notices

graph.link()

Aggregate

One call returns export licence type, code, unit and source

aggregate.v1

Deliver

Delivered to your business systems via a stable REST API

json_api.v1

You don't have to maintain catalogue parsing, notice tracking or HS code mapping.Call the API and use the results directly.

One API covering the core export licence lookup scenarios

Unified REST API · JSON responses · Bearer token authentication. HS code export licence lookup is the core of the product, with the other capabilities built on the same data model.

HS code export licence lookup API

Import/export compliance and pre-declaration screening

Enter a 10-digit HS code to check whether the product needs an export licence, the licence type, regulatory document code, declaration unit, notes, effective date and source notice. One call aggregates four data types.

Licence type
Regulatory document code
Goods category
Declaration unit
Source notice and effective date

Pre-declaration screening · compliance review · goods classification support · trade SaaS embedding

GET /v1/export-license/lookup?hsCode=0102900000

Static demo · Sample response200 OK

{
  "query": "0102900000",
  "goods": {
    "hs_code": "0102900000",
    "goods_name": "Live cattle",
    "category": "Live cattle",
    "unit": "head"
  },
  "license": {
    "required": true,
    "license_type": "Export licence",
    "supervision_code": "4",
    "effective_from": "2026-01-01",
    "source": "Ministry of Commerce、GAC Notice No. 89 of 2025"
  },
  "source": "MOFCOM"
}

API 02

Query by goods category API

Returns all HS codes under a goods category with their export licence requirements, for batch verification of a whole product category.

GET /v1/export-license/by-category?category=live-cattle JSON

Whole-category verificationReturns all HS codes under a category in one call

Licence type flaggingExport licence

Catalogue change trackingContinuous tracking of annual notice changes

API 03

Search by product name API

Search catalogue entries by product name keyword and get the HS code and export licence requirements.

GET /v1/export-license/by-name?keyword=live-cattle Product name · HS code · licence type

API 04

Export licence catalogue list API

Returns the currently effective export licence catalogue list with notice numbers and effective dates, for system-side caching and comparison.

GET /v1/export-license/catalogs Catalogue name · notice number · effective date · supersession

API 05

Batch HS code check API

Submit a list of HS codes at once and receive each code’s export licence requirements asynchronously — ideal for bulk pre-checking declarations.

POST /v1/export-license/batch Async jobs · Batch results · CSV export

This data can flow into your real business processes

Not another back office to open, but export licence results where customs declaration, compliance review and product management actually happen.

Customs brokers / freight forwarders

Bulk-check whether HS codes require a licence during declaration entry, flagging the export licence type and regulatory code up front to reduce rejections.

Customs HS listExport licence lookup APILicence requirement notice

Importer/exporter compliance

Confirm whether goods need an export licence during export and contracting, and build licence requirements into your compliance review flow.

Product HSHS lookup APICompliance conclusion

Cross-border e-commerce / trade SaaS

Embed export licence requirements into product management and ordering so operations are warned about restricted goods and required documents.

Product dimensionCatalogue list APIRestricted flag

ERP / customs system vendors

Integrate export licence type and regulatory code as standard fields in your customs module, updated automatically with the annual catalogue.

HS fieldsBatch check APIStructured data

Data and research firms

Use structured catalogue data to research the distribution of export-controlled goods and annual adjustment trends.

Category dimensionQuery by category APIStructured datasets

Data comes from the official 2026 published catalogue, organised item by item

Based on MoC and GAC 2026 Compiled from the Export Licence Goods Catalogue (Notice No. 89 of 2025) and the Catalogue of 300 Steel Products Subject to Export Licensing (Notice No. 79 of 2025). It is not a live feed; the field structure matches real catalogue entries.

HS codeGoods nameExport licence type / regulatory code

0102900000Live cattleExport licence · code 4

0103920000Live pigsExport licence · code 4

1006300000Rice (long-grain)Export licence · code 4

2709000000Petroleum crude oil (natural crude)Export licence · code 4

4407990090Sawn timberExport licence · code 4

The entries above are real catalogue samples (effective in 2026). Full coverage spans the 43 goods categories in the Export Licence Goods Catalogue and the catalogue of 300 steel products subject to export licensing, with HS codes listed item by item; the item-level detail is archived in export_license_sample.json.

The export licence lookup API supports further analysis

Annual catalogue change comparison
HS code classification
Regulatory document code distribution
Goods category coverage statistics
Notice supersession tracking
Restricted goods list export

The value of an API is more than "returning the catalogue to you"

GooFuture's core value lies before the data reaches the API: turning public data scattered across catalogues, notices and HS code tables into an export licence data model that is program-friendly, linkable and maintainable.

Aggregate

Both catalogue types in one response

Aggregates the export licence catalogue and the steel product export licensing catalogue into a single licence record, cutting repeated queries.

Two catalogues → one record

Resolve

HS code normalisation

Normalises differing product codes and names across catalogues so systems can match them.

Multiple naming schemes → unified entity

Structure

Export licence type standardisation

Unifies export licences with regulatory document code (4).

Catalogue text → standard fields

Flag

Source and effective date flags

Records source notice numbers, effective dates and supersession links to provide a compliance basis.

Notice text → traceable fields

Update

Annual sync

Continuous sync after each annual catalogue release, cutting your maintenance costs.

Source → sync

From enquiry to your first API call in just three steps

Code and responses are static samples. Your consultant will propose an integration plan based on data scope, call volume and delivery method.

01
Contact a consultant
Scan the QR code to add us on WeCom and tell us your business scenario, the data you need and your expected call volume.
02
Confirm the plan
Confirm endpoint scope, monitoring conditions, delivery method and enterprise support needs.
03
Start integration
Get your API key and integration materials, then wire the JSON results into your customs, compliance or SaaS product.

cURLResponse

curl "https://api.goofuture.com/v1/export-license/lookup?hsCode=0102900000" \
  -H "Authorization: Bearer YOUR_API_KEY"

Static demo · JSON response200 OK

{
  "data": {
    "hs_code": "0102900000",
    "goods_name": "Live cattle",
    "license_type": "Export licence",
    "supervision_code": "4",
    "unit": "head",
    "effective_from": "2026-01-01"
  }
}

From testing to production

Choose a plan by call volume, batch capability, notification method and enterprise support. Your consultant will quote based on your business needs.

Basic

For API testing and product validation

Contact a consultant

Monthly requests: 100
Core endpoints: HS lookup / lookup by category
Rate limits: Basic rate limiting
Monitoring conditions: —

Standard

For customs brokers and small teams

Contact a consultant

Monthly requests: 5,000
Core endpoints: All core queries
Monitoring conditions: 10 conditions
Notification method: Email

Recommended plan

Professional

For importers, exporters and SaaS

Contact a consultant

Monthly requests: 50,000
Concurrency: Higher concurrency
Monitoring conditions: 50 conditions
Data delivery: Webhook / CSV

Enterprise

For platforms, data companies and large enterprises

Contact a consultant

Monthly requests: High-volume usage
Data delivery: Incremental data push
Customisation: Field / dataset
Technical support: Enterprise technical support

The questions worth confirming before integrating an export licence data API

Straight answers on public catalogues, HS code matching, update frequency and commercial integration.

The catalogue data is public — why do I still need this API?

If you only need to look up a product occasionally, the official MoC and GAC channels are enough. GooFuture is built for teams that need bulk lookups, system integration, unified fields and continuous updates — aggregating public data scattered across the export licence catalogue, the steel product export licensing catalogue, the HS code table and the regulatory code table into an export licence record you can get in one call.

Where does the data come from?

Data comes from the Export Licence Goods Catalogue publicly issued by China's Ministry of Commerce and General Administration of Customs with its corresponding notice (No. 89 of 2025), plus the Catalogue of 300 Steel Products Subject to Export Licensing (No. 79 of 2025). GooFuture collects, cleans, standardises, links and aggregates the raw catalogues and delivers them via API.

How often is the data updated?

The catalogue is published annually, usually updated by public notice early each year and replacing the previous year's version. We keep syncing after each new notice; see the API documentation for specifics.

Which fields are returned for an HS code?

The HS code export licence lookup API returns product name, goods category, licence type (export licence), regulatory document code (4), declaration unit, notes, effective date and source notice number.

What is the difference between an export licence and an import licence?

An export licence applies to restricted exports (regulatory code 4) while an import licence applies to restricted imports (regulatory code 1); they differ in direction and applicable stage. The API returns the exact type and code per the catalogue so export systems can decide directly.

How are you different from the official catalogue publishers?

The official catalogues are published as notices and tables, one product at a time, with no direct system integration. GooFuture parses the catalogues, normalises HS codes and standardises export licence types into a single call, with batch checks and continuous sync. All raw data comes from public catalogues.

Can I integrate the data into my own customs / ERP product?

Yes. The API can be used in internal systems and integrated into customs declaration, compliance review, cross-border e-commerce and trade SaaS products; commercial usage is governed by the applicable plan and service agreement.

How do I tell whether a product needs an export licence?

Pass a product HS code to the export licence lookup API to get whether a licence is required, the licence type and the regulatory code; if the catalogue does not list it, the API returns a no-licence conclusion so your system can decide automatically.

No more checking catalogues and notices line by line yourself.

From collecting the public catalogues to HS code normalisation, export licence type standardisation and source notice linking — we handle it all. Your systems just call the API.

Enterprise consultant onboarding · REST API · JSON responses

China Export Licence Catalogue API

Goods search key 3

Master goods entity parsed

Data is scattered

Annual catalogue updates

Hard to query programmatically

Maintenance costs keep piling up

Collect

Clean

Normalize

Relate

Aggregate

Deliver

HS code export licence lookup API

Query by goods category API

Search by product name API

Export licence catalogue list API

Batch HS code check API

Customs brokers / freight forwarders

Importer/exporter compliance

Cross-border e-commerce / trade SaaS

ERP / customs system vendors

Data and research firms

The export licence lookup API supports further analysis

Both catalogue types in one response

HS code normalisation

Export licence type standardisation

Source and effective date flags

Annual sync

Contact a consultant

Confirm the plan

Start integration

No more checking catalogues and notices line by line yourself.