Hmm. The log you provided doesn't give much information. I only see one word ETIMEDOUT which means that the connection can't be established or the server ...
- 0
Post : 04/02/2021
I think there is no support for that in Messaging API right now. But there is an alternative way to acomplish this. You can use LIFFv2 app to get the OS of ...
- 0
Post : 22/01/2021
I understand the problem you are facing is the account created from LINE Manager don't appear in the LINE Developer site for con...
- 0
Post : 14/01/2021
Another solution. since the user can still move the pin to send the location in the Location Action. You can also use the LIFF App and use the [...
- 1
Post : 28/12/2020
Let answer this one by one. 1. if there is a way for each user who receives the message in the API, not the developer, to find out the user ID for them...
- 1
Post : 28/12/2020
Right now, There is no supported API that open for LINE OpenChat. and I strongly not recommend to use any 3rd party tools that use your personal acc...
- 1
Post : 28/12/2020
There are a few ways to get LINE userId without using the webhook in Messaging API
1) Retrieve it from LINE Login
2) Retrieve it from `LIFF ...
- 3
Post : 09/12/2020
I think there is no problem with your payload. In most cases I experienced that can cause the 400 status code and got the reply message **"Bad Request"*...
- 0
Post : 07/10/2020
You can't block them from adding your chatbot as a friend. But good news, You can fillter the incoming request from your webhook.
Example from your requ...
- 0
Post : 20/07/2020
Unfortunately, There is no API that can convert the actual user's LINE ID to userId. All of LINE API opened to developer use the userId to identify th...
- 1
Post : 20/07/2020