Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
WTO Connector
Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
Overview
The WTO Connector provides seamless access to the World Trade Organization (WTO), enabling retrieval of international trade and tariff data, metadata, and reference information. It standardizes requests to the WTO Timeseries through a unified proxy service, making it easy to integrate with GCP services. This connector allows developers to query topics, indicators, territories and trade data.
Integration Overview
This document provides a detailed description of each integration endpoint, configuration, and workflow supported by the WTO Connector.
Supported Integration Action Points
Detailed Integration Documentation
2.1 Topics
| Action | getTopics |
| Endpoint | /topics |
| Method | GET |
| Purpose | Retrieves a list of available topics such as tariffs, trade in goods, or trade in services. |
| Parameters |
Required:
|
| Output |
[
{ "id": "TRADE_IN_GOODS", "name": "Trade in Goods" },
{ "id": "TARIFFS", "name": "Tariffs" }
]
|
| Configuration | Ensure the connector is configured with the WTO base URL via CONNECTOR_ENV_WTO_BASE_URL environment variable. |
2.2 Frequencies
| Action | getFrequencies |
| Endpoint | /frequencies |
| Method | GET |
| Purpose | Retrieves available data frequencies such as Annual, Quarterly, or Monthly. |
| Parameters |
Required:
|
| Output |
[
{ "code": "A", "name": "Annual" },
{ "code": "Q", "name": "Quarterly" }
]
|
2.3 Periods
| Action | getPeriods |
| Endpoint | /periods |
| Method | GET |
| Purpose | Retrieves all available reporting periods for trade data. |
| Parameters |
Required:
|
| Output |
[
{ "id": "2022", "label": "2022" },
{ "id": "2023", "label": "2023" }
]
|
2.4 Units
| Action | getUnits |
| Endpoint | /units |
| Method | GET |
| Purpose | Retrieves available units of measurement used in WTO data (e.g., USD, Index). |
| Parameters |
Required:
|
| Output |
[
{ "id": "USD", "label": "US Dollars" },
{ "id": "INDEX", "label": "Index (2010=100)" }
]
|
2.5 Indicator Categories
| Action | getIndicatorCategories |
| Endpoint | /indicator_categories |
| Method | GET |
| Purpose | Retrieves the main categories under which indicators are organized. |
| Parameters |
Required:
|
| Output |
[
{ "id": "TRADE", "label": "Trade" },
{ "id": "SERVICES", "label": "Services" }
]
|
2.6 Indicators
| Action | getIndicators |
| Endpoint | /indicators |
| Method | GET |
| Purpose | Retrieves indicators filtered by topic, frequency, or product classification. |
| Parameters |
Required:
|
| Output |
[
{
"id": "HS_A_001",
"label": "Imports of goods",
"topic": "TRADE_IN_GOODS"
}
]
|
2.7 Territory Regions
| Action | getTerritoryRegions |
| Endpoint | /territory/regions |
| Method | GET |
| Purpose | Retrieves WTO-recognized regional groupings. |
| Parameters |
Required:
|
| Output |
[
{ "id": "AFRICA", "label": "Africa" },
{ "id": "EUROPE", "label": "Europe" }
]
|
2.8 Territory Groups
| Action | getTerritoryGroups |
| Endpoint | /territory/groups |
| Method | GET |
| Purpose | Retrieves groups such as “Developed economies” or “LDCs”. |
| Parameters |
Required:
|
2.9 Reporters
| Action | getReporters |
| Endpoint | /reporters |
| Method | GET |
| Purpose | Retrieves countries or regions reporting trade data. |
| Parameters |
Required:
|
| Output |
[
{ "id": "586", "label": "Pakistan" },
{ "id": "840", "label": "United States" }
]
|
2.10 Partners
| Action | getPartners |
| Endpoint | /partners |
| Method | GET |
| Purpose | Retrieves partner countries or entities in trade datasets. |
| Parameters |
Required:
|
2.11 Product Classifications
| Action | getProductClassifications |
| Endpoint | /product_classifications |
| Method | GET |
| Purpose | Retrieves classification systems used for WTO data (e.g., HS, BEC, ISIC). |
2.12 Products
| Action | getProducts |
| Endpoint | /products |
| Method | GET |
| Purpose | Retrieves available products filtered by classification or name. |
| Parameters |
Required:
|
2.13 Years
| Action | getYears |
| Endpoint | /years |
| Method | GET |
| Purpose | Lists all available years for which data is provided. |
2.14 Value Flags
| Action | getValueFlags |
| Endpoint | /value_flags |
| Method | GET |
| Purpose | Returns value flags describing data reliability or status (e.g., estimated, provisional). |
2.15 Data (GET)
| Action | getData |
| Endpoint | /data |
| Method | GET |
| Purpose | Retrieves WTO data for specific indicators, reporters, and partners. |
| Parameters |
Required:
|
| Output |
{
"indicator": "HS_A_001",
"reporter": "840",
"partner": "586",
"value": 105000000,
"unit": "USD",
"year": 2023
}
|
2.16 Data (POST)
| Action | postData |
| Endpoint | /data |
| Method | POST |
| Purpose | Allows data queries via JSON payload. |
| Parameters |
Required:
|
| Output |
[
{ "indicator": "HS_A_001", "reporter": "840", "value": 105000000 },
{ "indicator": "HS_A_002", "reporter": "124", "value": 25000000 }
]
|
2.17 Metadata
| Action | getMetadata |
| Endpoint | /metadata |
| Method | GET |
| Purpose | Retrieves metadata describing indicators, datasets, or reporting structures. |
2.18 Data Count
| Action | getDataCount |
| Endpoint | /data_count |
| Method | GET |
| Purpose | Returns the total count of data records available for a given query. |
Workflow Creation with the Connector
Example Workflow: Trade Data Analysis and Metadata Synchronization
WTO API Workflows
| Topic and Indicator Retrieval |
|
| Fetch Trade Data |
|
| Metadata and Reference Lookup |
|
| Integrate with GCP |
|
Pricing
Support
For Technical support please contact us on
custom-connectors-support@isolutions.sa
iSolution logo - white - transparent 250 px
Register To Wired For Banking
Register To Palo Alto & iSolution Event
[forminator_form id=”14485″]
[forminator_form id=”14419″]
[forminator_form id=”14298″]
[forminator_form id=”13094″]