re-port-flow.com

Sign in to Report Flow, create or open a workspace, then open the workspace's API連携 tab to copy the application key (ak_...). The docs say one application key is generated per workspace and can be regenerated from the same screen if needed. For quick start, register a free account first if you do not already have one.

For user-authorized integrations, create/register a public OAuth client in Report Flow and use Authorization Code + PKCE against the OIDC issuer described in OAuth 2.0 docs. The docs define Public Client (is_public=true) for apps such as SPAs, mobile apps, and Make.com-style integrations, with PKCE required and no client_secret. Use the discovery document at openid-configuration to obtain the authorization and token endpoints.

For server-to-server or backend integrations, create/register a confidential OAuth client in Report Flow and use it with OAuth 2.0 as documented in OAuth 2.0 docs. The docs define Confidential Client (is_public=false) for client_credentials; send client_id and client_secret either with HTTP Basic auth or as form fields (client_secret_post) to the token endpoint discovered from openid-configuration. The resulting bearer access token is then used against the protected resource API at https://api.re-port-flow.com/v1/....

For the official MCP server, the client self-registers automatically and starts OAuth in the browser; you do not manually create an API key for the AI client. Per the MCP server docs, local reportflow-mcp and the hosted MCP endpoint both use OAuth 2.0 with dynamic client registration. Add the server in your MCP client, then complete Sign in → choose workspace → consent when prompted.