EU CN Code Migration API

API ID 15196

Check how EU Combined Nomenclature (CN) codes change from 2026 to 2027: status, successor codes and manual review flags. Correspondences are indicative and may require manual review. Batch requests accept up to 10 codes.

API Documentation

Endpoints

Request
Returns ok when the service is running and the CN database is available. Useful for uptime monitoring; it does not count CN data.
Endpoint ID: 40656
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40656/service+health+check
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "status": "ok"
}
Service Health Check — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40656/service+health+check' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Describes the running API version, when the CN data was last imported, the official publications it was built from and the meaning of every migration status returned by the other endpoints.
Endpoint ID: 40657
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40657/api+status+and+data+sources
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "api_version": "1.0.0",
    "data": {
        "imported_at": "2026-11-18T17:19:47+00:00",
        "schema_version": 1,
        "available_years": [
            2026,
            2027
        ],
        "transitions": [
            {
                "from_year": 2026,
                "to_year": 2027
            }
        ],
        "correspondence_basis": "derived_from_official_texts",
        "coverage": "All 8-digit CN subheadings of Annex I to Regulation (EEC) No 2658/87 as published for 2026 and 2027. TARIC (10-digit) codes, duty rates and national codes are not covered."
    },
    "status_definitions": {
        "unchanged": "The code exists in both versions with identical official description and parent lines, and no CN code was added or removed in its 6-digit HS subheading.",
        "modified": "The code exists in both versions, but its official description or a parent line changed, or other CN codes were added/removed in the same 6-digit HS subheading, so its scope may have changed. Manual review required.",
        "added": "The code exists only in the target version (new code). Possible predecessor codes are listed.",
        "removed": "The code exists only in the source version and no corresponding code could be identified.",
        "replaced": "The code exists only in the source version and corresponds to exactly one new code, which itself has no other predecessor (one-to-one).",
        "split": "The code exists only in the source version and corresponds to two or more new codes, none of which has another predecessor (one-to-many). Manual review required.",
        "merged": "The code exists only in the source version and its single corresponding code also receives goods from other codes (many-to-one). Manual review required.",
        "ambiguous": "The code exists only in the source version and its correspondence is many-to-many; all candidate codes are returned. Manual review required.",
        "unknown": "The code is well formed but is not a CN code in either version covered by this API."
    },
    "correspondence_basis_definitions": {
        "official_correspondence_table": "Pair listed in an official EU correspondence table (Eurostat).",
        "derived_same_hs6_new_codes": "Derived from the two official annexes: the code was deleted and the candidate was created within the same 6-digit HS subheading (HS subheadings are identical in CN 2026 and CN 2027, so goods cannot move to another HS subheading).",
        "derived_same_hs6_retained_codes": "Derived from the two official annexes: no new code exists in the same 6-digit HS subheading, so the candidate is an existing code of that subheading."
    },
    "sources": [
        {
            "role": "cn_annex_2026",
            "title": "Commission Implementing Regulation (EU) 2025/1926, Annex I (Combined Nomenclature 2026), Formex 4 XML, English",
            "publisher": "Publications Office of the European Union (EUR-Lex / Cellar)",
            "url": "http://publications.europa.eu/resource/cellar/c3c0d050-b5fa-11f0-b37f-01aa75ed71a1.0006.02/DOC_1",
            "license": "© European Union. Reuse authorised under Commission Decision 2011/833/EU (commercial and non-commercial reuse permitted, source must be acknowledged, changes must be indicated).",
            "sha256": "23324fedd02019fdff810db0f7fd3e42ff11300e7b5eeec4fe8be75ba0f7bd12",
            "retrieved_at": "2026-11-18T17:19:41+00:00",
            "used_for": "Complete list of CN 2026 8-digit codes, official descriptions, hierarchy, supplementary units",
            "modifications": "Extracted the 'Schedule of customs duties' tables; dashes converted to depth; duty rates not used."
        },
        {
            "role": "cn_annex_2027",
            "title": "Commission Implementing Regulation (EU) 2026/2163, Annex I (Combined Nomenclature 2027), Formex 4 XML, English",
            "publisher": "Publications Office of the European Union (EUR-Lex / Cellar)",
            "url": "http://publications.europa.eu/resource/cellar/f70de77f-d403-11f1-9458-01aa75ed71a1.0006.02/DOC_1",
            "license": "© European Union. Reuse authorised under Commission Decision 2011/833/EU (commercial and non-commercial reuse permitted, source must be acknowledged, changes must be indicated).",
            "sha256": "f99ae077f81f795d9a29e749ea5e5d5979ea2a4af6b24f726c3945d96c47760e",
            "retrieved_at": "2026-11-18T17:19:41+00:00",
            "used_for": "Complete list of CN 2027 8-digit codes, official descriptions, hierarchy, supplementary units",
            "modifications": "Extracted the 'Schedule of customs duties' tables; dashes converted to depth; duty rates not used."
        },
        {
            "role": "eurostat_cn_texts",
            "title": "Eurostat Comext CN classification (CN.txt, English)",
            "publisher": "Eurostat",
            "url": "https://ec.europa.eu/eurostat/api/dissemination/files/?sort=1&downfile=comext%2FCOMEXT_METADATA%2FCLASSIFICATIONS_AND_RELATIONS%2FCLASSIFICATIONS%2FENGLISH%2FCN.txt",
            "license": "© European Union, Eurostat. Licensed under CC BY 4.0 (Commission Decision 2011/833/EU).",
            "sha256": "da4703237379350c8f86d8d2922e1bf4553b72d630ba6088bbd5462438bf4dcd",
            "retrieved_at": "2026-11-18T17:19:41+00:00",
            "used_for": "Cross-check of the CN 2026 code list; self-explanatory English texts for CN 2026 codes",
            "modifications": "Filtered to 8-digit codes valid for the whole of 2026; Comext pseudo-codes dropped."
        },
        {
            "role": "eurostat_pred_succ",
            "title": "Eurostat Comext CN8 predecessor/successor relations",
            "publisher": "Eurostat",
            "url": "https://ec.europa.eu/eurostat/api/dissemination/files/?sort=1&downfile=comext%2FCOMEXT_METADATA%2FCLASSIFICATIONS_AND_RELATIONS%2FRELATIONS%2FCN8-PRED-SUCC.txt",
            "license": "© European Union, Eurostat. Licensed under CC BY 4.0 (Commission Decision 2011/833/EU).",
            "sha256": "a5a28c853da4db6a16c4f5f06abbf59d69b9eee468d838842fcd3ecea5db5fba",
            "retrieved_at": "2026-11-18T17:19:41+00:00",
            "used_for": "Official CN 2026 -> CN 2027 correspondences, when Eurostat has published them",
            "modifications": "Filtered to successors valid from 1 January 2027."
        }
    ],
    "attribution": "© European Union. Reuse authorised under Commission Decision 2011/833/EU (commercial and non-commercial reuse permitted, source must be acknowledged, changes must be indicated). © European Union, Eurostat. Licensed under CC BY 4.0 (Commission Decision 2011/833/EU).",
    "disclaimer": "Indicative information derived from official EU publications. Correspondences between CN versions are not legally binding classifications; the classification of specific goods must be confirmed with the official texts, the customs authorities or a Binding Tariff Information decision. Not affiliated with or endorsed by the European Union or any national authority."
}
API Status and Data Sources — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40657/api+status+and+data+sources' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Lists the CN versions available in the API (currently 2026 and 2027) with their legal basis, Official Journal reference, adoption date, period of application, number of 8-digit codes and which version is in force today.
Endpoint ID: 40658
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40658/list+cn+versions
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "versions": [
        {
            "year": 2026,
            "legal_basis": "Commission Implementing Regulation (EU) 2025/1926",
            "celex": "32025R1926",
            "eli": "http://data.europa.eu/eli/reg_impl/2025/1926/oj",
            "official_journal": "OJ L, 2025/1926, 31.10.2025",
            "eur_lex_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1926",
            "adopted": "2025-09-22",
            "applies_from": "2026-01-01",
            "applies_to": "2026-12-31",
            "in_force_today": true,
            "cn_code_count": 9791
        },
        {
            "year": 2027,
            "legal_basis": "Commission Implementing Regulation (EU) 2026/2163",
            "celex": "32026R2163",
            "eli": "http://data.europa.eu/eli/reg_impl/2026/2163/oj",
            "official_journal": "OJ L, 2026/2163, 30.10.2026",
            "eur_lex_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32026R2163",
            "adopted": "2026-09-17",
            "applies_from": "2027-01-01",
            "applies_to": "2027-12-31",
            "in_force_today": false,
            "cn_code_count": 9809
        }
    ],
    "default_year": 2026
}
List CN Versions — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40658/list+cn+versions' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Real counts of CN codes per year and of the changes between 2026 and 2027: added, removed, split, merged, ambiguous and modified codes, changes per chapter, and how many codes require manual review.
Endpoint ID: 40659
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40659/cn+change+statistics
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "cn_codes_per_year": {
        "2026": 9791,
        "2027": 9809
    },
    "transitions": [
        {
            "from_year": 2026,
            "to_year": 2027,
            "added_codes": 35,
            "removed_codes": 17,
            "retained_codes": 9774,
            "by_status": {
                "unchanged": 9756,
                "modified": 18,
                "added": 35,
                "removed": 0,
                "replaced": 0,
                "split": 10,
                "merged": 0,
                "ambiguous": 7
            },
            "correspondences": 55,
            "correspondences_by_basis": {
                "derived_same_hs6_new_codes": 55
            },
            "hs_subheadings_with_new_or_deleted_codes": 13,
            "changed_codes_by_chapter": {
                "02": 3,
                "03": 3,
                "39": 6,
                "44": 10,
                "64": 7,
                "72": 5,
                "73": 5,
                "76": 10,
                "84": 1,
                "85": 20
            },
            "manual_review_required": 70
        }
    ]
}
CN Change Statistics — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40659/cn+change+statistics' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Returns the official description, hierarchy, chapter, heading, HS subheading and supplementary unit of an 8-digit CN code in a given CN version, and the versions in which the code is valid. Spaces and dots in the code are ignored.
Endpoint ID: 40660
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40660/look+up+cn+code
INPUT PARAMETERS

Look Up CN Code — Endpoint Features

Object Description
year Optional CN version year (2026 or 2027). Defaults to the version in force today.
code Required

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

year
API EXAMPLE RESPONSE
JSON
{
    "code": "02013000",
    "code_formatted": "0201 30 00",
    "year": 2026,
    "valid": true,
    "valid_in_years": [
        2026
    ],
    "version": {
        "legal_basis": "Commission Implementing Regulation (EU) 2025/1926",
        "applies_from": "2026-01-01",
        "applies_to": "2026-12-31",
        "eur_lex_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32025R1926"
    },
    "description": "Boneless",
    "hierarchy": [
        "Meat of bovine animals, fresh or chilled"
    ],
    "chapter": "02",
    "heading": "0201",
    "hs_subheading": "020130",
    "supplementary_unit": null,
    "eurostat_self_explanatory_text": "Fresh or chilled bovine meat, boneless",
    "disclaimer": "Indicative information derived from official EU publications. Correspondences between CN versions are not legally binding classifications; the classification of specific goods must be confirmed with the official texts, the customs authorities or a Binding Tariff Information decision. Not affiliated with or endorsed by the European Union or any national authority."
}
Look Up CN Code — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40660/look+up+cn+code?year=2026&code=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Explains what happens to a CN code between two versions: its migration status, the candidate successor or predecessor codes with their descriptions, and whether a manual classification review is required before the result is applied.
Endpoint ID: 40661
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40661/cn+code+migration+2026+to+2027
INPUT PARAMETERS

CN Code Migration 2026 to 2027 — Endpoint Features

Object Description
from_year Optional Source CN version year. Currently only 2026 is supported.
to_year Optional Target CN version year. Currently only 2027 is supported.
code Required

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

from_year
to_year
API EXAMPLE RESPONSE
JSON
{
    "code": "02013000",
    "code_formatted": "0201 30 00",
    "from_year": 2026,
    "to_year": 2027,
    "status": "split",
    "status_definition": "The code exists only in the source version and corresponds to two or more new codes, none of which has another predecessor (one-to-many). Manual review required.",
    "valid_in_from_year": true,
    "valid_in_to_year": false,
    "manual_review_required": true,
    "reasons": [
        "correspondence_derived_from_official_texts"
    ],
    "from": {
        "description": "Boneless",
        "hierarchy": [
            "Meat of bovine animals, fresh or chilled"
        ],
        "chapter": "02",
        "heading": "0201",
        "hs_subheading": "020130",
        "supplementary_unit": null,
        "eurostat_self_explanatory_text": "Fresh or chilled bovine meat, boneless"
    },
    "to": null,
    "successor_candidates": [
        {
            "code": "02013010",
            "code_formatted": "0201 30 10",
            "year": 2027,
            "description": "Tenderloin, rib steak, flank steak, sirloin and rump steak",
            "hierarchy": [
                "Meat of bovine animals, fresh or chilled",
                "Boneless"
            ],
            "basis": "derived_same_hs6_new_codes"
        },
        {
            "code": "02013090",
            "code_formatted": "0201 30 90",
            "year": 2027,
            "description": "Other",
            "hierarchy": [
                "Meat of bovine animals, fresh or chilled",
                "Boneless"
            ],
            "basis": "derived_same_hs6_new_codes"
        }
    ],
    "predecessor_candidates": [],
    "other_codes_in_same_hs_subheading": [
        {
            "code": "02013010",
            "status": "added"
        },
        {
            "code": "02013090",
            "status": "added"
        }
    ],
    "disclaimer": "Indicative information derived from official EU publications. Correspondences between CN versions are not legally binding classifications; the classification of specific goods must be confirmed with the official texts, the customs authorities or a Binding Tariff Information decision. Not affiliated with or endorsed by the European Union or any national authority."
}
CN Code Migration 2026 to 2027 — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40661/cn+code+migration+2026+to+2027?from_year=2026&to_year=2027&code=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Paginated list of every CN code that changes between two versions. Filter by change type and by 2-digit chapter to plan a catalogue migration or review only the codes relevant to your products.
Endpoint ID: 40662
GET https://zylalabs.com/api/15196/eu+cn+code+migration+api/40662/list+changed+cn+codes
INPUT PARAMETERS

