Considering: webhooks, a read API, and platform connectors

Under Review

Adrián Lozano

We want Termerly to plug into the rest of your stack. We're weighing webhooks for key events (a consent accepted, a policy published, a data request received), a public read API so you can pull your latest policy text and versions wherever you need them, and a server-side SDK for deeper integrations.

We're also looking at honoring standard browser privacy signals and adding one-click connectors for the platforms you already use.

All under review. If you would build on an API or automations, tell us what you would wire up first.

June 2, 2026

Activity feed

CF
Chloe Foster
Before I invest in an API integration, how stable would it be? I don't want to wire this in and have the contract change on me in three months.
June 2, 2026
•
Replay
Sofia Martinez
Webhooks on consent and policy events are what I'd build on first. I'd push accept/decline into my own analytics and trigger a rebuild when a policy is republished.
June 2, 2026
•
Replay