Dify service API keys and end-user identity
Calling Dify apps from a backend: per-app API keys, the user field Dify never authenticates, how it scopes conversations and files, and why API and web app users stay separate.
Dify APIs and app delivery
Getting Dify apps into products and pipelines: service API keys and end-user identity, embedded web apps, the difyctl CLI, and promoting apps between instances.
Embedding Dify web apps in websites and portals
Chat bubble, iframe and custom embedding of published Dify apps, passing user context and inputs, and the SSO and CSP issues that appear when apps sit inside another site.
Running Dify apps from CI pipelines with difyctl
Using the official Dify CLI to run apps from scripts and CI jobs, OAuth sign-in instead of stored keys, structured JSON output and letting coding agents call Dify apps as tools.
Promoting Dify apps from staging to production on Community
A release process for Community deployments without Enterprise Environments: separate instances, DSL exports in Git, version names and release notes, credentials per instance and rollback by version restore.
Streaming and long-running Dify API calls
Keeping streamed responses and long workflows alive through proxies and load balancers: SSE timeouts, resuming workflow event streams, stopping generation and webhook payload limits.
Dify web app settings and branding on Community
Customizing published web apps: titles, descriptions, input placeholders, logo replacement on supported editions, and what the license allows for the console.
