Creating Webhooks Directly via the TrackVia API

Zapier and Workato both let you trigger webhooks as part of a larger automation, but you don't need either one just to get a webhook out of TrackVia. If you only need TrackVia to notify an external system when a record is created, updated, or deleted, you can create that webhook yourself with a single API call — no Zapier or Workato account required.

Before you start

You'll need:

• API access enabled on your account, plus an API Key and Auth Token. See API Authentication and Access if you haven't set these up yet.
• The View ID of the view you want to attach the webhook to. A webhook is tied to a specific view, so pick the view whose record changes (created/updated/deleted) you want to be notified about.
• A target URL — the endpoint on the receiving system that should get the notification.

The endpoint

Send a POST request to:

https://<your-account>.trackvia.com/openapi/zapier/views/{viewId}/api/hooks?user_key={apiKey}

Replace:

• <your-account> with your TrackVia subdomain
• {viewId} with the ID of the view you're attaching the webhook to
• {apiKey} with your API Key

Don't let the /openapi/zapier/ segment in the path throw you off — this is the same underlying webhook mechanism TrackVia's Zapier integration uses internally, but it works as a standalone API call and doesn't require a Zapier account or subscription.

Request body

{
    "target_url": "https://example.com/hooks/incoming",
    "event": "created,updated,deleted"
}

Example request

curl --location 'https://<your-account>.trackvia.com/openapi/zapier/views/{viewId}/api/hooks?user_key={apiKey}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {authToken}' \
--data '{
    "target_url": "https://example.com/hooks/incoming",
    "event": "created,updated,deleted"
}'

A few notes on the fields above:

• {authToken} is the Auth Token generated for your API user (see API Authentication and Access) — not your account password.
• target_url should be the webhook-receiving URL provided by the system you're integrating with.
• event accepts any combination of the three event types, so you can register one webhook for just created events, or one that covers all three.

When to use this vs. Zapier or Workato

This direct API method is a good fit when:

• You already have a receiving endpoint built and just need TrackVia to call it — you don't need any of the "no-code" automation, filtering, or multi-step logic that Zapier or Workato provide.
• You want to avoid the cost or setup overhead of a Zapier or Workato account for a single, simple use case.

If you need to transform data, chain multiple steps together, or connect to apps that require their own authentication (Slack, Salesforce, etc.), Zapier or Workato are still the better tools for the job.

Related articles

• API Authentication and Access
• TrackVia API
• Zapier
• Workato