n11

n11

This connector uses the n11 seller integration API on https://api.n11.com (documentation at developer.n11.com): products and their tasks on the current REST services, prices and stock, the category tree and attributes, orders as shipment packages with approval, package splitting and pickup requests, and, on n11's SOAP services (the only ones n11 offers for them), return requests, customer questions and invoice links.

Setup (about 5 minutes)

1. Sign in to the n11 seller panel (so.n11.com) and open Hesabım > API Hesapları (account > API accounts). Create an API account if there is none.
2. Copy the API anahtarı (key) into N11_APP_KEY and the API şifresi (secret) into N11_APP_SECRET.
3. Install and run n11_list_products.

How requests are signed: the REST services take the key and secret in the appkey and appsecret headers; the SOAP services (returns, questions, invoice link) take them inside the request, which the connector fills in. A wrong pair answers 401 (SellerApiUserUnauthorizedException) or 403 Authentication failed. Since 15 August 2025 the category services need the key as well.

Products: n11_list_products (filter by stock code, group code, sale or approval status, brand or category; productStatus InApproval means n11 waits for an action from you, CatalogRejected comes with rejectInfo). To create products take a leaf category from n11_list_categories (subCategories null), its attributes from n11_get_category_attributes (send every isMandatory attribute: valueId when isCustomValue is false, customValue otherwise; the same productMainId groups variants), then n11_create_products. Change data with n11_update_products (status Suspended takes a product off sale), prices and stock with n11_update_price_and_stock, and delete with n11_delete_products (switched off).

Every product write is a task. Create, update, price and stock and delete answer with a task id and status IN_QUEUE (or REJECT with reasons). Call n11_get_task_details with that id until the status is PROCESSED, then read each stock code's status (SUCCESS or FAIL) and reasons. A 200 on the write only means the task was queued.

Orders: n11_list_shipment_packages returns packages with their lines; each line has an orderLineId. The flow: status Created (new) > n11_approve_order_lines (to Picking) > ship with the n11 cargo campaign code in cargoTrackingNumber > Shipped > Delivered. Split a Picking package with n11_split_package (by line) or n11_split_package_by_quantity (by quantity, optionally cancelling quantities). Bulky goods: n11_create_collection_request. Labour costs for jewellery lines: n11_send_labor_costs. Invoice: n11_send_invoice_link (required with invoice number and date for e-export orders, where micro is true). Order data before November 2024 is not available.

Returns: n11_list_claim_returns (status REQUESTED by default, ALL for all; search by order number with searchInfoType ORDERID), n11_approve_claim_return, n11_postpone_claim_return with a reason from n11_list_return_pending_reasons, and n11_deny_claim_return (switched off) with a reason from n11_list_return_deny_reasons.

Customer questions: n11_list_product_questions (dates DD/MM/YYYY, open questions by default; once a minute), n11_get_product_question, and n11_answer_product_question after the user approved the text.

Writes: confirm first. Prices, stock, product status, order approval, splits and cancellations, returns and answers act on the live store. Before each call show the user what changes (stock codes with old and new price or stock, lines, the answer text) and wait for a yes.

Reading the data: order dates (startDate, endDate, lastModifiedDate, invoiceDateTime) are epoch milliseconds in Turkey time (UTC+3), e.g. 1793318400000; the SOAP services use dd/mm/yyyy. Prices are in TL unless currencyType says USD or EUR; send prices with a dot and two decimals. Ids can grow longer over time (orderNumber, n11ProductId), so treat them as strings when you store them. The invoice amount of a line is sellerInvoiceAmount = price x quantity minus seller discounts.

Paging: the REST lists start at page 0 and return totalPages; stop when content is empty. Products at most 250 per page, packages 100, returns 20 per page.

Limits: the order list allows 1,000 requests a minute, product writes 1,000 stock codes per call, questions one list call a minute.