Professional Web API with Flask

Course Content

Professional Web API with Flask

Professional Web API with Flask

1. Introduction to the Course

Course Outline About API About REST API Project Description Project Initialization Environment Configuration and Dependency Management Establish SSH Connection to GitHub

2. Database and Models

SQLAlchemy Set Up Create Models Many-to-One Relationship One-to-One Relationship Many-to-Many Relationship

3. Flask-Smorest and Schemas

Introduction to Flask-Smorest Introduction to Marshmallow JSON Explanation Schema Handling with Marshmallow

4. Endpoints with Blueprints and MethodView

Blueprints and MethodView Overview Start with Blueprints and MethodViews First Endpoint, Flask-Migration and SQLite Studio Postman and Insomnia Team Endpoints User and Player Endpoints Swagger UI

5. Authentication with JWT

What is JWT?Flask-JWT-Extended Set Up User Registration Login Endpoint JWT Required Permissions Logout Endpoint Testing New Endpoints

6. Deployment

Enhancing Your App Last Git Push

Testing New Endpoints

Please watch the video to swiftly and efficiently learn how to utilize access tokens in tools such as Postman, Insomnia, and Swagger, enhancing your professional toolkit.

Note

Please remove the access token from ModHeader at the end, or you won't be able to navigate other sites in the same browser window.

The link lets you compare your code with the project's code on GitHub.

1. What is the correct format for including an authorization token in the request header?

2. What is the expected outcome after successfully sending a logout request?

3. Why is the POST method recommended for logout requests instead of GET?

What is the correct format for including an authorization token in the request header?

Select the correct answer

Authorization: Basic [token]

Authorization: Token [token]

Authorization: Bearer [token]

Authorization: OAuth [token]

What is the expected outcome after successfully sending a logout request?

Select the correct answer

The user's account is deleted.

The user's session is terminated.

The user's password is reset.

The user's role is changed to guest.

Why is the POST method recommended for logout requests instead of GET?

Select the correct answer

To align with RESTful practices.

Because logout actions modify server state by invalidating the session.

GET requests cannot carry headers.

POST requests are faster than GET requests.

Everything was clear?

How can we improve it?

Thanks for your feedback!

Section 5. Chapter 8

We're sorry to hear that something went wrong. What happened?

some-alt