Three steps
1
Connect your store
In the CrossUp admin, add your store. You get a
connection_id (cn_…),
which goes in the path of every call.2
Issue your connector key
From the admin, issue a
cct_… key. It is shown only once: store it
in your server’s secrets.3
Send catalog and orders
The first time, all at once with a snapshot. After that, each change.
Your first load walks you through it.
Request your connector setup
Tell us which platform or system you run and we build the connector with you.
Where it fits
- VTEX or another platform without the CrossUp app.
- Your own or headless store: your backend already has the catalog; the connector forwards it.
- An ERP or a file: one export a day is enough, sent as a snapshot.
- A platform with many stores: the same code serves all of them. Each store is a connection with its own key.
Your connector key
Thecct_… key lives on your server, never in a browser, and goes in
Authorization: Bearer. It works for one connection only: presented against
another, the answer is 401.
- It doesn’t expire. An automated process can’t depend on someone renewing it.
- Up to 5 active per connection: production, staging, an ERP, a migration.
- The admin shows it by its last four characters (
cct_…7k3m), so you know which one is deployed.
What you’ll see
In the admin, your store connected and your key with its last four characters. With the first load, every batch answers entity by entity.If you don’t see it
Your first load
Your whole catalog in CrossUp, with a snapshot.
The canonical model
Which entities you send and which fields they carry.