Integrations and no-code
Put Venued into the tools you already use, without writing a backend.
Two motions, and that is all
Nearly everything people build on Venued is one of two things. Something happens and you want to know: a ticket sells, an event goes public. That is a webhook, and Venued calls you. You want a list of something: your events for your own website, your confirmed orders for a spreadsheet. That is the API, and you call us.
Reach for the webhook first. It arrives once, at the moment the thing happens, and it costs you nothing while nothing is happening. A job that asks every five minutes whether anything changed is both slower to notice and the usual reason somebody runs into a rate limit.
Getting told when something happens
In Zapier, the trigger is Webhooks by Zapier, set to Catch Hook. In Make, it is a custom webhook. Either one hands you a URL. Paste that URL into Studio under Webhooks, tick the events you want, and you are connected.
The full list of fields, as paths you can map one to one, is in the API reference. Verifying the signature is in Webhooks, and it matters: without it, anyone who learns your URL can post to it.
Reading your own data out
Every endpoint is an ordinary HTTPS request with your key in an Authorization header, which every no-code tool with an HTTP step can send. The two most people want are GET/v1/events and GET/v1/orders.
Paste the whole address, host included:
https://europe-west3-venued.cloudfunctions.net/publicApi/v1/events?limit=50Answers come back as {"data": …}, with has_more and next_cursor beside it on lists. That shape is the same on every endpoint, including the ones that will never have a second page, so whatever you build to read one response reads all of them.
Putting your events on your own site
Call GET/v1/eventsfrom your site’s backend, cache the answer for a few minutes, and render it however your site renders things. Each event comes back with its title, its start, its place and its image.
When you need a developer
Plainly, so you do not spend an evening finding out the hard way. Verifying a webhook signature means computing an HMAC, which most no-code tools cannot do on their own. Publishing an event cannot be done through the API at all, by design. Anything involving money, refunds or issuing tickets is not something the API can reach, whoever is writing it.
Everything else on this page is a URL, a key and a field mapping.