Trendyol

Trendyol

This connector uses the Trendyol seller integration API on https://apigw.trendyol.com/integration (the old api.trendyol.com/sapigw host is no longer the documented one): products on the current Product v2 services, stock and prices, shipment packages (orders), returns, customer questions, the category, attribute and brand lookups, addresses and finance.

Setup (about 5 minutes)

1. Sign in to the Trendyol seller panel (partner.trendyol.com) with the master user (admin role); other users do not see the API data.
2. Open your store name (top right) > Hesap Bilgilerim > Entegrasyon Bilgileri. Copy the Satıcı ID into TRENDYOL_SELLER_ID, the API Key into TRENDYOL_API_KEY and the API Secret Key into TRENDYOL_API_SECRET.
3. Set TRENDYOL_API_HOST to https://apigw.trendyol.com.
4. Only if you sell on an international Trendyol storefront: set TRENDYOL_STOREFRONT_CODE to its two-letter country code; it is sent as the storeFrontCode header. Leave it empty for Trendyol Turkey.
5. Install and run trendyol_list_stock_and_prices.

How requests are signed: HTTP Basic with the API key as user name and the secret as password, plus the User-Agent header Trendyol requires, built as <seller id> - SelfIntegration from TRENDYOL_SELLER_ID. Requests without it are refused with 403. A 401 with ClientApiAuthenticationException or basic.authorization.failed means wrong credentials.

Stage (test) environment: https://stageapigw.trendyol.com uses separate stage credentials, and Trendyol only lets in IP addresses it has whitelisted; any other address gets 503. Use it from a self-hosted installation whose IP you registered with Trendyol, not for your live store.

Dates are epoch milliseconds (e.g. 1759276800000 = 2025-10-01 00:00 UTC), in Turkey time (UTC+3) for orders. Convert before calling and when reading orderDate, creationDate and similar fields.

Orders are shipment packages. trendyol_list_orders uses the v2 order endpoint, which Trendyol made mandatory on 15 October 2026: it reaches at most the last month, a date window of at most 2 weeks (without dates the last week) and the first 10,000 packages of a filter, so narrow the window or the status for more. The usual flow: status Created (to process) > trendyol_update_package_status with Picking > with Invoiced and the invoice number > Trendyol's carrier picks it up (Shipped, then Delivered). Sellers on the international storefronts who ship with their own carrier send the tracking number with trendyol_update_tracking_number after Picking. trendyol_send_invoice_link sends the e-invoice link to the customer.

Products use Trendyol's Product v2 services (the old product filter is being switched off): trendyol_list_products lists approved products grouped by content with their variants, trendyol_list_unapproved_products the ones pending or rejected (with the reasons), trendyol_list_stock_and_prices only stock and prices. To create a product, find a leaf category with trendyol_list_categories (pass name), its attributes with trendyol_get_category_attributes and their values with trendyol_list_attribute_values, the brand with trendyol_search_brands, the addresses with trendyol_list_addresses, then call trendyol_create_products.

Every product write is asynchronous. Create, update, stock and price, archive and delete return a batchRequestId; call trendyol_get_batch_request until status is COMPLETED and read each item's status and failureReasons. A 200 on the write only means the request was queued. Results stay available for 4 hours.

Writes: confirm first. Price and stock updates, content changes, package status, tracking, carrier change, invoice link, approving returns, answering questions, archiving and creating products act on the live store. Before each call, show the user what will change (barcodes with old and new price or stock, package and lines, the answer text) and wait for a yes. trendyol_delete_products, trendyol_report_unsupplied (cancels order lines) and trendyol_reject_claim_items are installed switched off.

Prices and stock: trendyol_update_price_and_inventory takes up to 1,000 barcodes, at most 20,000 units per product; salePrice may not exceed listPrice. Trendyol refuses the same request again within 15 minutes and more than 30 price updates a minute for one barcode.

More tools: trendyol_get_product (approval and archive state of one barcode), trendyol_get_buybox (buybox position and price, up to 10 barcodes), trendyol_update_product_content (title, description, images and attributes of approved products), trendyol_update_unapproved_products (fix products that are pending or rejected), trendyol_archive_products (archive or restore by barcode), trendyol_change_cargo_provider (carrier of a package), trendyol_list_brands and trendyol_list_cargo_providers (lookups).

Returns (claims): trendyol_list_claims lists returns with their items, trendyol_get_claim_item_audit shows one item's history, trendyol_approve_claim_items accepts returned items, and trendyol_reject_claim_items (switched off) opens an issue with a reason from trendyol_list_claim_issue_reasons.

Customer questions: trendyol_list_questions (status WAITING_FOR_ANSWER for open ones), trendyol_get_question, and trendyol_answer_question after the user approved the text.

Finance: trendyol_list_settlements (sales, returns, discounts, commissions) and trendyol_list_other_financials (payouts, transfers, invoices) need a transaction type and either a window of at most 15 days or a paymentDate / paymentOrderId.

Rate limits: at most 50 requests per 10 seconds on one endpoint (429 too.many.requests), plus per-minute limits per service group (product reads, product writes, stock and price writes) that depend on the store's listing tier. Do not loop over pages faster than needed.

Lookups need no seller data: categories, attributes, attribute values, brands, cargo providers and return rejection reasons are the same for every seller on a storefront; the attribute and category names come in Turkish on the TR storefront.