Nothing arrives at my endpoint

Your URL has to answer publicly over HTTPS. A local address or anything behind a login will never receive a delivery, and the usual fix while developing is a tunnelling tool that gives you a public URL.

How to tell a real delivery from a forged one

Check the signature against your webhook signing secret on every request, and reject anything that fails. A webhook URL is public by nature, so the signature is the only thing separating us from anyone who finds it.

Using this with Zapier or Make

Both have a generic webhook trigger and an HTTP action. Point their webhook at us and call our API from their HTTP step - you do not need a published Webkio app to do either, and there is not one yet.

Integrations

Send your website data to any tool

Signed webhooks and a documented REST API, so anything that can catch a request can hear about an order the moment it happens.

Signed webhooks plus a REST API

How it actually works

Subscribe a URL to an event and Webkio posts to it every time that event happens, signed so you can verify it came from us. The REST API covers the same objects in the other direction. Zapier and Make both work this way today: each has a generic webhook trigger and an HTTP step, which is all either needs. A published Webkio app in their marketplaces is still to come.

Setting it up

Create an API key in your Webkio account.
Subscribe a URL to the events you want, in the console or with a single API call.
Verify the signature on every delivery against your webhook signing secret.
In Zapier or Make, use their own webhook trigger and HTTP steps.

The contacts screen in Webkio, listing people captured from a site — One of the objects the API covers. Orders, bookings and subscribers have screens of their own.

What can start a workflow

Every one of these fires the moment it happens on any site in your account.

New order order.created: An order is placed in your shop. Card payments may still be pending.
Order paid order.paid: Payment for an order is confirmed.
New booking booking.created: A customer books an appointment.
New rental reservation rental.reserved: A customer reserves a rental item.
New subscriber subscriber.created: Someone joins your email list.
New property enquiry property_enquiry.created: A visitor enquires about a property listing.
New product review review.submitted: A customer reviews a product.

When it does not work

Nothing arrives at my endpoint: Your URL has to answer publicly over HTTPS. A local address or anything behind a login will never receive a delivery, and the usual fix while developing is a tunnelling tool that gives you a public URL.
How to tell a real delivery from a forged one: Check the signature against your webhook signing secret on every request, and reject anything that fails. A webhook URL is public by nature, so the signature is the only thing separating us from anyone who finds it.
Using this with Zapier or Make: Both have a generic webhook trigger and an HTTP action. Point their webhook at us and call our API from their HTTP step - you do not need a published Webkio app to do either, and there is not one yet.

Worth knowing first

In Zapier and Make you assemble these steps yourself rather than picking Webkio from their app list, because the published apps are still to come.

Build the site first

Every integration here attaches to a site you have already made. Start from a template for your trade and connect things once it is live.

Start free All integrations