Simple, Fast, Code first and Compile time generated OpenAPI documentation for Rust
utoipa - Auto-generated OpenAPI documentation
Pronounced /u:ΛtoΚ:i.pΙ/ or /u:ΛtoΚΛaΙͺ.piΛeΙͺ/ whatever works better for you.
Want to have your API documented with OpenAPI? But don't want to be bothered with manual YAML or JSON tweaking? Would like it to be so easy that it would almost be utopic? Don't worry: utoipa is here to fill this gap. It aims to do, if not all, then most of the heavy lifting for you, enabling you to focus on writing the actual API logic instead of documentation. It aims to be minimal, simple and fast. It uses simple proc macros which you can use to annotate your code to have items documented.
The utoipa crate provides auto-generated OpenAPI documentation for Rust REST APIs. It treats code-first approach as a first class citizen and simplifies API documentation by providing simple macros for generating the documentation from your code.
It also contains Rust types of the OpenAPI spec, allowing you to write the OpenAPI spec only using Rust if auto generation is not your flavor or does not fit your purpose.
Long term goal of the library is to be the place to go when OpenAPI documentation is needed in any Rust codebase.
Utoipa is framework-agnostic, and could be used together with any web framework, or even without one. While being portable and standalone, one of its key aspects is simple integration with web frameworks.
Choose your flavor and document your API with ice-cold IPA
|Flavor|Support| |--|--| |actix-web|Parse path, path parameters and query parameters, recognize request body and response body, utoipa-actix-web bindings. See more at docs| |axum|Parse path and query parameters, recognize request body and response body, utoipa-axum bindings. See more at docs| |rocket| Parse path, path parameters and query parameters, recognize request body and response body. See more at docs| |Others*| Plain utoipa without extra flavor. This gives you all the basic benefits listed below in Features section but with little less automation.|
Others* = For example warp but could be anything.
Refer to the existing examples to find out more.
Features
- OpenAPI 3.1
- Pluggable, easy setup and integration with frameworks.
- No bloat, enable what you need.
- Support for generic types
Tuples, arrays and slices cannot be used as generic arguments on types. Types implementing
ToSchema manually should not have generic arguments, as
they are not composeable and will result compile error.
- Automatic schema collection from usages recursively.
request_body attribute.
* Response body from response body attribute or response content attribute.
- Various OpenAPI visualization tools supported out of the box.
- Rust type aliases via
utoipa-config.
What's up with the word play?
The name comes from the words utopic and api where uto are the first three letters of utopic and the ipa is api reversed. Aaand... ipa is also an awesome type of beer :beer:.
Crate Features
macrosEnableutoipa-genmacros. This is enabled by default.yaml: Enables yaml_serde serialization of OpenAPI objects.actixextras: Enhances actix-web integration with being able to
path, path and query parameters from actix web path attribute macros. See
docs or examples for more details.
rocketextras: Enhances rocket framework integration with being
path, path and query parameters from rocket path attribute macros. See docs
or examples for more details.
axumextras: Enhances axum framework integration allowing users to useIntoParamswithout
parameterin attribute. See docs
or examples for more details.
debug: Add extra traits such as debug traits to openapi definitions and elsewhere.chrono: Add support for chronoDateTime,Date,NaiveDate,NaiveDateTime,NaiveTimeandDuration
string types with additional format information.
format: date-time for DateTime and NaiveDateTime and format: date for Date and NaiveDate according
RFC3339 as ISO-8601. To
override default string representation users have to use value_type attribute to override the type.
See docs for more details.
time: Add support for timeOffsetDateTime,PrimitiveDateTime,Date, andDurationtypes.
string. OffsetDateTime and PrimitiveDateTime will use date-time format. Date will use
date format and Duration will not have any format. To override default string representation users have to use value_type attribute
to override the type. See docs for more details.
jiff02Add support for jiff 0.2Timestamp,Zoned, andcivil::Datetypes.
string. Timestamp and Zoned will use date-time format. civil::Date will use
date format. To override default string representation users have to use value_type attribute
to override the type. See docs for more details.
decimal: Add support for rust_decimalDecimaltype. By default
String. If you wish to change the format you need to override the type.
See the valuetype in component derive docs.
decimalfloat: Add support for rustdecimalDecimaltype. By default
Number. This feature is mutually exclusive with decimal and allow to change the default type used in your
documentation for Decimal much like serdewithfloat feature exposed by rust_decimal.
- bigdecimal: Add support for bigdecimal BigDecimal type. By default
it is interpreted as String. If you wish to change the format you need to override the type.
See the valuetype in component derive docs.
- bigdecimalfloat: Add support for bigdecimal BigDecimal type. By default
it is interpreted as Number. This feature is mutually exclusive with bigdecimal and allows changing the default type
used in your documentation for BigDecimal.
- uuid: Add support for uuid. Uuid type will be presented as String with
format uuid in OpenAPI spec.
ulid: Add support for ulid.Ulidtype will be presented asStringwith
ulid in OpenAPI spec.
url: Add support for url.Urltype will be presented asStringwith
uri in OpenAPI spec.
smallvec: Add support for smallvec.SmallVecwill be treated asVec.openapi_extensions: Adds traits and functions that provide extra convenience functions.
request_body docs for an example.
repr: Add support for reprserde'srepr(u)andrepr(i)attributes to unit type enums for
preserve_order: Preserve order of properties when serializing the schema for a component.
preservepathorder: Preserve order of OpenAPI Paths according to order they have been
#[openapi(paths(...))] macro attribute. If disabled the paths will be
ordered in alphabetical order. However the operations order under the path will be always constant according to specification
indexmap: Add support for indexmap. When enabledIndexMapwill be rendered as a map similar to
BTreeMap and HashMap.
nonstrictintegers: Add support for non-standard integer formatsint8,int16,uint8,uint16,uint32, anduint64.rc_schema: AddToSchemasupport forArc<T>andRc<T>types. Note! serdercfeature flag must be enabled separately to allow
Arc<T> and Rc<T> types. See more about serde feature flags.
configEnablesutoipa-configfor the project which allows defining global configuration options forutoipa.
Default Library Support
- Implicit partial support for
serdeattributes. See docs for more details. - Support for http
StatusCodein responses.
Install
Add dependency declaration to Cargo.toml.
[dependencies]
utoipa = "5"
Examples
Create type with ToSchema and use it in #[utoipa::path(...)] that is registered to the OpenApi.
use utoipa::{OpenApi, ToSchema};
#[derive(ToSchema)] struct Pet { id: u64, name: String, age: Option<i32>, }
mod pet_api { /// Get pet by id /// /// Get pet from database by pet id #[utoipa::path( get, path = "/pets/{id}", responses( (status = 200, description = "Pet found successfully", body = Pet), (status = NOT_FOUND, description = "Pet was not found") ), params( ("id" = u64, Path, description = "Pet database id to get Pet for"), ) )] async fn getpetbyid(petid: u64) -> Result<Pet, NotFound> { Ok(Pet { id: pet_id, age: None, name: "lightning".to_string(), }) } }
#[derive(OpenApi)] #[openapi(paths(petapi::getpetbyid))] struct ApiDoc;
println!("{}", ApiDoc::openapi().toprettyjson().unwrap());
Above example will produce an OpenAPI doc like this:
{
"openapi": "3.1.0",
"info": {
"title": "application name from Cargo.toml",
"description": "description from Cargo.toml",
"contact": {
"name": "author name from Cargo.toml",
"email": "author email from Cargo.toml"
},
"license": {
"name": "license from Cargo.toml"
},
"version": "version from Cargo.toml"
},
"paths": {
"/pets/{id}": {
"get": {
"tags": [
"pet_api"
],
"summary": "Get pet by id",
"description": "Get pet from database by pet id",
"operationId": "getpetby_id",
"parameters": [
{
"name": "id",
"in": "path",
"description": "Pet database id to get Pet for",
"required": true,
"schema": {
"type": "integer",
"format": "int64",
"minimum": 0
}
}
],
"responses": {
"200": {
"description": "Pet found successfully",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/Pet"
}
}
}
},
"404": {
"description": "Pet was not found"
}
}
}
}
},
"components": {
"schemas": {
"Pet": {
"type": "object",
"required": [
"id",
"name"
],
"properties": {
"age": {
"type": [
"integer",
"null"
],
"format": "int32"
},
"id": {
"type": "integer",
"format": "int64",
"minimum": 0
},
"name": {
"type": "string"
}
}
}
}
}
}
Modify OpenAPI at runtime
You can modify generated OpenAPI at runtime either via generated types directly or using Modify trait.
Modify generated OpenAPI via types directly.
#[derive(OpenApi)]
#[openapi(
info(description = "My Api description"),
)]
struct ApiDoc;
let mut doc = ApiDoc::openapi(); doc.info.title = String::from("My Api");
You can even convert the generated OpenApi to OpenApiBuilder.
let builder: OpenApiBuilder = ApiDoc::openapi().into();
See Modify trait for examples on how to modify generated OpenAPI via it.
Go beyond the surface
- See how to serve OpenAPI doc via Swagger UI check utoipa-swagger-ui crate for more details.
- Browse to examples for more comprehensive examples.
- Check IntoResponses and ToResponse for examples on deriving responses.
- More about OpenAPI security in security documentation.
- Dump generated API doc to file at build time. See issue 214 comment.
FAQ
How to implement ToSchema for external type?
There are few ways around this that are elaborated here in detail.
Auto discover for OpenAPI schemas and paths?
Currently there is no build in solution to automatically discover the OpenAPI types but for your luck there is a pretty neat crate that just does this for you called utoipauto.
License
Licensed under either of Apache 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, shall be dual licensed, without any additional terms or conditions.