GITEX APIexhibitors.gitex.com ↗
Search and retrieve full profiles for GITEX Global 2025 exhibitors. Filter by country, category, and keyword across 4 endpoints covering stands, brands, and products.
What is the GITEX API?
The GITEX Global 2025 Exhibitors API exposes 4 endpoints for querying the official exhibitor directory at exhibitors.gitex.com. get_exhibitor_list returns paginated summaries — including stand number, hall, country, categories, and logo URL — across thousands of participating companies. get_exhibitor_detail goes deeper, adding brand names, product listings, and social links for any single exhibitor by slug.
curl -X POST 'https://api.parse.bot/scraper/b7d4c731-954c-443a-babe-2a691d7f4de2/get_exhibitor_list' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"limit": "10",
"start": "0",
"keyword": "AI"
}'Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace exhibitors-gitex-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: GITEX Global 2025 Exhibitor API — search, browse, drill-down."""
from parse_apis.gitex_global_2025_exhibitor_api import Gitex, ExhibitorNotFound
client = Gitex()
# Search for AI exhibitors and print summaries
for summary in client.exhibitorsummaries.search(keyword="AI", limit=5):
print(summary.name, summary.country, summary.stand_number)
# Drill into the first result's full profile
item = client.exhibitorsummaries.search(keyword="robotics", limit=1).first()
if item:
exhibitor = item.details()
print(exhibitor.name, exhibitor.company_profile[:100])
for product in exhibitor.products:
print(product.name)
# Fetch a known exhibitor by slug
try:
detail = client.exhibitors.get(slug="lumen")
print(detail.name, detail.hall, detail.country)
except ExhibitorNotFound as exc:
print(f"Not found: {exc.slug}")
# Browse available categories and their subcategories
for cat in client.categories.list(limit=3):
print(cat.name, len(cat.subcategories))
# List countries available for filtering
for country in client.countries.list(limit=5):
print(country.name, country.value)
print("exercised: exhibitorsummaries.search / details / exhibitors.get / categories.list / countries.list")
Paginated list of exhibitors with optional filters for keyword, country, categories, and initial letter. Returns exhibitor summaries including name, slug, country, stand number, hall, categories, and logo. Pagination is offset-based via start/limit.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of results per page. |
| start | integer | Starting index for pagination (0-based offset). |
| country | string | Country name to filter by (must match a value from get_all_countries). |
| keyword | string | Search keyword to filter exhibitors by name or description. |
| categories | string | Comma-separated list of category IDs (UAIDs) to filter by, e.g. 'UAID3863,UAID3882'. Union filter (OR). |
| initial_key | string | Single uppercase letter A-Z to filter exhibitors by name initial. |
{
"type": "object",
"fields": {
"count": "integer, number of exhibitors returned in this response",
"limit": "integer, the limit that was applied",
"start": "integer, the starting index used",
"exhibitors": "array of exhibitor summary objects with name, slug, country, stand_number, hall, short_description, categories, logo_url"
},
"sample": {
"data": {
"count": 1,
"limit": 10,
"start": 0,
"exhibitors": [
{
"hall": "Hall 14",
"name": ".lumen",
"slug": "lumen",
"country": "Romania",
"logo_url": "https://exhibitor-manual-004.s3.ap-south-1.amazonaws.com/Production/exb_doc/2028/43341/thumb_2028_43341_42564_3541.png",
"categories": [
"Mobile Accessories & Peripherals",
"Smart Cities"
],
"stand_number": "H14-C10",
"short_description": ".lumen builds Pedestrian Autonomous Driving AI..."
}
]
},
"status": "success"
}
}About the GITEX API
Browsing and Searching Exhibitors
get_exhibitor_list is the main discovery endpoint. It accepts a keyword string for name or description search, a country value (sourced from get_all_countries), a comma-separated categories string of UAID identifiers (sourced from get_all_categories), and an initial_key for A–Z browsing. Pagination is offset-based via start and limit. Each result in the exhibitors array includes name, slug, country, stand_number, hall, short_description, categories, and logo_url.
Exhibitor Detail Profiles
get_exhibitor_detail takes a slug from list results and returns the full company record. Response fields include brands (array of brand name objects), products (array of product name objects), social_links (an object with optional keys for website, facebook, twitter, linkedin, instagram, and youtube), hall, stand_number, and categories. This is the endpoint to use when you need to build a contact sheet or technology stack summary for a specific exhibitor.
Reference / Filter Endpoints
get_all_categories returns the full category tree: top-level categories each contain a subcategories array where every entry has a human-readable name and a UAID id string. These UAID values feed directly into the categories filter on get_exhibitor_list. get_all_countries returns a flat list of name/value pairs representing every country present in the directory; the value string is what the country filter on get_exhibitor_list expects.
The GITEX API is a managed, monitored endpoint for exhibitors.gitex.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when exhibitors.gitex.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official exhibitors.gitex.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a searchable internal directory of GITEX 2025 exhibitors filtered by technology category and country.
- Generate a lead list of exhibitors from a target country using the
countryfilter inget_exhibitor_list. - Pull social media handles and website URLs via
get_exhibitor_detailfor outreach or research. - Map exhibitor stand numbers and halls to a floor-plan tool for event navigation.
- Enumerate all product and brand names per exhibitor for competitive intelligence gathering.
- Feed category-filtered exhibitor data into a CRM enrichment pipeline using UAID identifiers.
- Build an A–Z exhibitor index using the
initial_keyparameter onget_exhibitor_list.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does GITEX Global provide an official developer API for its exhibitor directory?+
How do category filters work in get_exhibitor_list?+
categories parameter accepts a comma-separated string of UAID identifiers — for example, UAID3863,UAID3882. These IDs come from the subcategories array returned by get_all_categories. The filter is a union (OR), so an exhibitor matching any of the supplied UAIDs will be included in results.Does the API return exhibitor contact details such as email addresses or phone numbers?+
get_exhibitor_detail exposes social_links (website, LinkedIn, Facebook, Twitter, Instagram, YouTube) and stand_number but not direct contact information. You can fork this API on Parse and revise it to add an endpoint targeting any contact data the directory exposes.What are the pagination limits on get_exhibitor_list?+
get_exhibitor_list uses offset-based pagination controlled by start (0-based index) and limit (results per page). The response echoes back count, start, and limit so you can calculate subsequent pages. There is no cursor token; you increment start by limit to walk through the full result set.