Developer API & integrations · Webhooks & integrations

Send feature requests from your admin or the API

Request platform improvements from the Feedback page in your admin — or programmatically via the API with the feedback scope. You get a receipt when it's submitted and an email when your request ships.

The feature-request pipeline

When you want something the platform doesn't do yet, submit a feature request from the Feedback page in your admin. Your request goes to the AutoCreator team for review; approved requests enter the build queue, and when the feature ships you're notified by email automatically. It's a real pipeline, not a suggestion box — many platform features started life as tenant requests.

Submitting via the API

The same flow is available programmatically, which is handy if your own AI agent spots a gap while working, or you want a button in an internal tool. Create a key with the "Submit feature requests" scope, then send a POST request to https://your-domain.com/api/v1/feature-requests with a JSON body containing a title (3–200 characters) and a description (10–2,000 characters). A successful submission returns a 201 status with a pending state.

A receipt email goes to the admin who created the API key, and the platform team is notified — members are never emailed by this flow. The request is attributed to that admin, so keys must have been created by a real admin account to submit.

Writing requests that get built

The best requests describe the problem and the desired outcome, not just a feature name: what you were trying to do, where you got stuck, and what a good solution would let you accomplish. Concrete examples from your own workflow help the team scope it correctly the first time.

Good to know

  • There's also a generic tool form of the same call (feedback.submitFeatureRequest) if your agent works through the tools endpoint.
  • Check your email after submitting — the receipt confirms it landed, and a follow-up arrives when the feature goes live.

Related articles