Çiçeksepeti integration | Zervanor
← All connectors

Çiçeksepeti

Also an agent tool
ecommerce

Çiçeksepeti — Turkey's flowers, gifts and general-merchandise marketplace. Seller / Marketplace API over an x-api-key header (plus a mandatory user-agent seller identifier): products & catalog, stock/price sync, orders, shipping, returns/cancellations and customer questions (Q&A). Production + sandbox environments share one credential model. Çiçeksepeti has no webhook API; new-order / new-return / new-question triggers are polling on list actions.

21 actions · 6 triggers

The Çiçeksepeti integration lets you connect Çiçeksepeti to your automations with 21 actions and 6 triggers — and every action is also a tool an AI agent can call. Examples: List Products, Upload Products, Update Products, Update Price And Stock, Get Batch Status. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 6

Events in Çiçeksepeti that can start a workflow.

webhook

Order Created / Updated

Fires when an order is created or changes status (polling get_orders). Filter statusId=1 for new-order semantics.

webhook

Return / Exchange Request Created

Fires when a customer opens a return or exchange (polling get_canceled_orders).

webhook

Customer Question Created

Fires when a customer asks a question on a product (polling list_questions). Filter Answered=false.

polling

New / updated Çiçeksepeti order

Fires when an order is created or changes. Filter statusId=1 for new orders.

polling

New Çiçeksepeti return/exchange request

Fires when a customer opens a return or exchange.

polling

New Çiçeksepeti customer question

Fires when a customer asks a question on your product. Filter Answered=false.

Actions 21

What Zervanor can do in Çiçeksepeti.

Order10

POST

Get Orders

Return marketplace-model orders (JSON body filter, paginated). The flagship new-order feed and polling source.

PUT

Ready For Cargo (CS Integration)

For sellers using Çiçeksepeti's contracted carriers: send sub-order id(s) and receive a partialNumber (cargo code). Orders must be in New status.

PUT

Update Order Status (Own Cargo)

For sellers using their own carrier: advance order status and supply tracking info. Carrier/tracking fields required only when setting status to shipped.

PUT

Change Cargo Company

Change the carrier on an order (among carriers defined for the firm). Only New status orders.

POST

Send Cargo Measurement (Desi)

Supply desi (volumetric weight) and piece count for high-volume orders before advancing them. Only for logistics-assigned, New status orders.

PUT

Digital Order Status Update

For products configured as digital delivery, advance order status.

PUT

Update Labor Cost

Send a labor-cost amount (VAT included) for a sub-order before it is delivered. Only valid for specific jewelry/precious-metal categories; amount > 0 and < item price.

POST

Get Canceled / Return Orders

List orders with a return or exchange request (paginated). The new-return trigger surface and polling source.

POST

Mark Return Received

Confirm a returned item has reached the supplier (when the return's cargo isn't tracked via integration). Only for Return-process-started status; sets status to Return at supplier.

POST

Approve / Reject Return

Approve or reject a return/exchange. Only for Return-at-supplier status. Approving an exchange re-opens the order as New; approving a refund passivates it and refunds the customer; rejecting escalates to Çiçeksepeti.

Products5

GET

List Products

List the seller's products on Çiçeksepeti, paginated and filterable.

POST

Upload Products

Create new products/variants. Asynchronous — returns a batchId; poll get_batch_status for per-item result. Max 1000 items per call.

PUT

Update Products

Update existing product info (name, description, images, delivery, active/passive, attributes). Asynchronous — returns a batchId. Max 200 items per call.

PUT

Update Price And Stock

Update stock quantity and/or prices by supplier variant code (stockCode). Asynchronous — returns a batchId. Max 200 items per call.

GET

Get Batch Status

Return the per-item result of an upload/update/price-stock batch. A 200 on submit does not mean every item succeeded — check items[].status.

Sellerquestions3

GET

List Questions

List customer questions on the seller's products, with filtering. The new-question trigger surface and polling source.

PUT

Answer Question

Post an answer (or a moderation action) to a customer question. Field requirements depend on branchActionId.

GET

Get Question Actions

Return the valid branchActionId / branchActionDetailId values and their labels (Publish Q&A, Send answer to customer only, Inappropriate content, Belongs to another seller).

Categories2

GET

List Categories

Return the full Çiçeksepeti category tree (nested subCategories[]). Safe, auth-only read — used as the connector health check.

GET

Get Category Attributes

Return the product/variant/personalizable attributes valid for a leaf category.

Branch1

POST

Send Invoice (Email)

Queue an invoice (base64 PDF or a PDF URL) for emailing to the customer of a sub-order. Rooted at /Branch on the host, NOT under /api/v1 — uses a per-action base_url override to the host root.

Automations using Çiçeksepeti

Build your own automation with Çiçeksepeti in the visual builder.

Frequently asked questions

What can I automate with Çiçeksepeti?

21 actions are available — for example: List Products, Upload Products, Update Products, Update Price And Stock, Get Batch Status, and more.

Which Çiçeksepeti events can start a workflow?

6 triggers — for example: Order Created / Updated, Return / Exchange Request Created, Customer Question Created, New / updated Çiçeksepeti order.

Can Çiçeksepeti be used as an AI agent tool?

Yes. Every Çiçeksepeti action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Çiçeksepeti integration modelled?

Çiçeksepeti is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.