Skip to main content
Most app endpoints take a user field: your own identifier for the end user a call acts on behalf of. Dify never authenticates it, so pick a stable value per person, such as an account ID, and send it consistently. Dify starts tracking a new user the first time it appears, and one app key serves any number of end users.

What user Scopes

user controls what each call can see and do:
  • Conversations: listing, history, renaming, and deletion all operate on that user’s conversations only.
  • Files: not scoped. Any run in the same workspace can reference an upload by its id, whatever user it sends. If users’ uploads must stay private from each other, check in your app that an id belongs to the user you send it with.
  • Stopping generation: the chat-family stop endpoints act only when user matches the one that started the reply. A mismatch is silently ignored—the call succeeds either way, so it isn’t detectable from the response. Workflow’s Stop Workflow Task does not check user.

API Users and Web App Users Stay Separate

Traffic through the API and Dify’s hosted web app keep separate identities: conversations your API users create never appear in the web app, and web app conversations never appear through the API.

Resolve an End-User ID

Some responses carry an end-user ID instead of full details, such as created_by in the Upload File response. Get End User Info resolves it.