Welcome · Velisto API

WelcomeWhat the Velisto API does for agencies and CRMs, and how to make your first calls.The Velisto API lets your own code work with Velisto. Push listings in from your CRM or website, design images from Velisto’s templates, and make and schedule posts for your social channels. Webhooks tell your server as things happen. Every answer is JSON.These guides explain how it works. The reference lists every call, with what it takes and what it answers.What you can build

Keep Velisto’s listings in step with your CRM

Send each listing with Create or update a listing, under your CRM’s own id. The first call adds it, and the next ones update it. When a listing sells, Velisto can make a “Just sold” post for you to approve. See Listings from a CRM.

Post to your channels from your own app

Make posts with Create a post: as a draft, for a time, in the next free posting time, or now. One post can go to many channels, each with its own text and settings. See Posting.

Design images from Velisto’s templates

Pick a template, render it with a listing’s photos and details, and use the images in a post. Or write a design of your own and save it as a template. See Templates and rendering.

Hear what happens with webhooks

A webhook sends a message to your server when a listing changes, a post goes out or fails, a design is ready, or a channel needs reconnecting. See Webhooks.

Automate with Zapier, Make and n8n

Use Velisto from Zapier, Make and n8n, with their own tools for calling an API and catching webhooks. See Zapier, Make and n8n.

Read analytics

Read a channel’s daily numbers and a post’s numbers, from what Velisto has already stored. See Analytics.

The basicsEvery call goes to an address under this base URL:https://api.velisto.ai/v1So GET /me means GET https://api.velisto.ai/v1/me. Most calls are about one workspace, and their addresses start with /workspaces/{workspace}, where {workspace} is its id. These guides write that part as …, so …/posts means https://api.velisto.ai/v1/workspaces/{workspace}/posts.

Send JSON, with Content-Type: application/json, except when you upload a file.

Workspaces, channels, listings, media and posts have whole numbers as ids, like 42. Templates, renders, webhooks and keys have strings, like 01k9zq5d6e7f8g9h0j1k2m3n4p.

Times are in ISO 8601. Answers give them in UTC, like 2026-11-12T09:30:00Z.

A single thing comes back inside data. A list comes a page at a time (see Paging).

These docs are at https://developers.velisto.ai.Quick start

In Velisto, open Settings → API and press Create key. Only the account’s Owner and Admins can make keys.

Copy the key. It starts with vl_live_ and is shown only once, so keep it somewhere safe, like a password manager.

Send the key in the Authorization header of every call, as a Bearer token. Ask who the key is:

curl https://api.velisto.ai/v1/me \ -H "Authorization: Bearer vl_live_xxxxxxxxxxxx" \ -H "Accept: application/json"The answer names the key, its account, the person who made it and the ids of the workspaces it can reach:{ "data": { "key": { "id": "01k9zq5d6e7f8g9h0j1k2m3n4p", "name": "Our CRM", "access": "write", "all_workspaces": true, "created_at": "2026-11-08T09:30:00Z", "analytics": false }, "account": { "id": 7, "name": "Harbour Realty", "plan": "team", "read_only": false, "trial": false, "limits": { "listings": null, "social_connections": 10, "workspaces": 3, "seats": 5 } }, "maker": { "id": 12, "name": "Sara Khan", "email": "sara@example.com" }, "workspace_ids": [42] } }

Push a listing from your CRM. my-crm is a name you pick for your CRM, and A-1001 is your CRM’s id for the listing:

curl -X PUT https://api.velisto.ai/v1/workspaces/42/listings/external/my-crm/A-1001 \ -H "Authorization: Bearer vl_live_xxxxxxxxxxxx" \ -H "Content-Type: application/json" \ -d '{ "title": "Sea-view apartment in Marina Bay", "price": 450000, "currency": "EUR", "beds": 3, "baths": 2, "status": "For Sale", "status_kind": "active", "photos": ["https://crm.example.com/photos/a-1001-front.jpg"] }'The answer is 201 with the listing the first time, and 200 after that. Keep its id.

Schedule a post about it. GET …/channels lists the workspace’s channels and their ids:

curl https://api.velisto.ai/v1/workspaces/42/posts \ -H "Authorization: Bearer vl_live_xxxxxxxxxxxx" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 5f0c7a52-2f8e-4c1b-9a37-1d6b2e4f8c90" \ -d '{ "mode": "schedule", "channel_ids": [318], "scheduled_at": "2026-11-12T09:30:00+01:00", "listing_id": 1207, "text": "Just listed: a sea-view apartment in Marina Bay." }'

Keys only ever go in the Authorization header, never in the address.

Where to go nextAuthenticationWhat a key may do, where it works, and when it stops.Listings from a CRMPushing listings in by your CRM’s own id.PostingMaking, changing, publishing and approving posts.Templates and renderingDesigning images from templates and your own designs.MediaAdding images to a workspace’s Library.WebhooksMessages to your server as things happen.AnalyticsA channel’s daily numbers and a post’s numbers.ErrorsThe error codes, and what each one means.Rate limitsHow many calls and new posts a key may make in a minute.PagingGetting a list a page at a time.Retrying safelySending a request twice without it being done twice.Zapier, Make and n8nUsing the API and webhooks from them.ChangelogWhat changed, and when.