How to Add an Offer to Vereel Through the API

What you can do with the API

The API has two sides. Browsing is open: anyone can list Vereel's public offers and read one in detail, with the same information a visitor sees on the site and no money amounts. Writing is for brands: with a token from your settings you can create an offer, change it while it waits for review, add photos, and read the status of everything you sent.

It deliberately stops there. The API cannot publish an offer, delete one, start a campaign or move money. Those steps stay in the app, where the terms and the payment checks already live.

Step 1: create a token

Sign in as a brand and open Settings › API tokens. Name the token after what will use it (“Agency script”, “Shop feed”), choose read and write if it should create offers, and pick how long it lasts: 30, 90 or 365 days. Tick the Cooperation Terms for the offers it will send, because every offer sent with the token carries that acceptance.

Copy the token the moment it appears. Vereel keeps only a hash of it, so it cannot be shown again; if you lose it, revoke it and create another. Treat it like a password: keep it on a server or in your tool's secret storage, never in a web page or a public repository.

Step 2: send your first offer

Pick a category first: GET https://www.vereel.com/api/v1/public/categories returns the list with ids. Then send the offer. The request below is enough to start; swap in your own text, category id and image address.

curl -X POST https://www.vereel.com/api/v1/public/my/offers \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Autumn skincare set",
  "description": "Show how our vitamin C serum fits into your morning routine: one Reel and two Stories.",
  "offerType": "PRODUCT",
  "platforms": ["instagram"],
  "categoryIds": ["00000000-0000-0000-0000-000000000001"],
  "isPayment": false,
  "isBarter": true,
  "productServiceValue": 150,
  "currency": "PLN",
  "includedDescription": "One 30 ml bottle of the serum, shipped to you before you start.",
  "imageUrls": ["https://example.com/serum.jpg"]
}'

What comes back

A successful call answers 201 with the offer's id and the status in_review. When something is wrong the answer is 422, and details names each field, for example a category id that does not exist.

Step 3: add a photo

An offer needs at least one photo before it can be approved. The simplest way is imageUrls, as above: Vereel downloads the image itself. The address must be https on a public server, and the file a JPEG, PNG or WebP of at most 5 MB. Vereel checks the file's content, not its name.

If the image is not ready yet, add it later through the offer's images endpoint: send {"url": …}, or ask for an upload address, upload the file to it and attach the returned path within 15 minutes. An offer holds up to six photos, and the first is the cover.

Step 4: follow it through review

Every offer sent through the API waits in a review queue. A person at Vereel looks at it and either approves it or returns it to your drafts with a reason. You hear about it either way, in the app and by email. Until then the offer is not public, and you can still edit it. GET /my/offers/{id} shows its status: in_review, active, rejected (with the reviewer's note) or closed.

Once it is approved, the offer is live like one created in the wizard: creators can apply, and you handle applications in the app.

Limits worth knowing

A few rules protect you and Vereel from a flood of accidental requests:

• A request body is at most 64 KB.
• You can have up to 20 offers in review at once, and send up to 50 new API offers a day.
• One token can make up to 30 changes in 10 minutes.
• When the Cooperation Terms change, accept them again in Settings › API tokens: until then the token can read but not create offers.