A Sample OpenAPI 3.0 File to Get Started
Take a look at an example OpenAPI 3.0 file to get familiar with what's new in OpenAPI 3.0. API Evangelist Kin Lane walks us through his thoughts and the next steps.
Join the DZone community and get the full member experience.
Join For FreeI am investing more time into my Schema.org work, alongside my learning about OpenAPI 3.0. I’m pretty excited about the components object, and I want to push forward some of my Schema.org dictionary ideas, to help folks get better at reusing common schema throughout their work. Schema.org is the most robust vocabulary out there, and we shouldn’t be reinventing the wheel in this area. I know the most important reason that folks aren’t using is that they either don’t know about it, or they are just lazy. I figure if I create some ready to go schema in an OpenAPI 3.0 components object, maybe people will be more inclined to put common schema to use.
To share my components I need basic OpenAPI 3.0 shell to hold all my reusable schema. I really don’t care about the paths, and other elements being there. So I headed over to the OpenAPI 3.0 Github repo and borrowed the sample Petstore OpenAPI 3.0 my friend Darrel Miller created:
openapi"3.0.0"
info
version1.0.0
title Swagger Petstore
license
name MIT
servers
url http //petstore.swagger.io/v1
paths
/pets
get
summary List all pets
operationId listPets
tags
pets
parameters
name limit
in query
description How many items to return at one time (max 100)
requiredfalse
schema
type integer
format int32
responses
200
description An paged array of pets
headers
x-next
description A link to the next page of responses
schema
type string
content
application/json
schema
$ref"#/components/schemas/Pets"
default
description unexpected error
content
application/json
schema
$ref"#/components/schemas/Error"
post
summary Create a pet
operationId createPets
tags
pets
responses
201
description Null response
default
description unexpected error
content
application/json
schema
$ref"#/components/schemas/Error"
/pets/{petId}
get
summary Info for a specific pet
operationId showPetById
tags
pets
parameters
name petId
in path
requiredtrue
description The id of the pet to retrieve
schema
type string
responses
200
description Expected response to a valid request
content
application/json
schema
$ref"#/components/schemas/Pets"
default
description unexpected error
content
application/json
schema
$ref"#/components/schemas/Error"
components
schemas
Pet
required
id
name
properties
id
type integer
format int64
name
type string
tag
type string
Pets
type array
items
$ref"#/components/schemas/Pet"
Error
required
code
message
properties
code
type integer
format int32
message
type string
I will change all the information in this sample to reflect my work, but I figured before I did I would share this example document with my readers. At first glance, it doesn’t look much different than version 2.0 of OpenAPI, but once you start studying you see the differences. You see the responses have JSON specific content types inserted in between their schema references. There is also a components object, with a couple of schema present–this is all I need. There are a bunch of other things you can store in your components object, but I think this provides a nice first look at what is going on.
If you are looking for some other working examples of OpenAPI 3.0 in action, head over to Mike Ralphson’s repository, he has some additional ones you can play with. I don’t know about you, but I learn from others. I need to reverse engineer API definitions from other people before I become fluent myself. I’m going to spend some time hand-crafting some OpenAPI 3.0 definitions, so that I become more fluent. It is tedious work when you are just getting going, but once you get it down, it becomes like any other language you use. I’m hoping to cut my teeth on this Schema.org work. I’m going to replicate the OpenAPI 2.0 work I did when I created over a 1,000 OpenAPIs for each of the Schema.org objects. I’m going to be using them to deploy APIs for clients, and in my API training and storytelling. I want all my examples to be reusable patterns that already exist, not anything custom that I pull out of my magic arse.
Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments