The Growth Dept CRO API
Create draft tests, start and end them, read results and run email and SMS message tests from your own scripts and agents.
- One key per brand, with the scopes you choose
- The same results the app shows
- Every problem listed when a draft does not validate
At a glance
Does Growth Dept CRO work with Growth Dept CRO API?
What can it do?
List and read tests, create drafts, pause, start, resume and end tests, read results, and create and run message tests.
Which scopes?
tests:read, tests:write, tests:start and messages:write.
Which test types?
Every type the app has: split URL, content, theme, shipping, flag, multivariate, offer, price, checkout and post-purchase.
What do results look like?
The same object the app's results tab reads, cached for five minutes, with fresh=1 to recompute.
Can I preview a draft?
Yes. Each test comes with one preview link per group, which marks the visit as QA so it never counts.
How it works
How Growth Dept CRO API and Growth Dept CRO work together
Make a key
Settings, API keys. Choose only the scopes the script needs.
Create a draft
POST /api/v1/tests with the test as JSON. Problems come back as a list.
Start and read
Start it with a key that has tests:start, then read /results.
Get started
To get started
- 01
Create a key
In the brand's settings, with the scopes you need.
- 02
Draft a test
Send the test as JSON; fix anything the answer lists.
- 03
Start it
With tests:start, once the storefront runtime is on.
What it works with
FAQ
Growth Dept CRO API questions
What happens if a step does not apply?
Can a key read other brands?
Find out what is worth testing on your store.
Book a 45-minute call with the Growth Dept team. We look at your store and your traffic, and tell you which tests to run first.