We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similar to the go-algorand repo, we should provide an endpoint for fetching the open api specfile.
Unlike the old swagger.json endpoint, the v2 endpoints are split into multiple pieces. We need to find a way to merge them together.
The text was updated successfully, but these errors were encountered:
I'm currently drafting the SDK guides on the Developer Portal as curl http://{host:port}/swagger.json
curl http://{host:port}/swagger.json
I'd appreciate some feedback on anticipated implementation, priority, roadmap for this.
Sorry, something went wrong.
/openapi
any progress?
Successfully merging a pull request may close this issue.
Similar to the go-algorand repo, we should provide an endpoint for fetching the open api specfile.
Unlike the old swagger.json endpoint, the v2 endpoints are split into multiple pieces. We need to find a way to merge them together.
The text was updated successfully, but these errors were encountered: