The Complete Strapi™ Course with Plugins and Deployment - API Tokens

The video tutorial explains the concept of API tokens in Strapi, focusing on manually generating tokens for third-party access. It covers the differences between application users and third-party services, emphasizing the need for manual token generation for external services. The process of making authenticated requests using these tokens is also discussed, highlighting the similarities with previous lessons.

What is the primary purpose of API tokens in Strapi?

• To manage user roles

• To improve database performance

• To allow authenticated access to the API

• To enhance the user interface

How can API tokens be generated in Strapi?

• Automatically through user registration

• Through a third-party application

• By sending a request to the API

• Manually by the administrator

In a microservice architecture, why might you need to manually generate an API token?

• To enhance the security of the application

• To reduce the number of API calls

• To improve the speed of the application

• To allow a third-party service to access application state

What must an external service include in every request to make an authenticated request?

• A session cookie

• A user ID

• An API endpoint

• A JWT token

What is a key difference between manually generated tokens and automatically generated tokens?

• Manually generated tokens are for third-party services

• Automatically generated tokens are for individual users

• Manually generated tokens are more secure

• Automatically generated tokens require admin approval