Activepieces API
/api/v1/connection-keys* endpoint removal
Stopped workingSubscribe to Activepieces APIShare
On September 14, 2026, Activepieces API removed legacy product-embed connection-key and app-credential endpoints. Any calls targeting /api/v1/connection-keys* fail after this date.
Calls it hits
/api/v1/connection-keys*
What to use instead of these calls
Use the current embedding flow, which provisions users and connections through a platform signing key as outlined in the Embedding docs.
In Activepieces API's words
The legacy product-embed connection-key and app-credential endpoints are removed
Facts
- API
- Activepieces API
cloud.activepieces.com - Kind
- Endpoint removal
- Announced
- September 14, 2026
- Takes effect
- September 14, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Activepieces API's own pages
Questions
When does this change take effect?
Calls to /api/v1/connection-keys* on Activepieces API stopped working on September 14, 2026.
What happens to calls after September 14, 2026?
They have failed since September 14, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Activepieces API 3
-
/api/v1/flow-templates*Endpoint removal Stopped working -
/api/v1/app-credentials*Endpoint removal Stopped working -
No date
POST /v1/license-keys/verifyEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.