Global Trade Content (GTC)
Introducing ECN API for tracking export control number changes by country and list
What it is:
We introduced a new ECN API
to track changes to ECN numbers
by country or export control list for a given date range. You receive a list of changed ECN identifiers, country, export control list, modified data fields, and operation type. Access details in the API documentation
.Benefit to you:
You identify ECN changes instantly, streamline compliance reviews, and automate updates based on country and export control list. You save time by filtering for relevant changes, improving impact assessment and data accuracy.Enhanced client credential page
What it is:
We enhanced the Client Credential
list page with two new columns: Asset
displays the associated product, and Monthly Calls Quota
shows subscription limits with clear formatting, including “Unlimited” where applicable.Benefit to you:
You quickly identify each credential’s product and usage limits, making it easier to manage subscriptions and monitor quotas directly from the grid.Enhanced discrepancy check service for SQL and Elastic sync
What it is:
We updated the Discrepancy Check Service
to verify entity IDs
as well as record counts between SQL and Elastic databases.Benefit to you:
Improves data integrity and reliability by validating entity-level consistency, reducing errors, and ensuring accurate synchronization for critical operations.HS APIs now support filtering by source/destination country for easier queries
What it is:
Our HS APIs
now support filtering by import
or export country
even if the corresponding HS code isn’t provided. You can provide just one HS code (either import or export), simplifying your queries and reducing validation errors. Benefit to you:
- Fewer hard failures:You can avoid being blocked by validation errors when one HS code is missing, ensuring smoother workflows.
- Simpler integrations:Submit the HS code you have, and still retrieve accurate charges and controls filtered by the appropriate country, improving efficiency.
ECN APIs now support localized ECN numbers in responses (currently supported for Japan)
What it is
: ECN APIs
now support an optional request parameter includeLocalECNNumber (default false) that works with cultureCode. When set to true and a cultureCode is provided, responses include the number as given in source in a new attribute localECNNumber. Benefit to you
: Delivers localized ECN identifiers directly in API responses, enabling region‑specific compliance checks and reducing the need for separate lookups or mappings.ECN APIs enhanced with category-based filtering
What it is
: ECN APIs
now supports an optional category parameter. When provided, the API returns ECN data only for numbers within the specified category. If left blank, results include all matching ECNs as before. Benefit to you
: Enables more targeted searches by category, reducing unnecessary data and improving efficiency in retrieving relevant ECN information.ECN Headings API adds last-updated date for improved transparency
What it is
: The ECN Headings API
now includes a new field showing the date when the list was last updated, providing users with clear visibility into data freshness.Benefit to you
: Improves transparency and confidence by allowing customers to verify the timeliness of ECN information for compliance and decision-making.ECN APIs gain advanced filtering by true ECN numbers
What it is
: The ECN Search and Determination APIs
now support an optional parameter includeFullECNOnly (default = true) to filter results for fully qualified ECN numbers. When set to false, the API returns all matches as before. Additionally, the response includes a new attribute customsDeclarable, and the includeFullDescription parameter has been added to the ECN Search API for consistency.Benefit to you
: Provides greater control and precision when searching ECNs by allowing you to focus on fully qualified numbers and view customs declarable status directly in the response, improving compliance workflows and reducing unnecessary data review.DPS extracts are now case-insensitive
What it is:
We’ve improved our DPS extracts to ignore letter casing when pulling data. This means the system will focus on the actual content rather than capitalization differences. Benefit to you:
This change eliminates false updates caused by case variations and reduces unnecessary deltas, ensuring only accurate changes are triggered. You will receive cleaner, more reliable data making workflow smoother and more efficient.