API and webhooks: URLHop working inside your systems

Creating 300 QR codes by hand for the new catalog? Changing destinations one by one when your site moves? Let your systems do it. With an API key, they create links and QR codes, change destinations and read analytics. With webhooks, URLHop tells your tools when something happens.

Read the API docs →

When doing it by hand stops scaling

A store with hundreds of products, a real estate agency listing new homes every day, an agency managing dozens of clients. At some point, creating and updating links in the dashboard turns into repetitive work, and repetitive work leads to mistakes. The URLHop API does what the dashboard does, but from your own system, spreadsheet or automation tool. Webhooks go the other way: they tell you when something changes.

What you can do with the API

The URLHop API is a REST API that speaks JSON, with a public OpenAPI reference. Use it to create, edit and delete short links; change the destination of a QR code that's already printed; download QR codes; import up to 200 links at a time from a CSV; organize links into folders and tags; manage link-in-bio pages; and read each link's analytics. The dashboard's plan rules apply to the API too: for example, adding a password to a link requires Pro, and exporting raw analytics events as JSON requires Business.

Webhooks: URLHop tells you when something happens

Register an HTTPS address and choose your events. For each event, URLHop sends a POST with the data as JSON, signed with HMAC-SHA256 so you can confirm it came from us. If your system is down, delivery is retried for up to 9 hours, and the dashboard shows the delivery history. The events are: link created, updated or deleted (link.created, link.updated, link.deleted); click limit reached (link.click_limit_reached); link-in-bio page created, updated or deleted (tree.created, tree.updated, tree.deleted); domain verified (domain.verified); and 80% or 100% of the month's tracked clicks (usage.threshold_reached). It works with any tool that receives webhooks, such as n8n, Make or Zapier.

Real-world examples

How teams connect URLHop to the tools they already use.

Who uses it, and what happens

How to get started

You can make your first call in a few minutes.

Step by step

Which plan includes it

The API and webhooks are on the Starter plan and above, and in the 30-day free Pro trial every new account gets, no credit card. Some features follow the plan: password-protected links and CSV analytics export are Pro; raw analytics export as JSON through the API is Business. If your account goes back to Free, API keys stop working until you subscribe again, but no link is ever switched off.

Try the API free for 30 days

API and webhook questions

Does URLHop have an API?

Yes. URLHop has a public REST API, with an OpenAPI reference at app.urlhop.me/api/v1/docs/, to create and edit short links, download QR codes, import links from CSV, manage link-in-bio pages and read analytics. It's available from the Starter plan and in the 30-day free Pro trial.

How does API authentication work?

With API keys created under Settings → API. Each key is shown only once, only works for the workspace it was created in and goes in the Authorization: Bearer header. The limit is 120 requests per minute per key, and you can revoke a key whenever you want.

Which events do URLHop webhooks send?

link.created, link.updated, link.deleted, link.click_limit_reached, tree.created, tree.updated, tree.deleted, domain.verified and usage.threshold_reached, the last one when the account reaches 80% and 100% of the month's tracked clicks. Each delivery is a JSON POST signed with HMAC-SHA256.

How do I know a webhook really came from URLHop?

Every delivery includes an X-URLHop-Signature header with a timestamp and an HMAC-SHA256 signature of the timestamp and the request body, made with the secret shown when you create the webhook. Recompute the signature on your server and reject deliveries that are too old or don't match. The docs include a ready-made example.

Does URLHop work with n8n, Make or Zapier?

Yes, through webhooks and the API. Any tool that receives webhooks can handle URLHop events, and any tool that makes HTTP requests can call the API with a key. These aren't official integrations with those platforms; they're open features that work with them.

What if my server is down when an event happens?

URLHop retries after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, and the dashboard shows each delivery and its status. Your server should answer with a 2xx code within 5 seconds. An endpoint is switched off after 50 failures in a row.