INTEGRATIONS

Plays well with your stack

Because every feature is API-first, integrating yas.sh is a matter of HTTP calls. Here are the patterns teams use most — plus the full API reference.

Developer Note: These are integration patterns using our REST API and UTM builder — not first-party marketplace plugins. Every integration below can be implemented cleanly via HTTP requests.

Slack

WEBHOOK

Post a message to a channel every time a link is clicked or created — campaign launches without leaving Slack.

Zapier

ZAP

Trigger zaps from new links and clicks, or create links from any app in your Zapier workspace.

Shopify

APP / API

Shorten product and campaign URLs at scale; QR codes for packaging and shelf talkers.

WordPress

PLUGIN / API

Shorten links from posts with a custom function calling the v1 API — no plugin dependency required.

Google Analytics 4

UTM

Build UTM-tagged links with the campaign manager so GA4 sees clean source/medium/campaign dimensions.

HubSpot

UTM / API

Track content and campaign performance with consistent tagged links across HubSpot assets.

Custom webhooks

API

The API-first design means anything with HTTP can integrate: CRMs, CRMs, BI pipelines, internal tools.

The universal integration: the API

# Create a link from any system
curl -X POST https://yas.sh/api/v1/links \
  -H "Authorization: Bearer yas_live_..." \
  -H "Content-Type: application/json" \
  -d '{"originalUrl":"https://example.com","customAlias":"launch"}'

# → { "shortCode": "launch", "url": "https://yas.sh/launch", ... }

Want a first-party integration for your platform? Tell us about it →

About YAS.SH integrations

Integrations connect YAS.SH to the systems you already run: webhooks for event delivery, the REST API for direct calls, and the SDK for typed access from application code. This page describes what each integration path is suited to and what it costs you in operational complexity.

The honest framing is that most integrations are one API call and a webhook endpoint. Where something needs more than that, the additional work is described rather than glossed over.

Integration paths

REST API
Direct HTTP calls with JSON in and out, documented per endpoint with runnable examples.
Webhooks
Event delivery to an endpoint you control, signed so you can verify authenticity before acting on the payload.
SDK
A typed client for application code, wrapping authentication, retries and error handling.

Verifying webhook deliveries

Webhook payloads are signed with an HMAC over the raw request body. Verify the signature against the bytes exactly as received, before any JSON parsing — re-serializing the body changes whitespace and key order and therefore changes the signature. The HMAC Generator on this site reproduces the computation if you need to debug a mismatch.

Frequently asked questions

How do I verify a webhook signature?

Compute an HMAC over the raw request body with your signing secret and compare it to the header value using a constant-time comparison. Sign the bytes as received; parsing and re-serializing the JSON first is the most common cause of mismatches.

What happens if my endpoint is down?

Deliveries are retried with backoff for a bounded period. Persistent failures are surfaced in your dashboard rather than retried indefinitely.

Is there a sandbox environment?

Test credentials and test-mode calls let you exercise the integration without affecting production data or counting against production limits.