Developer docs & sandbox

Build on Vortex IQ. The docs are live and the sandbox is one request away.

For platform & tech partners, agencies and systems integrators, and developers integrating with the AI Operating System for e-commerce. The full API and connector reference is live at docs.vortexiq.ai. Build against a clear, proven model — read-first connectors, approval-gated writes, staging-first changes, one-click rollback and a full audit trail — then request a sandbox with sample data so you can prove your integration before it touches a live store.

BigCommerce Shopify Adobe Commerce WooCommerce 93 live integrations
The documentation is live

Start at docs.vortexiq.ai. It is live, and it is the source of truth.

The full API and connector reference is published and maintained at docs.vortexiq.ai. It is the canonical place to understand the core API and the connectors — how authentication works, what each connector reads, and how approval-gated writes behave. We keep the API surface documented there rather than restating it on a marketing page, so what you build against is always current.

Core API reference: authentication, the request model, and how read-first and approval-gated writes work end to end.
Documentation for every connector: what each connector reads, what it can propose, and how it fits the read-first model.
Maintained, not a snapshot: the docs are the live reference, so you build against the current surface rather than a stale PDF.

Read the docs

The documentation site covers the core API and the connectors in detail. It is the right first stop for any developer scoping an integration, and the reference your technical evaluators should read.

How you build with Vortex IQ

A proven model you can reason about, not a black box you have to trust.

Whatever you are integrating, the contract is the same. Connectors read first to understand context, the engine proposes a scoped change, that change is staged before it ever reaches production, a human approves it, and anything that goes live can be rolled back in one click with a full audit trail behind it. The safety guarantees are part of the model, not an add-on.

01 · Read-first

Connectors read before they write

Every connector is read-first by default: it pulls real context from the system so detection and proposals are grounded in actual data, not assumptions. You can integrate read-only and add write scope later.

02 · Approval-gated

Writes are proposed, not forced

The engine proposes a scoped change and explains it. Nothing reaches production without a human approving it, and you decide what may run autonomously and what always needs sign-off.

03 · Staging-first

Changes land in staging

Approved changes are applied staging-first and reviewed before go-live, so a write is observed in a safe context before it affects a live store.

Reversible, with a full audit trail

Anything that goes live can be rolled back in one click, and every signal, proposal, approval and rollback is recorded. That is what makes the model safe to build on at scale: every change has a record and a reverse path. The exact endpoints and payloads for this flow are documented at docs.vortexiq.ai.

Sandbox

Request a sandbox, and we provision a test environment for you.

Sandbox access is request-based today. You tell us what you are building, and we provision a test environment with sample data and the test keys your integration needs — so you can develop and verify against a realistic store before going anywhere near production. Provisioning is not yet self-serve, so it starts with a short request rather than an instant sign-up.

A test environment with sample data: a realistic store to build and verify against, without touching anything live.
Test keys, provisioned for you: we set up the credentials scoped to your sandbox once your request is approved.
The same safety model: approval-gated, staging-first and reversible, so what you prove in the sandbox is how it behaves in production.
Request a sandbox We provision it By request
1 Tell us what you are integrating Request
2 We provision your test environment Sample data
3 You receive scoped test keys Test keys
4 Build and verify against the docs Develop
Provisioning is not self-serve yet — request access and we set it up for you.
Architecture & security

Built control-first, so your security reviewers have something real to evaluate.

Vortex IQ sits as a cross-stack operating layer over the systems you already run. We lead with what is verified and point you at the evidence rather than asking you to trust marketing copy. The full posture and the AI/LLM data-governance summary live in the Trust Center.

01 · Certification

ISO 27001 certified

Our information security management is ISO 27001 certified, and SOC 2 is in progress. The current status, scope and supporting documentation live in the Trust Center for your security team to review.

02 · AI / LLM governance

How models see your data

AI actions are approval-gated and read-first. We are transparent about what data is processed, where, and under what controls, with the data-governance summary documented for review.

03 · Operational safety

Safe by construction

Staging-first changes, a full audit trail and one-click rollback mean autonomy never means unaccountable. Every change has a record and a reverse path, and a human approves before anything reaches production.

Documentation for your reviewers

The Trust Center is where your security team can review our posture, certifications and AI data-governance summary in detail. A high-level architecture whitepaper is available on request through your partner contact or enterprise sales — ask and we will share it for your evaluation.

Developer support

A clear support path — not an invented response time.

We will not quote a number we cannot stand behind on a marketing page. What we can give you is a clear route to a human. Start with the live docs, then reach a person through your partner contact or enterprise sales, who will route you to the right engineer and agree concrete support commitments in writing as part of your engagement.

A
Read the docs firstdocs.vortexiq.ai is the live reference for the core API and the connectors, and answers most integration questions directly.
B
Reach a humanGet to a person through your partner contact or enterprise sales, who routes you to the right engineer for your integration.
C
Agree commitments in writingFor partners and enterprise engagements, support commitments are scoped and confirmed in your agreement, not promised as a one-size figure here.

Why we frame support as a path

Response times and channels vary by partner type and the criticality of your integration. Publishing a single SLA figure would over-promise for some and under-serve others. The honest answer is a clear route to the right person, with concrete commitments agreed in your engagement. Get in touch and we will point you at the right channel.

For platform & tech partners

Integrating a platform or building a product alongside Vortex IQ?

If you are a platform, a tech partner or a systems integrator, the developer docs are the technical entry point — but the partnership model, where Vortex IQ fits alongside your stack, and the live connector directory sit on dedicated pages built for that conversation.

For tech partners

Where Vortex IQ fits alongside your platform, and how the partnership works. Read-first by design, so it complements your stack rather than competing with it.

The integrations directory

93 live integrations across the systems commerce teams actually use, all read-first. The directory lists what connects today and is the right thing to send to technical evaluators.

93 live integrations
Developer questions

Building on Vortex IQ, answered.

Where is the API and connector documentation?

It is live at docs.vortexiq.ai. That is the canonical, maintained reference for the core API and for the connectors — authentication, how read-first connectors behave, what each connector reads and how approval-gated writes work. We keep the API surface there rather than restating it on this page, so you always build against the current version.

How do I get a sandbox?

Sandbox access is request-based. Tell us what you are integrating through the contact form and we provision a test environment with sample data and scoped test keys for you. Provisioning is not yet self-serve, so it starts with a short request rather than an instant sign-up — once it is approved you receive what you need to build and verify.

How do writes work — can the engine change a live store on its own?

No. Connectors are read-first, the engine proposes a scoped change and explains it, the change is applied staging-first, and a human approves before anything reaches production. Anything that goes live can be rolled back in one click, with a full audit trail. The exact endpoints and payloads for that flow are documented at docs.vortexiq.ai.

What is your security posture and how do LLMs handle our data?

Vortex IQ is ISO 27001 certified and SOC 2 is in progress. AI actions are approval-gated and read-first, and we are transparent about what data is processed and under what controls. The full posture and the data-governance summary live in the Trust Center for your security team, and a high-level architecture whitepaper is available on request through your partner contact or enterprise sales.

What platforms and connectors are supported?

Vortex IQ runs on BigCommerce, Shopify, Adobe Commerce and WooCommerce, with 93 live integrations across the wider stack and documentation for every connector at docs.vortexiq.ai. The integrations directory lists what connects today; if a connector you need is not listed, get in touch and we can tell you where it sits on the roadmap.

How do I get developer support?

Start with the live docs, which answer most integration questions. Beyond that, support is a clear path to a human: reach us through your partner contact or enterprise sales and we route you to the right engineer. We do not publish an invented response time here; concrete support commitments are scoped and agreed in writing as part of partner and enterprise engagements.

I am a platform or tech partner — where should I start?

The developer docs at docs.vortexiq.ai are the technical entry point. For the partnership model and where Vortex IQ fits alongside your stack, see the tech partners page; for what connects today, see the integrations directory. Read-first by design means Vortex IQ complements your platform rather than competing with it.

Start building

Read the docs. Request a sandbox. Build with confidence.

The documentation is live at docs.vortexiq.ai and the model is built control-first — read-first, approval-gated, staging-first and reversible. Request a sandbox and we will provision a test environment so you can prove your integration before it touches production.

Integrate directly into your store's platform