Shop Apotheke

Shop Apotheke's marketplace runs on Mirakl, and this connector covers the seller surface. Agents pull new orders into an ERP or warehouse system and accept them, confirm shipments with tracking, handle returns and incidents, push stock and price imports, and read accounting documents.

118 actions API key available

Shop Apotheke website Vendor Seller Portal Capability data verified 2026-08-26

A scheduled poll runs List Orders filtered on update date since the last successful pass

Agent reads each new order's lines, quantities and requested shipping origin

Every line is matched against what the warehouse system says is actually on hand

Accept Or Refuse Order Lines answers the order in one call when every line can be filled

Update Order Tracking records the carrier and number, then Validate Order Shipment moves the order to Shipped

The agent posts the orders it could not fill in full, with the stock it found and the operator's own reason codes

The seller operations owner decides whether to refuse those lines, source them elsewhere, or accept and run late

What This Integration Enables

Selling on Shop Apotheke is not the same job as running your own store, and this connector is built for the difference. The marketplace runs on Mirakl, so the seller does not own the product record, the customer relationship or the notification emails. The seller owns offers against the operator's catalog, an acceptance decision on every order, a lead time to ship, a returns compliance judgment, and a scorecard the operator keeps. Every one of those is a clock, and clocks are what automation is for.

FlowRunner agents pull orders and accept them, create shipments and confirm tracking, and work the returns and incidents queue. They push price and stock through the file imports and follow each import to its error report, publish products and read back the identifiers the operator assigns, answer operator and customer messages, and pull billing cycles and transaction lines for reconciliation. The platform reference data, reason codes, carriers, shipping zones, logistic classes and currencies, is readable too, because a refund or a cancellation on Mirakl has to quote the operator's own codes rather than your words for them. The judgment calls that cost a sale or a rating go through human-in-the-loop. The rest runs on the clock.

Without FlowRunner

Orders read out of a back office New orders are noticed when somebody signs into the marketplace portal and looks at the queue

An acceptance clock nobody is watching The operator's acceptance window runs whether or not a person is at a desk, and a window that closes unanswered is a lost sale

Stock and price files sent and forgotten A file is uploaded by hand, and the import report is only opened when something already looks wrong

With FlowRunner

Orders pulled on the operator's cadence The agent polls on update date, which the platform pads so latency cannot let an order slip past, and reads to the end of the result set

Acceptance answered with evidence Every line carries a decision drawn from the system that counts stock, and the lines that cannot be filled reach a person instead of a guess

Imports followed to their outcome Every import returns a tracking identifier the agent follows to its report, and the rejected rows arrive as rows rather than as a failed job

Use Case Scenarios

Order intake that keeps pace with the operator

The agent polls List Orders on start update date, pages to the end using the offset the operation carries, and matches every line against the warehouse. Orders it can fill in full are answered immediately with Accept Or Refuse Order Lines. It then reads List Items To Ship, buys the label through Shippo, calls Create Shipments with the parcel contents, and confirms with Update Shipment Tracking and Validate Shipments As Shipped. Anything it cannot fill goes to a person with the numbers attached. The operator sees a shop that answers fast, and nobody had to sit in the portal to make that true.
Price and stock pushed from the system that counts, and the report actually read

On a schedule the agent builds the stock file from the warehouse system and the price file from the pricing rules, calls Import Offer Stock and Import Offer Prices, and keeps the import identifiers. It then polls Get Offer Stock Import and List Offer Price Imports until each one finishes, and pulls the rejected rows with Download Offer Import Error Report. Those rows land in Google Sheets beside the SKU that failed and the reason the platform gave. An import that half worked stops being invisible.
The returns and incidents desk, worked every morning

The agent runs List Returns and List Items To Return for anything waiting, and List Orders with the incident filter turned on for orders the customer has raised a problem against. Each one is posted to the support channel in Slack with the order, the reason code and the customer's message from List Order Messages. When a decision comes back, the agent executes it: Accept Or Refuse Returns, Create Return Labels for the ones being taken back, Receive Returns when the parcel lands, and Set Return Compliance line by line once the goods have been looked at. Resolve Order Incident closes the incident with the operator's reason code.

Human-in-Loop Highlight

Accept Or Refuse Order Lines is the operation this connector is really about, and refusing is the half that cannot be walked back. A refusal cancels that line's sale outright, it has to quote one of the operator's reason codes, and it lands on the metrics the operator judges the shop by. The call is also all or nothing: every line of the order has to carry a decision in the same request, so an agent cannot answer the easy lines now and think about the hard one later. What the agent has is a stock number from another system, which is a good reason to accept and a poor reason to refuse. So it accepts what it can prove and stops on the rest, posting: "Order 88-4102, three lines. Two accepted. Line 3, 6 units of SKU 41190, warehouse shows 2 on hand and 40 inbound Thursday. Refuse the line, part ship, or accept and ship late?" A person answers, and the agent sends the whole decision in one call. Speed on the lines that are obvious. A named human on the line that is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

118 actions

Orders

List Orders Lists the shop's orders with Mirakl's OR11 filters, including state, channel, creation date, update date, payment workflow and incident flag. This is the workhorse of an order flow.
Get Order Returns a single order with its lines, customer, addresses, prices and current state. Mirakl has deprecated its dedicated single order route (OR12) and tells sellers to call OR11 with the order_ids filter instead, which is exactly what this operation does, so it keeps working after the old route is removed.
Accept Or Refuse Order Lines Answers a new order by accepting or refusing its lines (Mirakl OR21). Every line of the order must carry a decision in the same call, or Mirakl answers ORDER_LINE_ACCEPTANCE_DECISION_MISSING, and partial acceptance has to be enabled for the shop at all.
Update Order Tracking Records the carrier and tracking number for an order (Mirakl OR23). Set this before Validate Order Shipment, which is the order Mirakl recommends, so the customer's shipping notification carries the tracking.
Validate Order Shipment Moves an order from Shipping to Shipped (Mirakl OR24), which is what notifies the customer and starts the payment workflow. The order must already be in the Shipping state, and Mirakl recommends calling Update Order Tracking first.
Cancel Order Cancels an order in full (Mirakl OR29). This is irreversible and it cancels every line of the order, so use Cancel Order Lines when only part of the order is affected.
Cancel Order Lines Cancels part of an order line by line (Mirakl OR30). The verb is PUT but the action is a cancellation and it cannot be undone.
Refund Order Lines Creates refunds on one or more order lines across one or more orders (Mirakl OR28), which is the current refund route now that the per order OR26 is deprecated.
Adjust Order Lines Corrects the actual measurement of order lines sold by weight or volume (Mirakl OR32), up to 100 lines per call. The order adjustment feature has to be enabled on the platform, the new measurement must differ from the ordered one, it must stay inside the operator's upward and downward limits, and a line can only be adjusted once and only before it is refunded.
Update Orders Updates orders field by field (Mirakl OR04), up to 100 per call, typically to set your own order reference or to record eco contributions on order lines.
Update Order Line Shipping Origin Records where order lines actually ship from (Mirakl OR07), either a warehouse code or a full address, up to 100 lines per call.
Update Order Custom Fields Sets the operator's custom fields on an order and its lines (Mirakl OR31). Only the fields you send are touched, and sending null or an empty string clears a value unless the field is required.
Resolve Order Incident Closes an incident on an order line with a resolution reason (Mirakl OR64). Find the affected orders with List Orders and the Has Incident filter turned on.
Get Order Evaluation Returns the rating and comment a customer left on an order (Mirakl OR51), together with the operator's moderation state where one applies.
List Order Taxes Returns the tax codes the operator has configured for orders (Mirakl OR75), which are the codes a refund or a cancellation has to quote in its taxes and shipping_taxes arrays.

Exports

Start Order Export Queues a full or incremental order export and returns a tracking id (Mirakl OR13). Mirakl recommends this over List Orders for large volumes because it handles them without paging.
Get Order Export Status Reports whether an order export is pending, completed, failed or canceled, and returns the download URLs once it is complete (Mirakl OR14).
Download Export File Fetches one file of a completed asynchronous export and stores it in FlowRunner file storage, returning a URL later steps can read.
Start Offer Export Queues a full or incremental export of the shop's offers and returns a tracking id (Mirakl OF52). This is the supported way to pull a whole catalog: the synchronous CSV route is deprecated and List Offers has to be paged.
Get Offer Export Status Reports whether an offer export is pending, completed or failed and returns the download URLs once it is complete (Mirakl OF53). Those URLs are the only way to fetch the files, because Mirakl publishes the retrieval step (OF54) as a placeholder path rather than a real route.
Start Transaction Line Export Queues an export of transaction lines and returns a tracking id (Mirakl TL03), which is the way to pull a whole accounting period without paging.
Get Transaction Line Export Status Reports whether a transaction line export has finished and returns the download URLs when it has (Mirakl TL04). Those URLs are the only way to fetch the files, because Mirakl publishes the retrieval step (TL05) as a placeholder path rather than a real route.

Order Documents

List Order Documents Returns every document attached to the given orders (Mirakl OR72), each with its identifier, type code and file name. Those identifiers are what Download Order Documents and Delete Order Document take, and what Post Order Message accepts as attachments.
Download Order Documents Downloads documents attached to orders and stores the result in FlowRunner file storage (Mirakl OR73). The shape of the download depends on what you ask for: a single document id comes back as that file, while several document ids or any order based request come back as a zip archive with one folder per order.
Upload Order Document Attaches a document such as an invoice or a delivery note to an order (Mirakl OR74). The response only lists documents that failed, so an empty errors list means the upload succeeded.
Delete Order Document Permanently removes one document from an order (Mirakl OR76). This cannot be undone, and Mirakl answers 204 with no body, so the confirmation returned here is assembled locally.

Shipments

List Shipments Lists the shop's shipments with their lines, tracking and states (Mirakl ST11). This resource uses seek pagination, not offset pagination, and neither kind appears in Mirakl's specification.
List Items To Ship Returns the order lines that still need a shipment (Mirakl ST12), which is the seller's outstanding work queue. This is the natural polling substitute for a shipping webhook, and Mirakl recommends calling it every 15 minutes.
Create Shipments Groups order lines into shipments (Mirakl ST01), up to 1000 at a time, optionally with tracking and the warehouse they leave from.
Update Shipment Tracking Records the carrier and tracking number on one or more shipments (Mirakl ST23), up to 1000 per call. Some shipping methods make tracking mandatory before a shipment can be validated, which List Shipping Methods reports as mandatory_tracking.
Validate Shipments As Shipped Moves shipments into the Shipped state (Mirakl ST24), which notifies the customer and advances the order's payment workflow, up to 1000 per call.
Validate Shipments As Ready For Pickup Marks click and collect shipments as ready for the customer to pick up (Mirakl ST26), up to 1000 per call. It applies to shipping methods flagged as click and collect, which List Shipping Methods reports.
Delete Shipments Deletes shipments that were created in error (Mirakl ST06), up to 1000 per call, which returns their order lines to the items still waiting to ship.
Update Shipment Origin Records which warehouse shipments leave from (Mirakl ST07), up to 100 per call. A 200 can still carry per shipment errors, so read the error list in the response.
Update Shipment Additional Information Fills in the operator's shipment specific fields such as a delivery bill number or an imei (Mirakl ST31), up to 100 shipments per call.

Returns

List Returns Lists customer returns with their lines, states, tracking and compliance results (Mirakl RT11). It uses seek pagination: read next_page_token from the body and send it back as Page Token, and note that Mirakl then ignores every other parameter.
List Items To Return Returns the order lines that are still eligible for a return, together with the return methods and reasons allowed on each (Mirakl RT12).
Create Returns Raises one or more customer returns against an order (Mirakl RT01), up to 200 per call. Call List Items To Return first, because it reports the return methods and reasons each line actually allows.
Accept Or Refuse Returns Answers return requests waiting for a decision (Mirakl RT21), up to 100 per call. Refusing needs a rejection reason and ends the return.
Receive Returns Records that returned goods have physically arrived (Mirakl RT25), up to 100 per call, which is the step before judging their compliance.
Close Returns Closes returns once they are settled (Mirakl RT27), up to 100 per call. A 200 can still carry per return errors, so read return_errors in the response.
Cancel Returns Cancels return requests (Mirakl RT29), up to 100 per call. The verb is PUT but this cancels, and a canceled return cannot be revived.
Set Return Compliance Judges returned goods line by line as compliant or not (Mirakl RT26), up to 100 returns per call, which is what decides whether the customer is refunded in full.
Update Returns Patches returns with tracking, a label URL, an RMA number, a return address or a different return method (Mirakl RT04), up to 100 per call.
Create Return Labels Asks Mirakl to generate carrier return labels for existing returns (Mirakl RT51). Give either a Carrier or a Label Selection Mode, and the package weight and dimensions are required.
List Return Labels Lists return label requests with their state, estimated cost, tracking and file URLs (Mirakl RT52). This is where the generated label PDF actually appears, under files.label.url, once the request reaches the created state.

Offers

List Offers Lists the shop's offers with their price, discount, stock, condition and channel prices (Mirakl OF21). It uses offset pagination, which Mirakl's specification does not publish, so Max and Offset are added here and the body carries total_count.
Get Offer Returns one offer in full, including its prices, discounts, volume prices, stock, condition, logistic class and custom fields (Mirakl OF22). It takes Mirakl's numeric offer identifier, not your own SKU.
Get Offer Quantity Returns the quantity currently available on one offer (Mirakl OF26). A zero is ambiguous by design: Mirakl documents that it answers 0 both when the stock is genuinely zero and when the offer is not available at all, so a flow cannot tell the two apart from this operation alone.
Create Update Or Delete Offers Writes offers through Mirakl's OF24 route, which is the main way to push price and stock without a file. The same route deletes: the action lives in the payload's update_delete field, surfaced here as the Mode parameter, so read it before running the operation.
List Product Offers Returns the offers that exist on given products (Mirakl P11), which includes competing sellers where the operator exposes them. This is the competitive pricing view: it is how a repricing flow sees what other shops charge on the same product.
Download Offers CSV Fetches the shop's offers as a CSV in one call and stores it in FlowRunner file storage (Mirakl OF51). Mirakl has deprecated this route and points sellers at Start Offer Export instead, so treat it as a convenience for small catalogs rather than the path to build on.

Offer Imports

Import Offers Uploads a CSV, XML or XLSX offer file and returns an import identifier to track it (Mirakl OF01). Import mode replace deletes every offer the file does not mention, because it treats the file as the complete inventory.
List Offer Imports Lists recent offer imports with their status and their counts of lines read, succeeded and failed (Mirakl OF04), whatever started them, including ftp drops and the back office.
Get Offer Import Reports how far an offer import got and how many lines succeeded, failed or are still pending (Mirakl OF02). Complete does not mean every line worked: read lines_in_error and has_error_report, and fetch the report with Download Offer Import Error Report when there is one.
Download Offer Import Error Report Fetches the rows an offer import rejected and stores the report in FlowRunner file storage (Mirakl OF03). The report comes back in the same format as the file that was imported, CSV, XLSX or XML, and it exists only when Get Offer Import reports has_error_report as true.
Import Offer Prices Uploads a semicolon separated price file and returns an import identifier (Mirakl PRI01). Its columns are offer-sku, price, discount-price, discount-start-date and discount-end-date, with optional range columns.
List Offer Price Imports Lists price imports with their status and their counts of lines and offers in error (Mirakl PRI02). This is also how you poll a single price import, by passing its identifier in Import IDs.
Download Offer Price Import Error Report Fetches the CSV of price rows that failed and stores it in FlowRunner file storage (Mirakl PRI03). Its first column is the line number and its second the reason.
Import Offer Stock Uploads a semicolon separated stock file and returns an import identifier (Mirakl STO01). Its columns are offer-sku, quantity, warehouse-code and update-delete, so it can set stock globally or per warehouse.
Get Offer Stock Import Reports how a stock import went, with its counts of lines succeeded and failed (Mirakl STO02). Read lines_in_error and has_error_report rather than the status alone, because a complete import can still have rejected rows.
Download Offer Stock Import Error Report Fetches the CSV of stock rows that failed and stores it in FlowRunner file storage (Mirakl STO03). It exists only when Get Offer Stock Import reports has_error_report as true, and rows absent from it were imported successfully.

Products

Get Products Resolves operator product references such as EAN or UPC into the catalog products behind them (Mirakl P31), which is how you find the product SKU an offer has to be attached to.
Import Products Submits new or updated products to the operator's catalog and returns an import identifier (Mirakl P41). Products are proposals: the operator's catalog rules decide what is integrated, which is why the import produces several separate reports, one for rejected products, one for products actually added, and two more when the Catalog Transformer is in play.
List Product Imports Lists product imports with their status and integration counters (Mirakl P51). It uses offset pagination, which the specification does not publish, so Max and Offset are added here.
Get Product Import Reports how a product import went and how many products were integrated or rejected (Mirakl P42). Products that fail the operator's catalog rules are reported here rather than raising an error at import time, so read the counters and then fetch the matching report.
Download Product Import Error Report Fetches the products an import could not integrate and stores the report in FlowRunner file storage (Mirakl P44), which Mirakl calls the non integrated products report.
Download Product Import Added Products Report Fetches the products the operator actually accepted into the catalog and stores the report in FlowRunner file storage (Mirakl P45). This report carries the product SKUs the operator assigned, which are what your offers have to reference, so it is the file to read after importing new products.
Download Product Import Transformed File Fetches the CSV Mirakl's Catalog Transformer produced from your source file and stores it in FlowRunner file storage (Mirakl P46). It shows exactly what the operator's catalog received after transformation, which is what to inspect when an import behaved unexpectedly.
Download Product Import Transformation Error Report Fetches the rows Mirakl's Catalog Transformer could not read from your source file and stores the report in FlowRunner file storage (Mirakl P47).
Get Product Attributes Returns the attributes the operator expects on products, with their type, whether they are required, and the value list each one draws from (Mirakl PM11).
List Value Lists Returns the value lists the operator defines and the values inside them (Mirakl VL11), which are the only accepted values for attributes of type list.
List Catalog Categories Returns the operator's catalog category tree, parents and children, with the code each product has to be filed under (Mirakl H11). Some operators only allow products on leaf categories, which Get Platform Configuration reports as product_import_only_on_leaf.

Messaging

List Threads Lists the shop's message threads with customers and with the operator (Mirakl M11), optionally with the messages themselves. Poll it on Updated Since to react to new customer messages, which is the substitute for a messaging webhook.
Get Thread Returns one thread with its participants, topic and messages (Mirakl M10), including the identifiers of any attachments, which Download Thread Attachment then fetches.
Reply To Thread Posts a reply into an existing thread, optionally with one attachment (Mirakl M12). A thread holds at most 1000 messages, and Mirakl caps attachments at 50 across all threads of one order and 1000 across all threads of one entity.
Create Operator Thread Opens a new conversation with the marketplace operator and sends its first message (Mirakl M14). Use it to raise an operational question with Shop Apotheke itself, as opposed to Create Order Thread, which writes to the customer about a specific order.
Create Order Thread Starts a conversation about a specific order, with the customer or with the operator (Mirakl OR43), and sends its first message. Each message including its attachments is capped at 30 megabytes.
Download Thread Attachment Fetches a file a customer or the operator attached to a message and stores it in FlowRunner file storage (Mirakl M13). Mirakl routes this under the threads path even though the identifier is the ATTACHMENT's, not the thread's, which is easy to misread from the URL alone.
List Messages Lists individual messages linked to orders and offers (Mirakl M01). Mirakl has deprecated this route and points sellers at List Threads and Get Thread, which return the same conversations grouped into threads.
List Order Messages Lists the messages exchanged about a single order (Mirakl OR41). Mirakl has deprecated this route in favor of List Threads filtered on the order, and it is kept here for existing integrations.
Post Order Message Posts a message about an order to the customer, the operator or the shop (Mirakl OR42). Mirakl has deprecated this route in favor of Create Order Thread and Reply To Thread, and it is kept here for existing integrations.

Invoicing

List Accounting Documents Lists the shop's invoices and credit notes with their amounts, payment status and billing cycle (Mirakl IV01). Mirakl states a maximum usage of once per day plus one call per page returned, so this is a daily reconciliation job rather than something to poll.
Download Accounting Document Fetches one invoice or credit note as a file and stores it in FlowRunner file storage (Mirakl IV02). Mirakl returns it as a binary stream with no declared file type, so the extension in the stored name is a guess unless you set File Name yourself.
List Seller Billing Cycles Lists the billing cycles that group the shop's transactions into a payout (Mirakl SBC11), with their amounts and payout state. The cycle identifier is what links an invoice to the transaction lines behind it, so it is the join key for reconciliation.
List Transaction Lines Lists the individual accounting movements behind the shop's payouts (Mirakl TL02), one line per order amount, commission, tax, refund or fee. This is the ledger a finance flow reconciles against: filter it by billing cycle to explain a payout, or by order to explain one sale.
List Document Requests Lists the accounting documents the marketplace expects the shop to issue, and the ones it has issued to the shop (Mirakl DR11).
List Document Request Lines Returns the individual amounts a requested accounting document has to cover (Mirakl DR12), which is what an invoice generated for that request must add up to.
Download Requested Documents Downloads the accounting documents attached to document requests and stores them in FlowRunner file storage (Mirakl DR73). Mirakl requires at least Document IDs or Entity IDs, and Entity IDs needs Entity Types alongside it.
Upload Requested Document Answers an accounting document request by uploading the invoice or credit note the marketplace asked for (Mirakl DR74). When the operator requires several formats for one request, Mirakl expects all of them in the same call, which the Properties hatch allows by supplying a complete files array.
Confirm Document Issuance Tells the marketplace that a fee document was issued outside Mirakl, without uploading a file (Mirakl DR75), up to 100 requests per call.

Shop

Get Shop Returns the shop's profile: contact address, channels, currencies, payment details, professional details, shipping country, return policy, closing dates and applicable taxes (Mirakl A01).
Update Shop Updates the shop's profile, its contact address, description, return policy, channels, shipping country and closing dates (Mirakl A02). Mirakl documents a maximum usage of once per day on this route.
Get Shop Statistics Returns the shop's marketplace performance, its evaluation average, acceptance rate, approval delay and order counts, per period and optionally per channel (Mirakl A21).
List Shop Documents Lists the business documents held against the shop, such as identity papers and legal filings used during onboarding and know your customer checks (Mirakl S30).
Download Shop Documents Downloads business documents held against the shop and stores the result in FlowRunner file storage (Mirakl S31). Mirakl requires either Document IDs or Shop IDs, and the shop parameter is missing from its published specification.
Upload Shop Document Uploads a business document such as an identity paper or a trade register extract, which is what a marketplace know your customer process asks for (Mirakl S32).
Delete Shop Document Permanently removes one business document from the shop (Mirakl S33). This cannot be undone, and removing a document the operator requires can put the shop's onboarding checks back into an incomplete state.

Promotions

List Promotions Lists the shop's promotions with their trigger, reward, period, channels and approval state (Mirakl PR01). It uses offset pagination, which the specification does not publish.
Create Promotion Creates a shop promotion, a percentage or amount off, free items or a reduced unit price, triggered by a quantity or a cart amount (Mirakl PR03).
Update Promotion Updates an existing promotion (Mirakl PR04). This is a full replace, not a PATCH: Mirakl requires the description, the start date, the reward and the trigger on every call, so read the promotion first and send it back with your change applied.
List Picklists Lists the warehouse picklists the marketplace generates for pick runs, with the order lines to prepare and their pick up dates (Mirakl PL11).

Platform

Get Platform Version Returns the Mirakl version the marketplace runs. This is the connection test: it is the one route that sits above Mirakl's authentication filter, so it proves the host is reachable and really is a Mirakl marketplace even before a key is valid.
Get Platform Configuration Returns which Mirakl modules and features the marketplace has switched on, including the order acceptance workflow, the tax mode, price approval, multi currency, lead time to ship, minimum and maximum order quantities and the circular economy data collection (Mirakl PC01).
List Custom Fields Returns the custom fields the operator has defined on offers, shops, orders and order lines, with their type, whether they are required, and the accepted values of list fields (Mirakl AF01).
List Channels Returns the sales channels enabled on the marketplace, with their code and label (Mirakl CH11). Channel codes are what the order, offer and promotion filters take, and an offer can carry a separate price per channel.
List Currencies Returns the currencies activated on the marketplace and which one is the platform default (Mirakl CUR01). A refund or a cancellation only needs a currency when the shop does not use the platform default, which is what this operation tells you.
List Locales Returns the locales the marketplace supports and which one is the default (Mirakl L01). These are the codes the Locale parameter takes on every localized operation, and the ones a multilingual product file has to be built for.
List Document Types Returns the document types the operator accepts on orders and on shops, with the mime types allowed for each (Mirakl DO01). These codes are what Upload Order Document and Upload Shop Document take.
List Offer Conditions Returns the offer conditions the operator defines, such as new, refurbished or used, with the code each one carries (Mirakl OF61). These codes are the state_code an offer has to be written with.
List Reasons Returns the reason codes the operator has configured for refunds, cancellations, incidents and messaging, each with its type and whether the shop is allowed to use it (Mirakl RE01).
List Shipping Zones Returns the shipping zones the operator defines, which are the geographies a shipping charge is configured against (Mirakl SH11). Their codes are what the offer export and the product offer lookup take as shipping zone filters.
List Shipping Methods Returns the shipping methods the operator offers, with the flags that change how a shipment behaves: whether tracking is mandatory before it can be validated, whether it is a click and collect method, and whether the operator delivers on the seller's behalf (Mirakl SH12).
List Carriers Returns the carriers registered on the marketplace, with their code and the tracking URL template Mirakl builds links from (Mirakl SH21). Using a registered carrier's code on a tracking update means Mirakl builds the customer's tracking link itself, which is why it is preferable to sending a free text carrier name.
List Logistic Classes Returns the logistic classes the operator defines, which group offers by size or handling and decide which shipping charge applies (Mirakl SH31).
Get Shipping Configuration Returns the shop's delivery times per shipping method and zone, its lead time to ship against the platform default, its order cut off times and whether the operator collects shipping charges on the shop's behalf (Mirakl SH42).
Get Shipping Charges Returns what the shop charges for shipping per logistic class, shipping method and zone, whether that is a fixed price, free shipping or a price by order value range (Mirakl SH52), and which of them the shop has customized.
List Shop Roles Returns the roles a shop user can hold and what each one grants (Mirakl RO02). Read it when a call answers 403: the API key belongs to a portal user, and its roles are what decide which operations that key can run at all.

Frequently Asked Questions

What can FlowRunner do with Shop Apotheke?

FlowRunner agents can run List Orders, Get Order, and Accept Or Refuse Order Lines in Shop Apotheke, plus 115 more actions.

Does connecting Shop Apotheke to FlowRunner require OAuth?

No. Shop Apotheke connects to FlowRunner with an API key, no OAuth flow required.

Can Shop Apotheke trigger a FlowRunner workflow automatically?

Shop Apotheke doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Shop Apotheke

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us