# LINE Login development guidelines
When developing web apps using LINE Login, follow these development guidelines.
Prohibited matters
Required matters
Recommended matters
The basic rules for LINE Login development are based on the content described in Terms and Policies.
# Prohibited matters
# Prohibiting mass requests to the LINE Platform
Don't send a large number of authorization requests or LINE Login API requests to the LINE Platform for load testing purposes. For load testing web apps, prepare a test environment that doesn't generate a large number of requests to the LINE Platform.
If the rate limit is exceeded, 429 Too Many Requests will be returned and an error will occur.
# Required matters
# Deauthorize your app when a user unregisters from your app
When a user unregisters from your app (website, smartphone app, etc.) that integrates LINE Login, or when a user terminates the link between your app and the LINE app, you must do the following:
- The permissions that the user has granted to the authorized app must be deauthorized using the Deauthorize your app to which the user has granted permissions endpoint on behalf of the user.
- Write what happens when a user unregisters from your app or terminates the link between your app and the LINE app as follows near the function or in the terms and conditions that the user agrees to at the time of registration or authorization.
- e.g. If you unsubscribe from the service, LY Corporation will be notified that you have unsubscribed and the link between the service and LINE app will be terminated.
- e.g. If you do this, LY Corporation will be notified and the link between the service and LINE app will be terminated.
The following use cases require deauthorization.
When a user logs in to the app that integrates LINE Login with their LINE account and authorize the app on the channel consent screen, the target app will appear in Settings > Account > Authorized apps in the LINE app. Deauthorize the app so that the permissions don't remain authorized after the user unregisters from your app.
For more information about how a user can deauthorize the permissions that the user has granted to the app, see Managing authorized apps in the LINE Login documentation.
# Recommended matters
# Saving logs
We recommend saving logs for Authorization requests and LINE Login API requests for a certain period of time so that developers themselves can smoothly investigate the cause and scope of a problem when it occurs.
# Authorization request logs
We recommend saving the following information as a log when making an Authorization request.
- Time when authorization request was made
- Parameter of the authorization request
More specifically, save it in a log file using the following format.
| Time when authorization request was made | Parameter of the authorization request |
|---|---|
| Mon, 16 Jul 2021 10:20:10 GMT | https://access.line.me/oauth2/v2.1/authorize?response_type=code&client_id=xxxxxxxxxx... |
# Authorization code or error response
We recommend saving the following information as a log when you receive an Authorization code or an Error response through an Authorization request.
- Time when the authorization code or error response was received
- Request method
- Log of authorization codes or error responses
More specifically, save it in a log file using the following format.
| Time when response was received | Request Method | Log of authorization codes or error responses |
|---|---|---|
| Mon, 16 Jul 2021 10:20:20 GMT | GET | /callback?code=Zfl2WjsWcn2XBBWApcty&state=n5B9b9FR2BWjloDzEskZMmGysITRTYpjLkM6oD5qfmA |
# Time logs for LINE Login API request
We recommend saving the following information as a log when making a LINE Login API request.
- Request ID (
x-line-request-id) of the Response headers - Time when API request was made
- Request method
- API endpoint
- Status codes returned by the LINE Platform
More specifically, save it in a log file using the following format.
Request ID (x-line-request-id) | Time when API request was made | Request method | API endpoint | Status code |
|---|---|---|---|---|
| 8d48c8577e739b9c | Mon, 16 Jul 2021 10:20:22 GMT | POST | https://api.line.me/oauth2/v2.1/token | 200 |
Depending on the requirements of the web app you're running, the following information, in addition to the above, can be stored for investigation when problems occur.
- LINE Login API request body
- Response body returned by the LINE Platform after the API request
We don't provide logs of authorization requests or logs of LINE Login API requests, etc. despite inquiries. Logs should be saved by the developers who are developing web apps using LINE Login.