Hepsiburada Merchant Data — Store ID, Alias & Product Count
Send a Hepsiburada merchant slug or store URL and this source returns the store as structured data: ID, name, alias, store URL and how many products it lists.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "hepsiburada_merchant",
"merchant": "efeturk",
"human": "# Hepsiburada merchant\n\n- **Merchant:** efeturk\n- **Proxy traffic:** 1.99 MB\n- **Name:** EFETÜRK\n- **Products:** 18\n- **URL:** https://www.hepsiburada.com/magaza/efeturk",
"machine": {
"merchant": {
"@type": "HepsiburadaMerchant",
"id": "fff01cd7-3d56-4491-b594-4afc5d7e80d6",
"name": "EFETÜRK",
"alias": "efeturk",
"url": "https://www.hepsiburada.com/magaza/efeturk",
"product_count": 18
},
"response_bytes": 2082311
},
"total_points": 5
}- You send
- A Hepsiburada merchant slug or store URL
- You get back
- Merchant ID, name, alias, store URL and product count
- Coverage
- Hepsiburada.com stores with a public store page.
- Price
- 5 pts — $5 per 1,000
- Charged only when the merchant resolves. A slug or store URL that doesn't resolve is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Checking the site by hand | Open the store page and read it | Free, and slow | Fine for one store, slow across many |
| Building a scraper | Write it, host it, and repair it when Hepsiburada changes store pages | Engineering time | A maintenance commitment for something that isn't your product |
| NeuralVerge | One request per merchant | $5 per 1,000, misses not billed | Returns the store summary only — pull the listings separately |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
merchant | object | The merchant record; the fields below sit inside it. |
id | string | Merchant ID (a UUID). |
name | string | Store name as shown. |
alias | string | Store slug, usable as input for merchant products. |
url | string | Direct link to the store page. |
product_count | number | Number of products the store lists. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
merchant accepts a store slug (like efeturk) or a store URL. For the store's listings, run Hepsiburada merchant products with the same slug.
curl -X POST https://api.neuralverge.ai/functions/v1/run-hepsiburada-merchants \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "merchant": "efeturk" }'What teams use it for
Where this field shows up in an actual workflow.
Confirm a store exists and see how large its catalog is.
Compare product counts across rival stores.
Add the store ID and canonical URL to seller names you already hold.
Verify the slug before running Hepsiburada merchant products.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Hepsiburada.com stores with a public store page.
Read at request time.
This source returns publicly visible information, stamped with the input it was read from and a session id you can trace.
- —The product count reflects the moment of the request.
- —The profile has no rating or contact details; it returns what the sample shows.
- —A slug that doesn't match a store won't resolve.
Questions, answered
A store slug such as efeturk or the store's URL on Hepsiburada.
Related sources
List a merchant's products.
Every seller offering one product, with the buybox winner.
Full details for one listing.
Amazon, eBay, Walmart, AliExpress, Alibaba, Hepsiburada, Trendyol and Yandex Market product, seller and review data.
Try hepsiburada merchant on your own data
One request format across every source in the catalog.