Get Boyner data with one API
The Boyner API returns product data from the Turkish fashion retailer Boyner as clean JSON.
2 active endpoints. Every call is 1 credit.
- POST/boyner/v1/search
- POST/boyner/v1/product/detail
What Boyner endpoints does ReefAPI ship?
2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Boyner API
2 of 2 endpoints, ready to run
Search Boyner by keyword (query), paginated (page, 24/page).
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Boyner API works
Boyner is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 185 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Boyner ids, the merchant_id that says who is selling, and the one place Turkish number formatting survives
Boyner is a department store and a marketplace on the same product page, so the field that matters most is merchant_id rather than the brand. The ids below were read off live responses on 2026-08-27, and the last two rows are the exception to an otherwise clean numeric payload: everything money-shaped is a JSON number except the coupon block, which Boyner passes through in Turkish notation.
| Field | Where it comes from | Measured shape |
|---|---|---|
| product_id | the digits after '-p-' in a boyner.com.tr URL | "15593795" - a string of 8 digits, not an integer |
| merchant_id | who actually ships the item | "1" is Boyner's own stock; marketplace sellers are 10 digits. On 'kahve makinesi' 12 of 24 rows were merchant_id 1 and the rest split across 2005134975, 2001260882, 2009607398, 2006499259 and 2002188899 |
| variant_id | sizes[].variant_id, one per size | "22711208" - the size-level key, a different id from product_id |
| category_id | search cards and detail | "2756" = Sneaker |
| barcode / gtin | sizes[].barcode, one EAN-13 per size | 5715825094299; product.gtin is the barcode of whichever size Boyner had selected |
| price, original_price | search and detail | JSON numbers, currency "TRY": 1899.0 down from 3449.0 |
| coupons[].MinBasketAmount | Boyner's coupon block, passed through raw | "7.500" - a string in Turkish notation where the dot is the thousands separator, so this is 7,500 TRY |
| other_merchants[].rating | the offer list on a detail page | "10.0" as a string, while the top-level merchant_rating for the same seller is the number 10.0001 |
seller is null on every search card measured (24 of 24 on two different queries) because Boyner stopped printing the seller name on listing tiles. merchant_id still identifies the seller there, and product/detail fills seller in as "BOYNER" or the marketplace shop name.
What people build with Boyner
The jobs this data is most often used for.
endpoints
credit per call
Pricing teams call search to track Boyner prices and discounts.
Catalog-enrichment tools use product/detail to fill listings with images and specs.
Market analysts use search to size a Turkish fashion segment.
What Boyner data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 185 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/boyner/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"erkek spor ayakkabı"}'import requests
r = requests.post(
"https://api.reefapi.com/boyner/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "erkek spor ayakkabı"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Boyner.
Get a free key →Why is the seller field null on every Boyner search result?▾
Boyner removed the seller name from its listing tiles, so search cards have nothing to parse and seller comes back null rather than guessed. merchant_id is still there and still identifies the seller, so filter on that. Calling product/detail on the same product_id fills in seller, merchant_rating and other_merchants with the competing offers.
Are Boyner prices Turkish-formatted strings or numbers?▾
Numbers. price, original_price and every price inside other_merchants come back as JSON floats with currency "TRY" - 1899.0, 3449.0, 3239.1 - so no locale parsing is needed. The one exception is the coupons block, which Boyner publishes in Turkish notation and which is passed through unchanged: MinBasketAmount "7.500" means 7,500 TRY, not seven and a half.
How do I tell Boyner's own stock from a marketplace seller?▾
merchant_id "1" is Boyner selling it themselves; anything else is a marketplace shop, and those ids are 10 digits long. On detail the same fact is available as is_boyner_product. Fashion queries skew heavily to Boyner's own stock (24 of 24 on 'erkek spor ayakkabi') while electronics do not (12 of 24 on 'kahve makinesi').
Why does discount_rate disagree with the campaign text?▾
discount_rate is computed from price against original_price and rounded, while campaign is Boyner's own marketing label. A measured row priced 1899.0 from 3449.0 is a 44.94% cut, so discount_rate reads 45 while campaign reads "%44 Indirim". campaign is often a lump-sum offer rather than a percentage at all, such as "500 TL Indirim" on a product whose derived discount_rate was 12.
What is inside sizes[] on a Boyner product?▾
One row per size, each with its own variant_id, its own EAN-13 barcode and a quantity. stock_variants_total is the sum of those quantities, verified on a live product where 0, 2, 1, 16, 15 and 8 added up to the reported 42. size_title tells you what the sizes mean, which is "Beden" for footwear and apparel.
What happens when a Boyner search matches nothing?▾
You get NOT_FOUND, not an empty 200. A nonsense query returned code NOT_FOUND with the message that the source's own result count is 0, and meta.total was 0. That distinction matters when you are monitoring a keyword: an empty list would look like a temporary parse failure, and this way it does not.
Does the Boyner detail endpoint return review text?▾
No. rating, review_count and favorite_count are all there - 4.8, 12 reviews and 2,854 favorites on a measured product - but sample_reviews is null, because Boyner loads review bodies client-side and does not put them in the page this endpoint reads. The field is returned as null rather than omitted so you can tell absent from empty.
How does Boyner paging work and how deep can I go?▾
24 products per page, 1-based, with meta.total carrying the source's own match count - 10,017 for 'erkek spor ayakkabi'. Page 2 of that query shared zero product_ids with page 1, so paging is real rather than a re-served first page. meta.total stays constant across pages, so you can size a crawl before you start it.
What is the Boyner API?▾
Boyner API is a ReefAPI endpoint group for boyner It returns live JSON through POST requests under /boyner/v1.
Is the Boyner API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Boyner calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Boyner login or account?▾
No login to Boyner is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Boyner data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Boyner API use?▾
Boyner actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Boyner from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call boyner actions with the same key, credit pool and JSON envelope used by normal REST requests.
15 More APIs APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Boyner, you are one call away from the rest of the category — no second contract, no second integration.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 184 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts.