- A basic understanding of REST APIs
- Experience with JSON or XML formats
- Object-orientated programming experience
Audience
- Back-end Developers
Swagger is an open source framework of tools that use Open API Specification (OAS) files for building, designing, documenting, and consuming RESTful web services.
This instructor-led, live training (online or onsite) is aimed at back-end developers who wish to use Swagger to build, design, document, and consume RESTful web services.
By the end of this training, participants will be able to:
- Create an API management strategy for software infrastructure.
- Use Swagger tools to edit OAS files and create SDKs.
- Implement API security, versioning, documentation, and other important features.
Format of the Course
- Interactive lecture and discussion.
- Lots of exercises and practice.
- Hands-on implementation in a live-lab environment.
Course Customization Options
- To request a customized training for this course, please contact us to arrange.
Introduction
API Definition
- Definition file
- API request
YAML
- What is YAML
- Rules of YAML
Overview of RESTful Services
- Resoures
- State transfer
- Representation sate
Preparing the Development Environment
- Installing and configuring Swagger
- Installing and configuring Node.Js
REST Web Service Constraint Architecture
- Using the client-server constraint
- Working with uniform interface constraints
- Working with the statelessness constraint
- Using HTTP-caching
- Enabling a layer system
REST API Designing
- Implementing CRUD operations
- Using Error Handling
- Implementing operations for REST APIs
- Handling changes in API
- Versioning API
- Caching API
- Supporting pagination and partial responses
Specifications using Swagger
- Editing documents with Swagger
- Creating specifications in YAML format
- Creating paths and observations
- Adding documentation
- Adding schemas to an OAS file
- Using SwaggerHub
API Management
- Creating an API management strategy
- Managing the API life cycle
- Generating API proxies
- Controling the behavior of API
- Building an API portal
- Providing traffic management
API Security
- Securing with tokens and JWT
- Securing with API key and secret
- Authorizing using OAuth2.0
Summary and Conclusion
United Arab Emirates - Swagger and the OpenAPI Specification
Qatar - Swagger and the OpenAPI Specification
Egypt - Swagger and the OpenAPI Specification
Saudi Arabia - Swagger and the OpenAPI Specification
South Africa - Swagger and the OpenAPI Specification
Brasil - Swagger and the OpenAPI Specification
Canada - Swagger and the OpenAPI Specification
中国 - Swagger and the OpenAPI Specification
香港 - Swagger and the OpenAPI Specification
澳門 - Swagger and the OpenAPI Specification
台灣 - Swagger and the OpenAPI Specification
USA - Swagger and the OpenAPI Specification
Österreich - Swagger and the OpenAPI Specification
Schweiz - Swagger and the OpenAPI Specification
Deutschland - Swagger and the OpenAPI Specification
Czech Republic - Swagger and the OpenAPI Specification
Denmark - Swagger and the OpenAPI Specification
Estonia - Swagger and the OpenAPI Specification
Finland - Swagger and the OpenAPI Specification
Greece - Swagger and the OpenAPI Specification
Magyarország - Swagger and the OpenAPI Specification
Ireland - Swagger and the OpenAPI Specification
Luxembourg - Swagger and the OpenAPI Specification
Latvia - Swagger and the OpenAPI Specification
España - Swagger and the OpenAPI Specification
Italia - Swagger and the OpenAPI Specification
Lithuania - Swagger and the OpenAPI Specification
Nederland - Swagger and the OpenAPI Specification
Norway - Swagger and the OpenAPI Specification
Portugal - Swagger and the OpenAPI Specification
România - Swagger and the OpenAPI Specification
Sverige - Swagger and the OpenAPI Specification
Türkiye - Swagger and the OpenAPI Specification
Malta - Swagger and the OpenAPI Specification
Belgique - Swagger and the OpenAPI Specification
France - Swagger and the OpenAPI Specification
日本 - Swagger and the OpenAPI Specification
Australia - Swagger and the OpenAPI Specification
Malaysia - Swagger and the OpenAPI Specification
New Zealand - Swagger and the OpenAPI Specification
Philippines - Swagger and the OpenAPI Specification
Singapore - Swagger and the OpenAPI Specification
Thailand - Swagger and the OpenAPI Specification
Vietnam - Swagger and the OpenAPI Specification
India - Swagger and the OpenAPI Specification
Argentina - Swagger and the OpenAPI Specification
Chile - Swagger and the OpenAPI Specification
Costa Rica - Swagger and the OpenAPI Specification
Ecuador - Swagger and the OpenAPI Specification
Guatemala - Swagger and the OpenAPI Specification
Colombia - Swagger and the OpenAPI Specification
México - Swagger and the OpenAPI Specification
Panama - Swagger and the OpenAPI Specification
Peru - Swagger and the OpenAPI Specification
Uruguay - Swagger and the OpenAPI Specification
Venezuela - Swagger and the OpenAPI Specification
Polska - Swagger and the OpenAPI Specification
United Kingdom - Swagger and the OpenAPI Specification
South Korea - Swagger and the OpenAPI Specification
Pakistan - Swagger and the OpenAPI Specification
Sri Lanka - Swagger and the OpenAPI Specification
Bulgaria - Swagger and the OpenAPI Specification
Bolivia - Swagger and the OpenAPI Specification
Indonesia - Swagger and the OpenAPI Specification
Kazakhstan - Swagger and the OpenAPI Specification
Moldova - Swagger and the OpenAPI Specification
Morocco - Swagger and the OpenAPI Specification
Tunisia - Swagger and the OpenAPI Specification
Kuwait - Swagger and the OpenAPI Specification
Oman - Swagger and the OpenAPI Specification
Slovakia - Swagger and the OpenAPI Specification
Kenya - Swagger and the OpenAPI Specification
Nigeria - Swagger and the OpenAPI Specification
Botswana - Swagger and the OpenAPI Specification
Slovenia - Swagger and the OpenAPI Specification
Croatia - Swagger and the OpenAPI Specification
Serbia - Swagger and the OpenAPI Specification
Bhutan - Swagger and the OpenAPI Specification