Webhook

The webhook commands register and manage webhook endpoints, browse the event catalogue, and verify webhook signatures locally. All commands are root-scoped — they do not require --account.

Changed in 0.15.0: webhook state-diff <account_id> is removed — no v2 endpoint returns account-level state deltas. There is no replacement; reconcile missed events from the webhook deliveries themselves.

webhook create

# Register a new webhook endpoint (write, --preview accepted)
# --source, --request-url, and --account-ids are required
curviate webhook create \
  --source <messaging|user|account_status> \
  --request-url <https://yourapp.com/webhooks/curviate> \
  --account-ids <acc_id1,acc_id2> \
  [--name <name>] \
  [--format <json|form>] \
  [--no-enabled] \
  [--events <event1,event2>] \
  [--data <key1,key2>]

--account-ids is comma-separated. --events and --data are also comma-separated. The webhook is created enabled by default — pass --no-enabled to create it disabled.

webhook list

# List all registered webhooks (paginated)
curviate webhook list [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>]

webhook events

List the canonical event type catalogue. Not paginated — --all is not accepted.

# Get all supported event types (read, not paginated)
curviate webhook events

webhook get

Get a single webhook by id. The plaintext secret is never returned on a read — only secret_prefix.

# Get a single webhook (read)
curviate webhook get <webhook_id>

webhook update

Update a registered webhook. --source is immutable — passing it causes the command to exit with code 2 without making an API call.

# Update a webhook (write, --preview accepted)
# --source cannot be changed; passing it is a usage error (exit 2)
curviate webhook update <webhook_id> \
  [--request-url <url>] \
  [--name <name>] \
  [--enabled <true|false>] \
  [--format <json|form>] \
  [--events <event1,event2>] \
  [--data <key1,key2>] \
  [--account-ids <acc_id1,acc_id2>]

webhook delete

# Delete a webhook (write, --preview accepted)
curviate webhook delete <webhook_id>

webhook verify

Offline command — no network call, no API key required. Verifies a webhook payload's HMAC-SHA256 signature locally by calling constructEvent from the SDK directly. Use this to validate your signature-verification logic without running a live server.

# Verify a webhook signature offline (no Curviate client constructed)
curviate webhook verify \
  --secret <signing_secret> \
  --header <x-curviate-signature-header-value> \
  [--body <path-to-body-file|-stdin>] \
  [--max-age-secs <n>]

On success, the parsed event JSON is written to stdout (exit 0). On a signature mismatch, a structured error is written to stdout and a summary to stderr (exit 2).

Examples

Create a messaging webhook

curviate webhook create \
  --source messaging \
  --request-url https://yourapp.com/webhooks/messages \
  --account-ids acc_YOUR_ACCOUNT_ID \
  --name "Message events"

Create a webhook disabled

curviate webhook create \
  --source user \
  --request-url https://yourapp.com/webhooks/users \
  --account-ids acc_YOUR_ACCOUNT_ID \
  --no-enabled

Preview a webhook update

curviate webhook update wh_YOUR_WEBHOOK_ID \
  --request-url https://yourapp.com/webhooks/v2/messages \
  --preview

Disable a webhook

curviate webhook update wh_YOUR_WEBHOOK_ID --enabled false

Verify a webhook payload from a file

# Raw body saved from the incoming HTTP request
curviate webhook verify \
  --secret whsec_YOUR_SIGNING_SECRET \
  --header "t=1234567890,v1=abc123..." \
  --body ./webhook-payload.json

Verify a webhook payload from stdin

# Pipe the raw request body directly
cat raw-body.txt | curviate webhook verify \
  --secret whsec_YOUR_SIGNING_SECRET \
  --header "t=1234567890,v1=abc123..." \
  --body -

Get a single webhook

curviate webhook get wh_YOUR_WEBHOOK_ID
COMPANY · LEGAL

Privacy Policy

Redmer Holding GmbHLast updated July 25, 2026

Who we are

Curviate is operated by Redmer Holding GmbH ("Curviate", "we", "us"), a German GmbH registered at Amtsgericht Bonn, HRB 29957, registered address Hostertstraße 16, 53332 Bornheim, Germany. Full company details are on our Imprint. We haven't appointed a statutory Data Protection Officer, since our processing doesn't reach the scale or sensitivity that requires one. Privacy questions go to privacy@curviate.com.

The two roles we play

When you create an account and use Curviate, we process your own data (identity, billing, API keys, connector authorizations). For that data, we are the controller.

When you use Curviate to act on your own connected LinkedIn account, viewing profiles, sending messages, managing engagement, that content and those contacts belong to that account and its people. You are the controller of that data; we are the processor, acting only on your instructions, under the Data Processing Agreement between us. If one of your contacts has a question about being reached through Curviate, you're who they should contact first; email privacy@curviate.com if you need help routing it.

What we collect, and why

DataWhy
Account identity (name, email, sign-in method)Create and secure your account
Your LinkedIn credentialsOperate the actions you request
LinkedIn content returned by an API callFulfil that specific request, nothing more
API keys and connector (OAuth) authorizationsAuthenticate your API, CLI, MCP, or SDK requests
Billing detailsCharge you correctly and meet our tax obligations
Usage and security logsKeep the service reliable and abuse-free
Support messagesRespond to you
Website analytics, only if you opt inUnderstand how the site is used

We rely on our contract with you, our legitimate interest in running and securing the service, our legal obligations (tax law, for example), and, for analytics, your consent. We never sell your data or use it to train models.

Where it's processed, and who else touches it

Our infrastructure runs in the EU. Hosting: Railway. Database and auth: Supabase, Ireland. Email: Resend. Payments: Stripe. Network security: a DDoS-protection provider sits in front of our app and never sees or stores request content. LinkedIn connectivity: a third-party infrastructure provider that lets us execute LinkedIn actions on your behalf. Error tracking: Sentry, Frankfurt. Product analytics: PostHog, Frankfurt. Uptime monitoring: Better Stack.

We give the current, named list of every provider above, plus our Data Processing Agreement, to any customer who asks: security@curviate.com.

Outside the EU

All customer LinkedIn data, account data, and telemetry are processed and stored exclusively in EU regions of our sub-processors. A few providers we rely on (Stripe and Sentry, for example) are headquartered outside the EU/EEA; where that applies, it's covered by their own GDPR safeguards, typically the EU Standard Contractual Clauses.

How long we keep it

DataRetention
Account and workspace dataWhile your account is active
Closed accountRecoverable for 7 days, then deleted on day 8
LinkedIn credentialsUntil you disconnect that account
LinkedIn contentNot stored; any transient cache clears within 1 hour, never indexed, never used for training
API keysUntil you revoke or rotate them
Connector (OAuth) authorizationsAccess token ~1 hour; refresh token up to ~12 months, or until you revoke it, whichever comes first
Billing recordsAs required by German tax law, currently up to 10 years
LogsA short operational window; metadata only, never message content

The 12-month figure above is a server-side credential for a connected AI agent or app. It is not a cookie and doesn't touch your browser session; see Cookies below for that. You can see and revoke every connector from Authorized applications in your dashboard at any time.

Cookies

We keep cookies to a minimum, and ask before anything beyond the essentials runs.

Strictly necessary, no consent needed:

NamePurposeExpiry
cc_cookieRemembers your cookie choice12 months
curviate-themeRemembers light/dark mode (local storage, not a cookie)Persistent
sb-*-auth-tokenKeeps you signed inWhile active; cleared on sign-out

Analytics, only if you accept:

NamePurposeExpiry
_gaGoogle Analytics: distinguishes visitors2 years
_gidGoogle Analytics: distinguishes visitors24 hours
_ga_<container id>Google Analytics: persists session state2 years

No advertising cookies, ever. Accept and reject are equally easy, and you can change your mind any time via Cookie Preferences in the footer; we won't ask again for 12 months unless something material changes. Our LinkedIn connect flow and OAuth authorization screen never set anything beyond the essentials, so no banner appears there.

Connecting an AI agent or app

Curviate is built for AI agents and automated clients as much as for people. If you connect an app like Claude, or your own code, via an API key or an OAuth connector, it can act on your workspace within the access you gave it. What it does with anything it receives back, including what it sends to its own AI model, is between you and that provider; review its practices before connecting it. Review and revoke any connection any time from your dashboard.

Your rights

You can access, correct, delete, restrict, or object to your data, port it elsewhere, and withdraw consent at any time: email privacy@curviate.com. Closing your account starts the 7-day recoverable window above. We don't make automated decisions about you that have a legal or similarly significant effect. You can also complain to a supervisory authority; ours is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), www.ldi.nrw.de, though you're free to complain to the one in your own country instead.

Keeping it secure

Credentials are encrypted and never logged, returned, or shared. LinkedIn actions run through native, humanized flows; full detail is on our Security & Compliance page. If a breach puts your rights at risk, we'll notify the authorities and you, as GDPR requires. Curviate isn't directed at, or offered to, anyone under 16.

Changes

We'll update this page when our practices change, and reset the cookie prompt if the change is material.

Contact