What is a REST API, again?<\/h2>\n\n\n\n
If you work at all with the web, you will have probably heard of many “REST APIs”, particularly the WordPress REST API<\/a>. Any article dealing with a REST API devotes its beginning to explaining what<\/strong> a REST API is. While we follow that pattern, we’ll try to be as concise as possible.<\/p>\n\n\n\n The “API” acronym stands for “Application Programming Interface”. In layman’s terms, it means the tools and controls (the Interface<\/em>) the server (typically a website) makes available to the client (the Application in API – typically a browser, app, or other website) for accessing data. Our main concern with APIs typically involves the format the data is exchanged in – “how do we use this?”<\/p>\n\n\n\n The “REST” acronym stands for “REpresentational State Transfer” which means that the state of the transaction between a client and the server providing a RESTful API is wholly contained in the response the client receives, so “WYSIWYG” for data. HTTP protocol-based communications (what a browser uses to “get stuff” from the web) are considered to be the only domain where it makes sense to talk about REST APIs. We use the term “consume”<\/strong> to describe when a client uses an API (the Transfer).<\/p>\n\n\n\n “State” is the representation of how a client got what it currently holds: if you have $5 in your pocket and a shop receipt saying you paid for a $5 meal with a $10 bill, you know what you have ($5) and how you got there (spent $5 and got $5 in change). If all you had was the $5 bill, the scenarios leading to that might include you winning the lottery, losing it all to tricky raccoons, and finding a $5 bill on the ground.<\/p>\n\n\n\n So, for an API to be “RESTful”, said API should not require clients consuming<\/strong> it to keep track of a “state” and make full use of HTTP methods.<\/p>\n\n\n\n HTTP is a protocol, the one you use to commonly access a site using a URL like http:\/\/how-not-to-get-scammed-by-raccoons.org<\/strong>. It provides ways to do what you need to do on the web. Commonly you use the GET<\/samp> method to retrieve data from websites. In the case above, the HTTP request would look like this:<\/p>\n\n\n But GET<\/samp> is not the only existing HTTP method. When you submit a form, you are usually making a POST<\/samp> request to a URL. That request represents your intent to send<\/strong> data to the site instead of receiving<\/strong> data from it. When completing a login form, you press the submit button in the form, and the browser would make a request like this:<\/p>\n\n\n\n Since you are sending<\/strong> something, the user=luca&password=secret<\/samp> string represents what you are sending to the server. The syntax above does not correspond to any particular API and is merely for the purposes of this article–do not use that in your code, or raccoons will invade your home!<\/p>\n\n\n\n GET<\/samp> and POST<\/samp> are the most widely used HTTP methods, but there are more: DELETE<\/samp> is used to remove stuff from the server, PATCH<\/samp> or PUT<\/samp> are commonly used to edit data on the server, and HEAD<\/samp> and OPTIONS<\/samp> are used to fetch information about the server.<\/p>\n\n\n\n When an API makes full and correct use of the methods above, it is then considered “RESTful”. If I wanted to update my password on the site, I could use:<\/p>\n\n\n\n Notice I’m now using a different URL to perform the required operation, one that ends in \/api\/users\/luca<\/samp>. This could be translated as “call the api<\/samp> on http:\/\/how-not-to-get-scammed-by-raccoons.org<\/samp>: we need to update the details for one of the users<\/samp>, luca<\/samp> is the name, and set the password<\/samp> to new-secret<\/samp>“.<\/p>\n\n\n\n In technical terms, \/api<\/samp> is the site’s REST API root path<\/strong>, \/api\/users<\/samp> is an endpoint<\/strong> provided by the API, and luca<\/samp> is a parameter<\/strong> of the specific call.<\/p>\n\n\n\n If we wanted to remove my user from the site, we would issue this request to the server:<\/p>\n\n\n\n Now you know why a typical WordPress “Trash” link, which employs URLs such as http:\/\/tribe.localhost\/wp-admin\/post.php?post=6&action=trash&_wpnonce=25a5cdc0ba<\/samp>, is not RESTful: you are deleting something using the HTTP GET<\/samp> method.<\/p>\n\n\n\n Reading the examples, it’s clear that the site might authorize anyone<\/em> to make GET<\/samp> requests, but it would probably impose limits (in the form of authentication requirements) on performing operations like adding, updating and deleting a user. Or any kind of data, really. Almost any REST API, the WordPress and The Events Calendar APIs being no exception, will make full use of authorization to allow or not allow a user to perform an action. There are many ways to authenticate a user–for the time being, just keep the idea in mind.<\/p>\n\n\n\n The last piece of information you need to fully qualify as a REST API expert, is the notion of HTTP response codes<\/em>. These are numbers the server will use to tell the client what happened in response to a certain request. You are probably familiar with some: 404<\/samp> means what you were looking for was not found, 403<\/samp> means you are not authorized to do what you tried to do, 500<\/samp> means an internal error happened on the server, and so on. Feast your eyes on the full list of status codes here<\/a>, and get ready to explore The Events Calendar REST API.<\/p>\n\n\n\n We built The Events Calendar REST API to allow our users and ourselves to consume<\/strong> and manage events created with The Events Calendar from anywhere<\/strong>. In its most basic form, a REST API separates the content from its presentation, freeing developers and users from the unbreakable paradigm of a WordPress site and a WordPress theme.<\/p>\n\n\n\n “Anywhere” is a big concept, so here are some examples:<\/p>\n\n\n\n Since The Events Calendar REST API is built on top of the WordPress REST API<\/a> it inherits its excellent code, robustness, and security.<\/p>\n\n\n\n Now that we’ve sung the praises of The Events Calendar REST API, it’s time to see it in action!<\/p>\n\n\n\n The Events Calendar REST API is free and bundled with The Events Calendar plugin. It is PHP 5.2 compatible and requires WordPress 4.5 or above. Once you have installed the latest version of The Events Calendar, simply activate, and you’re ready to get started.<\/p>\n\n\n\n In the following examples, we’ll assume the site on which The Events Calendar REST API is active can be reached at http:\/\/tribe.localhost<\/samp>–so keep that in mind.<\/p>\n\n\n\n Once The Events Calendar is active, we’ll create an event, set its details, publish it, and preview it in the browser:<\/p>\n\n\n\n This is the familiar look of an event in the context of the Twenty Seventeen theme. Let’s now head, using a browser, to the address http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/events<\/samp>:<\/p>\n\n\n\n Uhm\u2026 not that nice. But wait: that’s the essence<\/strong> of what The Events Calendar REST API does: providing the raw data about the event without all the presentation stuff surrounding it.<\/p>\n\n\n\n Here is the response in a pretty format:<\/p>\n\n\n This time, I’ve specified some parameters for my request:<\/p>\n\n\n\n The REST API is using those parameters to narrow down the query. What if we only want to get a single event and not all of them? The data returned is identical to the one shown above but for that specific event only (content removed for brevity):<\/p>\n\n\n So far, we’ve seen the stock response format from The Events Calendar REST API, but what if we want to change the contents of that response? The following code should live in a plugin or in the current theme’s functions.php<\/samp> file:<\/p>\n\n\n And see that pop up in the response (content removed for brevity):<\/p>\n\n\n But wait for a second: what’s that json_ld<\/samp> stuff in the response? The code is full of filters you can use to customize your responses, not only for events but for venues and organizers as well. So we’re pretty confident there will always be a way for you to make it work the way you want it to. Take a look around in the src\/Tribe\/REST\/V1<\/samp> folder to begin with.<\/p>\n\n\n\n There is so much you can do with The Events Calendar REST API that you might get lost. Figuratively speaking, of course.<\/p>\n\n\n\n Instead of having to parse page after page of out-of-date documentation, Post-It notes, and Slack messages, The Events Calendar REST API comes with a documentation endpoint you can hit any time you’re lost. You can find it at \/wp-json\/tribe\/events\/v1\/doc<\/samp>.<\/p>\n\n\n\n Hitting the endpoint in a browser (http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/doc<\/samp> in our example) will provide–you probably guessed it–a JSON format object detailing all the functionalities available on the REST API. An insanely large amount of content has been omitted for your comfort:<\/p>\n\n\n Why a JSON object?<\/p>\n\n\n\n That entry at the beginning of the response saying “swagger”: “2.0”<\/samp> tells you that The Events Calendar REST API documentation comes in Swagger.io<\/a> format. If you copy and paste the whole response into the Swagger.io API editor<\/a>, it will be converted into easily readable documentation:<\/p>\n\n\n\n This has several advantages:<\/p>\n\n\n\n What else? Oh, right–since we provide documentation in Swagger.io format, you can generate client applications for The Events Calendar REST API from the Swagger.io editor<\/strong>. With one click.<\/p>\n\n\n\n Since The Events Calendar REST API documentation is generated by WordPress code, you can filter that too. What about documenting that raccoon_suspect_level<\/samp> field from before?<\/p>\n\n\n And here is the field in the Swagger.io output:<\/p>\n\n\n\n So far we’ve limited our request to what is publicly available on the site. By default, The Events Calendar REST API will show events in the same way the plugin would: if you are a visitor, a user who is not logged in, or a user with subscriber-level access, you will be shown public events, venues, or organizers only. If you are an editor up to an administrator, you will be shown private and draft posts, too.<\/p>\n\n\n\n Let’s try and see an example of how basic, cookie-based authentication would work in the context of the crappiest theme ever.<\/p>\n\n\n\n The way WordPress knows “who you are”, as a user, is by using cookies and “nonces”<\/a>. When we want to perform operations reserved for logged-in users with specific roles, WordPress will print on the page a string (a nonce<\/strong>) that has been generated using the information in the authentication cookies and a specific action. In the “Trash” link shown in the first paragraph\u2026<\/p>\n\n\n\nGET http:\/\/how-not-to-get-scammed-by-raccoons.org\/index.php\n<\/pre><\/div>\n\n\n
POST http:\/\/how-not-to-get-scammed-by-raccoons.org\/login.php
\nuser=luca&password=secret<\/code><\/p>\n\n\n\nPUT http:\/\/how-not-to-get-scammed-by-raccoons.org\/api\/users\/luca\n password=new-secret<\/pre>\n\n\n\n
DELETE http:\/\/how-not-to-get-scammed-by-raccoons.org\/api\/users\/luca<\/pre>\n\n\n\n
A REST API for The Events Calendar: how can we use it?<\/h2>\n\n\n\n
\n
A first example<\/h2>\n\n\n\n
![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/example-event-1-665x492.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/rest-example-events-665x280.png\")
<\/figure>\n\n\n\n\n{\n "events": [{\n "id": 6,\n "global_id": "tribe.localhost?id=6",\n "global_id_lineage": [\n "tribe.localhost?id=6"\n ],\n "author": "1",\n "status": "publish",\n "date": "2017-09-21 11:57:52",\n "date_utc": "2017-09-21 11:57:52",\n "modified": "2017-09-21 12:03:35",\n "modified_utc": "2017-09-21 12:03:35",\n "url": "http:\/\/tribe.localhost\/event\/example-event-1\/",\n "rest_url": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/events\/6",\n "title": "REST Event 1",\n "description": "Example content",\n "excerpt": "",\n "image": {\n "url": "http:\/\/tribe.localhost\/wp-content\/uploads\/2017\/09\/raccoon.jpg",\n "id": "8",\n "extension": "jpg",\n "width": 220,\n "height": 147,\n "sizes": {\n "thumbnail": {\n "width": 150,\n "height": 147,\n "mime-type": "image\/jpeg",\n "url": "http:\/\/tribe.localhost\/wp-content\/uploads\/2017\/09\/raccoon-150x147.jpg"\n }\n }\n },\n "all_day": false,\n "start_date": "2017-09-21 08:00:00",\n "start_date_details": {\n "year": "2017",\n "month": "09",\n "day": "21",\n "hour": "08",\n "minutes": "00",\n "seconds": "00"\n },\n "end_date": "2017-09-21 17:00:00",\n "end_date_details": {\n "year": "2017",\n "month": "09",\n "day": "21",\n "hour": "17",\n "minutes": "00",\n "seconds": "00"\n },\n "utc_start_date": "2017-09-21 08:00:00",\n "utc_start_date_details": {\n "year": "2017",\n "month": "09",\n "day": "21",\n "hour": "08",\n "minutes": "00",\n "seconds": "00"\n },\n "utc_end_date": "2017-09-21 17:00:00",\n "utc_end_date_details": {\n "year": "2017",\n "month": "09",\n "day": "21",\n "hour": "17",\n "minutes": "00",\n "seconds": "00"\n },\n "timezone": "UTC+0",\n "timezone_abbr": "",\n "cost": "$5",\n "cost_details": {\n "currency_symbol": "$",\n "currency_position": "prefix",\n "values": ["5"]\n },\n "website": "http:\/\/raccoons-ate-my-neighbour.com",\n "show_map": false,\n "show_map_link": false,\n "hide_from_listings": false,\n "sticky": false,\n "featured": false,\n "categories": [{\n "name": "rest-stuff",\n "slug": "rest-stuff",\n "term_group": 0,\n "term_taxonomy_id": 2,\n "taxonomy": "tribe_events_cat",\n "description": "",\n "parent": 0,\n "count": 1,\n "filter": "raw",\n "id": 2,\n "urls": {\n "self": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/categories\/2",\n "collection": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/categories"\n }\n }],\n "tags": [{\n "name": "example",\n "slug": "example",\n "term_group": 0,\n "term_taxonomy_id": 3,\n "taxonomy": "post_tag",\n "description": "",\n "parent": 0,\n "count": 1,\n "filter": "raw",\n "id": 3,\n "urls": {\n "self": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/tags\/3",\n "collection": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/tags"\n }\n }, {\n "name": "raccoon",\n "slug": "raccoon",\n "term_group": 0,\n "term_taxonomy_id": 4,\n "taxonomy": "post_tag",\n "description": "",\n "parent": 0,\n "count": 1,\n "filter": "raw",\n "id": 4,\n "urls": {\n "self": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/tags\/4",\n "collection": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/tags"\n }\n }],\n "venue": {\n "id": 10,\n "author": "1",\n "status": "publish",\n "date": "2017-09-21 12:00:59",\n "date_utc": "2017-09-21 12:00:59",\n "modified": "2017-09-21 12:00:59",\n "modified_utc": "2017-09-21 12:00:59",\n "url": "http:\/\/tribe.localhost\/venue\/raccoon-org\/",\n "venue": "raccoon Org",\n "description": "Venue Description",\n "address": "123, raccoon Ave.",\n "city": "Raccon City",\n "country": "United States",\n "province": "raccoon County",\n "state": "NH",\n "zip": "12345",\n "phone": "+112341234",\n "website": "http:\/\/raccoons.org",\n "stateprovince": "NH",\n "show_map": true,\n "show_map_link": true,\n "global_id": "tribe.localhost?id=10",\n "global_id_lineage": ["tribe.localhost?id=10"]\n },\n "organizer": [{\n "id": 11,\n "author": "1",\n "status": "publish",\n "date": "2017-09-21 12:01:48",\n "date_utc": "2017-09-21 12:01:48",\n "modified": "2017-09-21 12:01:48",\n "modified_utc": "2017-09-21 12:01:48",\n "url": "http:\/\/tribe.localhost\/organizer\/a-first-raccoon\/",\n "organizer": "A first raccoon",\n "description": "Shy but packing a lot of punch.",\n "phone": "+1233434234",\n "website": "http:\/\/first-raccoon.com",\n "email": "first@raccoon.com",\n "global_id": "tribe.localhost?id=11",\n "global_id_lineage": ["tribe.localhost?id=11"]\n }, {\n "id": 12,\n "author": "1",\n "status": "publish",\n "date": "2017-09-21 12:02:43",\n "date_utc": "2017-09-21 12:02:43",\n "modified": "2017-09-21 12:02:43",\n "modified_utc": "2017-09-21 12:02:43",\n "url": "http:\/\/tribe.localhost\/organizer\/a-second-raccoon\/",\n "organizer": "A second raccoon",\n "description": "Gentle and deadly.",\n "phone": "+134473847",\n "website": "http:\/\/raccoon-for-me.com",\n "email": "racc00n@raccoon.for-me.com",\n "global_id": "tribe.localhost?id=12",\n "global_id_lineage": ["tribe.localhost?id=12"]\n }]\n }],\n "rest_url": "http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/events\/?page=1&per_page=10&start_date=2017-09-21 01:59:00&end_date=2019-09-21 13:06:27",\n "total": 1,\n "total_pages": 1\n}\n\n<\/pre><\/div>\n\n\n\n
The word “query” should sound familiar to WordPress developers, and that’s because many of the WordPress and The Events Calendar REST API parameters share a name with those used in a WP_Query<\/samp><\/a> object. Some of those parameters will be set to a default value by the REST API, and that explains why the rest_url<\/samp> in the data does not look exactly like the one we typed.<\/p>\n\n\n\n
It’s sufficient to pass the event post ID as a path parameter in the URL, like this:<\/p>\n\n\n\nGET http:\/\/tribe.localhost\/wp-json\/tribe\/events\/v1\/events\/6\n<\/pre><\/div>\n\n\n
\n{\n "id": 6,\n "author": "1",\n "title": "REST Event 1",\n "description": "Example content" \n}\n\n<\/pre><\/div>\n\n\nModifying the response<\/h2>\n\n\n\n
As WordPress developers managing a site dedicated to victims of scams perpetrated by raccoons, we might provide an educated guess about how much an event “looks suspicious” to us. We do that by allowing the site editors to set a _raccoon_suspect_level<\/samp> custom field (aka “meta field”) value ranging from 1<\/samp> to 5<\/samp>. As the good and honest developers that we are, we want that value to show up in the REST API response: we can use the tribe_rest_single_event_data<\/samp> filter to do exactly that.<\/p>\n\n\n\n\nadd_filter( 'tribe_rest_single_event_data', 'raccoon_add_suspect_level' );\n\nfunction raccoon_add_suspect_level( array $event_data ) {\n $event_id = $event_data['id'];\n\n $level = get_post_meta( $event_id, '_raccoon_suspect_level', true );\n\n if ( empty( $level ) ) {\n \/\/ let's be wary...\n $level = '4';\n }\n\n $event_data['raccoon_supect_level'] = $level;\n\n return $event_data;\n}\n\n<\/pre><\/div>\n\n\n\n{\n "id": 6,\n "author": "1",\n "status": "publish",\n "title": "REST Event 1",\n "raccoon_supect_level": "5",\n description: "Example content ",\n "json_ld": {\n "@context ": "http: \/\/schema.org",\n "@type": "Event",\n "name": "REST Event 1",\n "raccoon_supect_level": "1",\n "description": "Example content ",\n "image ": "http: \/\/tribe.localhost\/wp-content\/uploads\/2017\/09\/raccoon.jpg",\n "url": "http:\/\/tribe.localhost\/event\/example-event-1\/",\n "startDate": "2017-09-21 08:00:00",\n "endDate": "2017-09-21 17:00:00",\n "location": {\n "@type": "Place",\n "name": "raccoon Org",\n "description": "Venue Description",\n "url": false,\n "address": {\n "@type": "PostalAddress",\n "streetAddress": "123, raccoon Ave.",\n "addressLocality": "Raccoon City",\n "addressRegion": "NH",\n "postalCode": "12345",\n "addressCountry": "United States"\n },\n "telephone": "+112341234",\n "sameAs": "http:\/\/raccoons.org"\n },\n "organizer": {\n "@type": "Person",\n "name": "A first raccoon",\n "description": "Shy but packing a lot of punch.",\n "url": false,\n "telephone": "+1233434234",\n "email": "one@first-raccoon.com",\n "sameAs": "http:\/\/first-raccoon.com"\n },\n "offers": {\n "@type": "Offer",\n "price": "5",\n "url": "http:\/\/tribe.localhost\/event\/example-event-1\/"\n }\n },\n "raccoon_supect_level": "5"\n}\n\n<\/pre><\/div>\n\n\n
We haven’t shown it before, but, when grabbing a single event, the REST API will also provide the JSON LD data<\/a> for the event. Again. Information. A lot<\/em> of it.
But what if you don’t need that piece of information and would like to remove it from the response?
The same principle applies–filter the response data and remove it.<\/p>\n\n\n\nadd_filter( 'tribe_rest_single_event_data', 'raccoon_remove_json_ld_data' );\n\nfunction raccoon_remove_json_ld_data( array $event_data ) {\n unset( $event_data['json_ld'] );\n\n return $event_data;\n}\n<\/pre><\/div>\n\n\nA living Swagger.io documentation<\/h2>\n\n\n\n
\n{\n "swagger": "2.0",\n "info": {\n "version": "1.0.0",\n "title": "The Events Calendar REST API",\n "description": "The Events Calendar REST API allows accessing upcoming events information easily and conveniently."\n },\n "host": "tribe.localhost",\n "basePath": "\/wp-json\/tribe\/events\/v1\/",\n "schemes": [\n "http"\n ],\n "consumes": [\n "application\/json"\n ],\n "produces": [\n "application\/json"\n ],\n "paths": {\n "\/doc": {\n "get": {\n "responses": {\n "200": {\n "description": "Returns the documentation for The Events Calendar REST API in Swagger consumable format."\n }\n }\n }\n },\n "\/events": {\n "get": {\n "parameters": [\n {\n "in": "query",\n "type": "integer",\n "description": "The archive page to return",\n "required": false,\n "default": 1,\n "name": "page"\n },\n {\n "in": "query",\n "type": "integer",\n "description": "The number of events to return on each page",\n "required": false,\n "default": "10",\n "name": "per_page"\n },\n }\n }\n }\n }\n}\n<\/pre><\/div>\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-output-665x408.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-output-2-665x408.png\")
<\/figure>\n\n\n\n\n
\nadd_filter( 'tribe_rest_swagger_event_documentation', 'raccoon_document_suspect_level' );\n\nfunction raccoon_document_suspect_level( array $documentation ) {\n $documentation['properties']['raccoon_suspect_level'] = array(\n 'type' => 'integer',\n 'description' => __( 'How much the event looks like a raccoon scam in a 1 to 5 range', 'raccoon' ),\n );\n\n return $documentation;\n}\n<\/pre><\/div>\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/racoon-documentation-665x408.png\")
<\/figure>\n\n\n\nA JavaScript example of authentication<\/h2>\n\n\n\n
![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/visitor-events-1.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/admin-events-665x408.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/deleting-events-no.gif\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/deleting-event-ok.gif\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-io-editor-landing-665x408.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-io-editor-paste-665x409.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-io-editor-generate-665x409.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2017\/09\/swagger-io-editor-generation-gif.gif\")
<\/figure>\n\n\n\n