This is an OpenAPI specification for the FusionAuth API.
Here's the openapi specification YAML file.
It can be used in a variety of contexts, including generating client libraries, tracking API changes over time and testing. More here: https://openapi.tools/
Use this file to do all your OpenAPI related actions. For additional information and documentation on FusionAuth refer to https://fusionauth.io.
- Generate libraries
- Java
- Ruby
- Test the YAML
- Postman Collection
- Known issues
- Next steps
- Questions and support
- Contributing
- License
Install either Swagger: https://github.com/swagger-api/swagger-codegen/ or openapi: https://github.com/OpenAPITools/openapi-generator
These instructions will be for openapi.
To build the java client libraries:
bin/java/build.sh
This will produce a jar you can use.
To build the ruby client libraries:
bin/ruby/build.sh
Read the readme in ruby/README.md
for installation and usage instructions. To install it as a gem locally using --dev, I had to build it and then install a couple of rspec dependencies by hand.
More docs here: https://openapi-generator.tech/docs/generators/ruby
To build the dart client libraries:
bin/dart/build.sh
This will produce a dart package you can import.
pip3 install schemathesis # one time
schemathesis run -vvvv --checks not_a_server_error openapi.yaml --base-url http://localhost:9011 -H "Authorization: bf69486b-4733-4470-a592-f1bfce7af580"
You can also explore around with our API in postman.
Here's our Postman profile and public workspace.
- Log into the FusionAuth Postman team
- Click the
Import
button on the left hand nav, toward the top - Import the API definition. This should also create a new collection
- Rename the API and collection with the correct API version
- Copy over the description from a previously imported API (easiest to do it in two tabs)
- Copy the new collection into the workspace.
- Go to the FusionAuth Postman homepage and edit the new collection and put the date on it.
While the specification is valid, the generated client libraries haven't been fully exercised.
- FusionAuth uses polymorphic responses for some API calls, particularly Identity Providers. The support for that in client library generation code is problematic, based on our testing. I'm not sure if there are workarounds, but it seems like some work is being done. See swagger-api/swagger-codegen#10011 and OpenAPITools/openapi-generator#10880 (comment) for an openapi workaround.
- This spec is built using the fusionauth-client-builder project JSON files. This covers almost all of the API, but not everything. A few calls may be missing. If you find one that you need, please open a bug report.
- Deprecated API endpoints are not included.
- There's no information about what parameters are required or not, because that is not part of the API JSON files.
- There are certain operations, status codes and security mechanisms (JWT auth, cookies for auth) that are not currently supported because they are not included in the API JSON files.
- OAuth grant actions aren't currently supported (the /oauth2/ endpoints).
- There is an issue generating the ruby client libraries. OpenAPITools/openapi-generator#11350 has the repro steps. The
RUBY_POST_PROCESS_FILE
environment variable is a workaround.
We are publishing this to see how useful the FusionAuth community finds it. We welcome feedback on your usage of this spec. We'll plan to revisit this after we've received some feedback on how useful it is and determine if there are additional features we need to implement.
Please open bugs on this repository. For support in using this, please see the next section.
If you have a question or support issue regarding this OpenAPI spec, we'd love to hear from you.
If you have a paid edition with support included, please open a ticket in your account portal. Learn more about paid editions here.
Otherwise, please post your question in the community forum.
Bug reports and pull requests are welcome on GitHub at https://github.com/FusionAuth/go-client.
If you find an issue with syntax, etc - this is likely a bug in the generation script. Feel free to submit a PR against the Client Builder project.
The code is available as open source under the terms of the Apache v2.0 License.