List Changed CN Codes — Endpoint Features

Object Description
type Optional Change type to return: added, removed, replaced, split, merged, ambiguous or modified. Omit for all changes.
chapter Optional 2-digit CN chapter to filter on, e.g. 85 for electrical machinery.
page Optional Page number of the results, starting at 1.
page_size Optional Number of items per page, from 1 to 100 (default 50).
from_year Optional Source CN version year. Currently only 2026 is supported.
to_year Optional Target CN version year. Currently only 2027 is supported.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

type
chapter
page
page_size
from_year
to_year
API EXAMPLE RESPONSE
JSON
{
    "from_year": 2026,
    "to_year": 2027,
    "type": "split",
    "chapter": null,
    "page": 1,
    "page_size": 3,
    "total": 10,
    "total_pages": 4,
    "items": [
        {
            "code": "02013000",
            "code_formatted": "0201 30 00",
            "status": "split",
            "presence": "only_in_from",
            "manual_review_required": true,
            "description": "Boneless",
            "hierarchy": [
                "Meat of bovine animals, fresh or chilled"
            ],
            "related_codes": [
                "02013010",
                "02013090"
            ]
        },
        {
            "code": "39076100",
            "code_formatted": "3907 61 00",
            "status": "split",
            "presence": "only_in_from",
            "manual_review_required": true,
            "description": "Having a viscosity number of 78 ml/g or higher",
            "hierarchy": [
                "Polyacetals, other polyethers and epoxide resins, in primary forms; polycarbonates, alkyd resins, polyallyl esters and other polyesters, in primary forms",
                "Poly(ethylene terephthalate)"
            ],
            "related_codes": [
                "39076110",
                "39076190"
            ]
        },
        {
            "code": "39076900",
            "code_formatted": "3907 69 00",
            "status": "split",
            "presence": "only_in_from",
            "manual_review_required": true,
            "description": "Other",
            "hierarchy": [
                "Polyacetals, other polyethers and epoxide resins, in primary forms; polycarbonates, alkyd resins, polyallyl esters and other polyesters, in primary forms",
                "Poly(ethylene terephthalate)"
            ],
            "related_codes": [
                "39076910",
                "39076990"
            ]
        }
    ]
}
List Changed CN Codes — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15196/eu+cn+code+migration+api/40662/list+changed+cn+codes?type=split&chapter=85&page=1&page_size=50&from_year=2026&to_year=2027' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the EU CN Code Migration API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime.

(Save 2 months with annual billing 🎉)

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Check how EU Combined Nomenclature (CN) codes change from 2026 to 2027: status, successor codes and manual review flags. Correspondences are indicative and may require manual review. Batch requests accept up to 10 codes.

EU CN Code Migration API FAQs

The EU CN Code Migration API allows users to check how EU Combined Nomenclature (CN) codes are expected to change from the 2026 to the 2027 classification periods. It provides information on the status of these changes, identifies successor codes, and flags codes that may require manual review.

The API provides the status of a CN code's migration, the corresponding successor code for the next classification period (if applicable), and a flag indicating whether manual review is recommended for the identified correspondence.

Yes, the API supports batch requests. Users can submit up to 10 CN codes in a single batch request to efficiently check their migration status.

The API accepts a list or array of CN codes as input for batch requests. The exact structure will depend on the specific implementation, but it will typically be a JSON array of strings, where each string is a CN code.

CN codes are typically represented as alphanumeric strings. The API expects these codes to be provided as string data types.

The API response is typically returned in JSON format. For each input CN code, it will provide details such as the migration status, the successor code, and a manual review flag.

The 'status' field indicates the outcome of the CN code migration check. This could include information like 'migrated', 'no change', 'discontinued', or other relevant statuses related to the transition between classification periods.

The 'successor_code' field provides the new CN code that is expected to replace the input code in the subsequent classification period (e.g., 2027 if checking from 2026). This field may be null or absent if there is no direct successor or if the code is discontinued.

The 'manual_review_flag' is a boolean or indicator that suggests whether the automatically determined correspondence between the old and new CN code requires further human verification. A 'true' or 'yes' value indicates that manual review is recommended due to potential complexities or ambiguities.

Businesses involved in international trade can use this API to proactively identify how their current CN codes will change. This allows them to update their product classifications, customs declarations, and internal systems in advance, ensuring compliance and avoiding delays.

The core value proposition is to provide clarity and foresight into upcoming changes in EU Combined Nomenclature codes, enabling businesses to manage transitions smoothly, maintain compliance, and optimize their trade operations.

No, the API explicitly states that correspondences are indicative. The 'manual_review_flag' highlights that some transitions may require expert human judgment to ensure the correct classification.

A single lookup is useful for quickly verifying the migration status of a specific product's CN code, perhaps when a new product is being introduced or when a specific classification is in question.

The API can be integrated by making calls to its endpoints with lists of CN codes from the customs management system. The returned migration data can then be used to update product master data, flag items for review, or automate classification updates.

The batch request feature significantly improves efficiency by allowing users to check multiple CN codes simultaneously, reducing the number of API calls and processing time, which is crucial for large product catalogs.

Based on the description, the API focuses specifically on the transition from 2026 to 2027. It does not appear to provide historical migration data for other periods.

A single query response would typically be a JSON object containing fields like 'original_code', 'migration_status', 'successor_code', and 'manual_review_flag' for the queried code.

By providing advance notice of CN code changes and highlighting potential issues requiring manual review, the API helps businesses ensure their classifications are up-to-date and compliant with the latest EU trade regulations.

For a customs broker, the 'manual_review_flag' acts as an alert system. It directs their attention to specific CN code transitions that are not straightforward and require their expertise to confirm the correct classification, thereby reducing the risk of errors and penalties.

The provided API description focuses on the outcome of the migration (status, successor, review flag) rather than the underlying reasons for the change. Detailed explanations for specific code changes would likely require consulting official EU tariff publications.

It returns a small JSON object such as `{"status":"ok"}` when the API service is running and the CN database is available. This endpoint is intended for operational monitoring and does not return CN codes, migration results, or classification data.

It returns the API version, data import metadata, schema version, available CN years, supported transitions, correspondence basis, coverage statement, and definitions for migration statuses. Use it to interpret response fields and verify which datasets and transitions are available.

Coverage includes all 8-digit CN subheadings in Annex I to Regulation (EEC) No 2658/87 for the published 2026 and 2027 versions. Responses can include descriptions, hierarchy, chapter, heading, HS subheading, supplementary units, and validity by year. TARIC codes, duty rates, and national codes are excluded.

It returns a JSON array describing each available CN version. Each item may include the year, legal basis, CELEX and ELI identifiers, Official Journal reference, EUR-Lex URL, adoption date, application period, code count, and whether that version is currently in force.

A migration response identifies the source and target years, status, status definition, validity in each year, manual-review flag, reasons, and source and target classification details. For non-direct changes, `successor_candidates` or predecessor candidates may list related codes with descriptions.

Statuses include `unchanged`, `modified`, `added`, `removed`, `replaced`, `split`, `merged`, and `ambiguous`. Their precise meanings are provided by the API Status endpoint. For example, `split` indicates one source code corresponds to multiple new codes and requires manual review.

Requests can specify the source year, target year, change `type`, 2-digit `chapter`, `page`, and `page_size`. The response includes the applied filters, page information, total count, total pages, and an `items` array containing changed codes, status, presence, descriptions, and related codes.

CN codes are 8-digit values and may be supplied with spaces or dots; these separators are ignored. Responses provide both the compact `code` and formatted `code_formatted` value. A lookup also reports `valid` and `valid_in_years`, allowing clients to distinguish an invalid code from one valid only in another CN version.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs