IdeaSoft

IdeaSoft stores connect with a product XML or by pushing through the Data API. The IdeaSoft Admin API needs an OAuth redirect flow, so a direct connector does not exist yet.

The steps and verification flags below are taken one-to-one from the preset the product shows in the setup wizard. A step or fact marked Not verified in the docs could not be confirmed in the platform’s public documentation; check it in your admin panel.

Summary

Product XML or push via the Data API.

Recommended path

XML-CSV link (data feed)

Available paths

XML-CSV link (data feed) · Push via API (Data API) · Manual upload

Researched

2026-09-26

What is verified

Each fact below was either confirmed in the platform's public documentation or not. Unverified facts are still usable, but check them in the preview before relying on them.

• ✓ Verified in the docs API
• ✓ Verified in the docs authentication
• ✓ Verified in the docs field names
• ✓ Verified in the docs order statuses
• ✓ Verified in the docs webhooks
• ! Not verified in the docs feed URL
• ! Not verified in the docs file format
• ! Not verified in the docs record path
• ! Not verified in the docs admin menu paths

XML-CSV link (data feed)recommended

1. Create your product XML in the IdeaSoft admin (e.g. Google Shopping or marketplace XML) and paste its URL in the wizard. ! Not verified in the docs
2. The XML menu path couldn't be verified in the docs: check the mapping in the preview.

Push via API (Data API)

1. The IdeaSoft Admin API only works with an OAuth redirect (Integrations → API → Add, a redirect URL is required); there is no token to paste.
2. Your integrator reads orders (GET /admin-api/orders: status, shippingTrackingCode, customerPhone) and sends them to the Zitena Data API.
3. Create the secret API key in the wizard (or Settings → API keys) and share it with your developer or integrator over a secure channel.
4. The IdeaSoft integration sends products to PUT /api/v1/catalog/products, orders to PUT /api/v1/orders and customers to PUT /api/v1/musteriler (examples on the Data API page).
5. If orders include status, carrier, tracking number and the customer phone, the assistant recognises callers by phone and answers shipping questions.

Manual upload

1. Export the product list as CSV or XML from your platform's admin panel.
2. Upload the file in the wizard; columns are mapped automatically and you can adjust them.
3. A manual upload is one-off: re-upload when prices or stock change, or switch to an XML link.

Feed template

Product feed (XML/JSON)

Format

auto ! Not verified in the docs

URL pattern

Not documented — copy the address from the admin panel.

Known field names

• item_ref ← id
• urun_adi ← name, fullName
• urun_kodu ← sku, barcode
• fiyat ← price1
• stok ← stockAmount
• url ← slug

Known field names are only applied when they actually exist in your file; an unmatched name does nothing. The mapping is always shown in the preview before anything is imported.

Order status mapping

Status values from the platform are mapped to standard short names, and then to your own status in the same group if you have one. Unknown values are left unmapped and flagged for you.

Platform value	Standard short name
waiting_for_approval	on-hold
approved	processing
being_prepared	processing
fulfilled	shipped
delivered	delivered
cancelled	cancelled
refunded	refunded
waiting_for_payment	pending
deleted	cancelled

Notes

An IdeaSoft connector needs an OAuth redirect flow, so it isn't available yet.

Platform documentation

• IdeaSoft Admin API: authentication