# Channel access tokens

This article explains what channel access tokens are and the different types that we provide.

# What are channel access tokens?

Access tokens are objects that contain security credentials that are used in a token-based authentication process. It allows an app to call an API.

Channel access tokens are access tokens that are used for the Messaging API. LINE supports 3 types of channel access tokens:

Maximum number of channel access tokens to be issued

Short-lived channel access token, long-lived channel access token, and a channel access token in which the user can specify the expiration (Channel access token v2.1) each have their own maximum number that can be issued. The number of channel access tokens issued for each channel access token does not affect the number of other types of channel access tokens that can be issued.

  • Short-lived channel access token: Up to 30 tokens per channel
  • Long-lived channel access token: Up to 1 token per channel
  • A channel access token in which the user can specify the expiration (Channel access token v2.1) : Up to 30 tokens per channel

Until the end of May 2020, the maximum number of channel access tokens that could be issued had been shared among all types.

# Short-lived channel access token

A short-lived channel access token is an access token for the Messaging API that is valid for 30 days.

Learn how to Issue a short-lived channel access token in the Messaging API reference.

Note

You do not need to use short-lived channel access tokens that are issued using the /v2/oauth/accessToken endpoint. Instead you can use a long-lived channel access token.

# Long-lived channel access token

A long-lived channel access token is an access token for the Messaging API that has no expiration date.

You can issue a long-lived channel access token from the Messaging API tab by selecting a channel from the Channels in the LINE Developers Console.

You can reissue a long-lived channel access token at any time. When you do, the current token becomes invalid. If you need extra time to update the access token in your app, you can delay the time the current access token becomes invalid by up to 24 hours.

# User-specified expiration (Channel access token v2.1)

Channel access tokens v2.1 lets developers specify the expiration date and provides additional security benefits by using a JSON Web Token (JWT) instead of a channel secret. We recommend using this version.

Learn how to Issue a channel access token v2.1 in the Message API documentation.