exhibitors.gitex.com APIexhibitors.gitex.com ↗
Search and retrieve GITEX Global 2025 exhibitor profiles, categories, and country filters via 4 structured API endpoints. Get stand numbers, brands, products, and social links.
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": "5",
"start": 0
}'Get a 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.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of results per page. |
| start | integer | Starting index for pagination. |
| 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 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"
},
"sample": {
"data": {
"count": 1,
"limit": 5,
"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 exhibitors.gitex.com API
The GITEX Global Exhibitors API provides 4 endpoints to query the full exhibitor directory for GITEX 2025, covering company profiles, hall and stand assignments, product and brand listings, and category taxonomy. The get_exhibitor_list endpoint accepts filters for keyword, country, category IDs, and name initial, returning paginated summaries. The get_exhibitor_detail endpoint returns a complete profile including social links, brands, and products for any single exhibitor by slug.
Browsing and Filtering Exhibitors
The get_exhibitor_list endpoint accepts limit and start for pagination alongside four optional filters: keyword for name or description search, country for a single country (values must match those returned by get_all_countries), categories for a comma-separated list of UAID identifiers (applied as a union/OR filter), and initial_key for a single A–Z letter. Each response returns a count, the applied limit and start, and an array of exhibitor summary objects that include name, slug, country, stand_number, hall, categories, and logo.
Full Exhibitor Profiles
Passing a slug to get_exhibitor_detail returns the complete company record. Beyond the summary fields, this endpoint exposes social_links (keys: website, facebook, twitter, linkedin, instagram, youtube), a products array, a brands array, and a categories array of label strings. Stand and hall assignments appear in stand_number and hall. Slugs are stable identifiers available from list results or directly from exhibitor page URLs on the GITEX site.
Reference Lookups: Categories and Countries
get_all_categories returns the full category and subcategory tree used in the directory, with each subcategory carrying a UAID identifier. These UAIDs feed directly into the categories filter parameter in get_exhibitor_list. get_all_countries returns name and value pairs for every country represented in the directory; the value field is what the country filter parameter expects. Calling these two endpoints first is the correct approach before constructing filtered list queries.
- Build a searchable exhibitor directory filtered by technology category and country for pre-event research.
- Aggregate stand numbers and hall assignments from
get_exhibitor_detailto generate a floor-plan overlay. - Collect exhibitor social media handles (
linkedin,twitter,website) for outreach or enrichment pipelines. - Map exhibitor brand and product arrays to identify vendors operating in a specific technology segment.
- Use
initial_keypagination alongsideget_exhibitor_listto mirror the full directory alphabetically. - Cross-reference UAID category IDs from
get_all_categorieswith exhibitor counts to analyze sector representation at GITEX 2025. - Filter exhibitors by country using
get_all_countriesvalues to identify national delegations or pavilions.
| 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 | 250 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 the exhibitor directory?+
How do I use category filters in get_exhibitor_list?+
get_all_categories first to retrieve the full category tree. Each subcategory includes a UAID identifier (e.g. UAID3863). Pass one or more of these as a comma-separated string to the categories parameter in get_exhibitor_list. The filter applies as a union, meaning exhibitors matching any of the specified UAIDs are returned.Does the API return contact details like email addresses or phone numbers for exhibitors?+
social_links (website, LinkedIn, Twitter, Facebook, Instagram, YouTube), brands, products, and location data. You can fork this API on Parse and revise it to add any contact fields the source exposes.Does the API cover historical GITEX editions or only the current year?+
How does pagination work in get_exhibitor_list?+
start and limit parameters. The response always includes count (number of records returned in that page), start (the offset used), and limit (the page size used). To walk through all results, increment start by limit on each request until count is less than limit.