Skip to Content
APIsAPIs

APIs

Flexkit generates a GraphQL API from each deployed project schema. Studio also uses a same-origin application handler for its signed-in requests.

SurfaceAddress or locationUse
Hosted project GraphQLhttps://PROJECT_ID.api.flexkit.io/graphqlAuthorized data queries and mutations.
Deployed schemahttps://PROJECT_ID.api.flexkit.io/schemaThe schema the Studio renders, for signed-in members.
Studio application handlerYour app’s /api/flexkit/...Framework-managed Studio authentication and proxy requests.
MCP serverhttps://mcp.flexkit.ioOAuth-enabled AI client access (MCP).
Custom toolsYour app’s /api/flexkit/toolsSigned discovery and invocation by Flexkit.

Replace PROJECT_ID with the ID from Dashboard Settings → General. These endpoints use different authentication flows; a working credential for one is not proof that every other surface accepts it.

Start with authentication, queries, and tokens. Use Explorer to inspect the schema before constructing data operations.

For data-change notifications, configure outgoing webhooks. A custom interface for members can read the deployed entities, menu groups and validation from the schema endpoint. The Studio UI is not extended from code; to add behaviour, use custom tools, skills, automations, the API and the Studio hooks described in Extending Flexkit. See the reference index for the documented integration surfaces, and integrations for every way to connect external systems.

Last updated on