Integrations
Connect Zippykind to the tools you run
Plug Zippykind into your POS, storefront, and systems, through native integrations, Zapier, and an open API.
Integrations
Ways to connect
Connect the tools you already use to Zippykind's delivery software, so new orders become delivery tickets on their own.
Zapier
Trigger deliveries and sync data across 5,000+ apps, no code required.
Epic (Willow)
Available. Prescription orders you mark for delivery in Epic (Willow) arrive in Zippykind as delivery tickets. Contact us to connect your pharmacy.
Liberty Software
Available. Prescription orders you mark for delivery in Liberty arrive in Zippykind as delivery tickets. Contact us to connect your pharmacy.
PioneerRx and PrimeRx
Available. Our Bridge Agent is a small program that runs at your pharmacy and passes delivery orders from PioneerRx and PrimeRx to Zippykind. Contact us to set it up.
REST API & webhooks
Create tickets, pull live status, and push events from your own systems.
POS & storefronts
Send orders straight from your point of sale or online store.
Most connected
The five apps customers plug in first
Each one runs through our Zapier app, so it is a few clicks and no code. The same trigger works for every other app Zapier reaches.
-
Shopify
New Shopify orders arrive as delivery tickets, with the customer, address and items already filled in.
via Zapier -
WooCommerce
Every WooCommerce order that needs a local delivery becomes a ticket the moment it is paid.
via Zapier -
Square
Ring up a delivery at the Square register and it is on a route before the receipt finishes printing.
via Zapier -
BigCommerce
BigCommerce checkouts hand off straight to dispatch, with nobody re-typing an address into two systems.
via Zapier -
Wix
Wix Stores orders route into Zippykind and the buyer gets the live tracking link automatically.
via Zapier
Running something else? Zapier reaches 750+ more apps, and anything it does not reach, our open REST API does.
Inside the software
Connect it, test it, then watch it run
Building an integration is not a support ticket here. Everything below is a screen in your own account, on every plan.
Push every status change into your own system
Add a URL on the Webhooks screen and Zippykind posts delivery ticket updates to it as they happen. You set it up yourself, in your own account, and it is live as soon as your endpoint answers.
- Add a webhook yourself: paste the URL, choose all events or just one, and it starts
- Ownership is proved once, and your endpoint can answer in whichever of four ways it supports
- Active webhooks are listed with their event and status, and can be removed at any time
Watch the integration work, the day you build it
API Connect charts every call you make and every webhook we send back, broken out by scope, so you can see traffic arriving instead of guessing at it.
- API and webhook connection charts side by side, over the date range you choose
- Counted per scope: newTicket, updateTicket, trackTicket, ticketHistory, listDrivers
- Webhook events counted the same way: assigned, accepted, started, delivered
Build against the real API without creating real deliveries
Switch test mode on and the same endpoints, the same keys and the same responses write to a separate testing set instead of your live dashboard.
- No live tickets, so nothing reaches your dispatch dashboard
- No driver is assigned and no customer is notified while you are testing
- Test tickets get their own list, so you can read back exactly what you created
Read the request and the response, while you are still typing
Every call is logged as it happens with its status, scope, endpoint and ticket. Open any row for the full request and response body.
- Searchable and sortable, so a failing call is found in seconds and not in a terminal
- Webhook deliveries get their own log, with the endpoint we called and what it returned
- Enough to debug an integration end to end without anyone from Zippykind on the call
Don't see your integration?
Tell us what you run, our open API connects the rest.
