Legacy API endpoints are being retired — migrate by June 1, 2027
If your team uses our legacy API endpoints, here’s an important heads-up: we’re retiring them, and you’ll need to move to our current API before they’re switched off.
Deadline: June 1, 2027. After that date, the legacy endpoints will stop responding.
Does this affect you? Only if you call the legacy API directly from your own code or scripts. If you use our native integrations (Mailchimp, Klaviyo, HubSpot, GoHighLevel, and the rest) or Zapier, you’re all set — nothing changes for you.
What’s next: we’re putting the finishing touches on our current API and a full migration guide. We’ll post it right here in the changelog — and email it to you — as soon as it’s ready, well ahead of the deadline.
There’s plenty of runway, and we’re here to help. If you call the legacy API directly and want to get ahead of the migration, reach out to support any time.
We also sent this to your inbox earlier this week — this post is here so it’s easy to find and link back to.