langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Publish a live OpenAPI specification #2864

New Issue
Closed
opened 2026-02-21 17:50:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:50:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @mamift on GitHub (May 1, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

I want to create my own client for the dify API in C# and TypeScript. I see there are Java, Ruby and Go client libraries already created, but they do not seem to be based on an OpenAPI specification; i.e. they're hand written. I think this is a mistake. What is more useful for programmers these days is to take a specification like an OpenAPI spec, and use that to create a client library in a language of their own choice.

The reasoning is: vendors should not bother creating language-specific client libraries for their APIs or services anymore as it is too much hassle to:

  • manually write all the connecting/glue code, which is idiomatically different in each language
  • support the different type systems used by different languages
  • support the package and dependency management systems that each language has

What should be done is: vendors should publish specifications that allow any programmer of any language to create their own clients using code generators that take the specification as input and generates scaffolding code that can be used to create a client library in a language of their own choosing.

In the case of OpenAPI, a very popular tool for generating clients is the openapi-generator-cli. It supports generating client code for about 24+ languages.

2. Describe the feature you'd like to see

Publish an OpenAPI specification for the entirety of the dify API surface, from the dataset API, to the chatting/workflow API.

And ideally it should be available in app, like how currently, the {DIFY_APP_URL]/app/{APP_UID}/develop URL is used to display the documentation for a custom app's API.

A good example of what I'm talking about is JIRAs API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about

They provide an OpenAPI spec.

3. How will this feature improve your workflow or experience?

I can generate C# and TypeScript code for dify API. And others will be able to create client code in nearly any programming language of their choice using a code generator like openapi-generator.

This would also mean the dify maintainers would no longer need to maintain the Java, Ruby and Go client libraries for others to use; just point future devs to the the OpenAPI spec and they can create their own libraries!

Alternatively, if you wanted to keep your own 'official' client libraries for a select few languages, you can just use the code generator to automatically update official client libraries whenever the OpenAPI spec changes; all you would need to do is just re-run the code generator against an updated OpenAPI spec.

4. Additional context or comments

Doing this would also provide the benefit of being able to import the spec into tools like Postman.

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @mamift on GitHub (May 1, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? I want to create my own client for the dify API in C# and TypeScript. I see there are [Java](https://github.com/langgenius/java-client), [Ruby ](https://github.com/langgenius/ruby-sdk)and [Go client ](https://github.com/langgenius/dify-sdk-go) libraries already created, but they do not seem to be based on an OpenAPI specification; i.e. they're hand written. I think this is a mistake. What is more useful for programmers these days is to take a specification like an OpenAPI spec, and use that to create a client library in a language of their own choice. The reasoning is: vendors should not bother creating language-specific client libraries for their APIs or services anymore as it is too much hassle to: - manually write all the connecting/glue code, which is idiomatically different in each language - support the different type systems used by different languages - support the package and dependency management systems that each language has What should be done is: vendors should publish specifications that allow any programmer of any language to create their own clients using code generators that take the specification as input and generates scaffolding code that can be used to create a client library in a language of their own choosing. In the case of OpenAPI, a very popular tool for generating clients is the [openapi-generator-cli](https://github.com/OpenAPITools/openapi-generator-cli). It supports generating client code for [about 24+ languages](https://openapi-generator.tech/docs/generators). ### 2. Describe the feature you'd like to see Publish an OpenAPI specification for the entirety of the dify API surface, from the dataset API, to the chatting/workflow API. And ideally it should be available in app, like how currently, the `{DIFY_APP_URL]/app/{APP_UID}/develop` URL is used to display the documentation for a custom app's API. A good example of what I'm talking about is JIRAs API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about They provide an [OpenAPI spec](https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json). ### 3. How will this feature improve your workflow or experience? I can generate C# and TypeScript code for dify API. And others will be able to create client code in nearly any programming language of their choice using a code generator like [openapi-generator](https://openapi-generator.tech/docs/installation). This would also mean the dify maintainers would no longer need to maintain the [Java](https://github.com/langgenius/java-client), [Ruby](https://github.com/langgenius/ruby-sdk) and [Go client](https://github.com/langgenius/dify-sdk-go) libraries for others to use; just point future devs to the the OpenAPI spec and they can create their own libraries! Alternatively, if you wanted to keep your own 'official' client libraries for a select few languages, you can just use the code generator to automatically update official client libraries whenever the OpenAPI spec changes; all you would need to do is just re-run the code generator against an updated OpenAPI spec. ### 4. Additional context or comments Doing this would also provide the benefit of being able to import the spec into tools like Postman. ### 5. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:50:56 -05:00
yindo closed this issue 2026-02-21 17:50:56 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2864
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?