Connectivity mark

—INTEGRATION · Marketplace

Hepsiburada

Answers “Ask the Seller” questions; gives live order and shipping status from the order number.

Answers questions in your Hepsiburada seller panel and looks up order and shipping status with the three-part identity.

Ready For: Marketplace seller
Category
Marketplace
Direction
Read: orders, shipping and “Ask the Seller”. Write: order status is not changed.
Plan
Available on all plans. The paid channel limit applies when the marketplace channel is opened; web widget + Telegram are outside the limit.

Brand names and logos are connectivity indicators only; all trademarks belong to their owners.

01WHAT IT DOES

The scope that works today.

The three jobs below are today’s scope; read/write direction is stated separately.

01

Checks “Ask the Seller” questions every 3 minutes and answers from your knowledge base.

02

Looks up status and shipping by order number; the same answer is used on every channel.

03

Prefers answers that do not redirect off-platform or leak contact details; hands over when unsure.

DIRECTION

Read: orders, shipping and “Ask the Seller”. Write: order status is not changed.

02WHAT HAPPENS AFTER CONNECTING

One conversation, four stops.

The customer asks; YanıtLabs verifies; the connection reads or writes only the needed field; the answer returns on the same channel. The flow is fictional.

SAMPLE FLOW

03HOW TO CONNECT

Connect in three steps.

Each step is one screen in the panel. “Test connection” is read-only and runs before saving. Timing depends on the provider’s approval and your account readiness; we do not promise a fixed duration.

  1. 01
    Step 1

    Get the Merchant ID, service key and Developer Username from the Hepsiburada seller panel.

    Panel · 1 screen
  2. 02
    Step 2

    In Connections → + New connection → Hepsiburada, enter the three values; do not put the Merchant ID in Developer Username.

    Provider approval
  3. 03
    Step 3

    In Order sources → New source → Hepsiburada, save the same values and test the connection.

    Test record

04WHAT DATA IT READS / WRITES

Reads, does not write, does not store.

Data minimisation: only the field needed for the job is read or written. The limits below are today’s code scope.

Hepsiburada data scope
Reads Does not write Does not store
READS“Ask the Seller” questions, order status and shipping step. NO WRITEOrder-status change, return, shipping label or product-catalog write. NO STOREThe three-part identity is only for the connection; customer phone/email is not written to the model.

For KVKK processing, retention and deletion details, see the Security and KVKK page.

05VERIFICATION AND SECURITY

How is the customer verified?

Order information is not shown before verification; “not found” and “failed” get the same response.

  • The default check is the order number only. You can require the last 4 digits, the full phone number, or email on written channels; email is never asked on voice.

    01
  • Hepsiburada can also mask phone and email, so verification falls back to the order number; the three-part identity is only for the connection.

    02
  • If the WhatsApp sender or caller number matches the phone on the order, no extra information is requested; the channel number verifies it.

    03
  • There are 3 attempts per session in a 30-minute window. After the third attempt the conversation is handed to a human.

    04
  • “Not found” and “verification failed” use the same message, counter and delay; the existence of an order number does not leak.

    05
  • Order content is shown only after successful verification. Phone and email are not written to the model or logs.

    06
  • Credentials are stored encrypted and are never shown again in the panel.

    07

06LIMITS

We also state what it does not do.

These are today’s code limits; we do not claim “it does everything”. If one blocks your work, a connector request is evaluated separately.

  • The product catalog is not read; product questions are answered from your knowledge base.
  • There is no label, return or order-status change; access is read-only.
  • The test store has no order query; production is required for real order verification.

07FAQ

Three questions, clear answers.

Are Merchant ID and Developer Username the same?
No. Merchant ID is the store identity; Developer Username is the integrator username expected in the User-Agent header. Mixing them returns 401.
Can I test in the test store?
The test store is for listing only; order lookup does not work there. Use production for orders.
Is the order number enough?
Yes; when contact details are masked, only the order number is asked. “Not found” and “verification failed” get the same response.

+RELATED POSTS

Posts on this topic

Posts from the same topic cluster that complete this page. Hepsiburada integration posts.

Let’s set up your Hepsiburada connection together.

Try free for 14 days, no credit card. We will set it up together; the connection test starts read-only.

Call Start 14-day trial