NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #2548 most downloaded on Packagist
SDK of the LINE BOT API for PHP
Latest stable
v12.9.0
Last release 26 days ago
27 Oct 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
106 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- PR-START https://github.com/line/line-openapi/pull/133 -->
Update the OpenAPI schema to support URI action URLs up to 10,000 characters.
maxLength: 10000 to URIAction.uri.AltUri.desktop.maxLength from 1,000 to 10,000.For more details, please refer to the release note: https://developers.line.biz/en/news/2026/10/27/uri-action/
(original PR is https://github.com/line/line-openapi/pull/133)
<!-- PR-END https://github.com/line/line-openapi/pull/133 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.8.0...v12.9.0
This release is prepared by @habara-k
Update the OpenAPI schema to support URI action URLs up to 10,000 characters.
maxLength: 10000 to URIAction.uri.AltUri.desktop.maxLength from 1,000 to 10,000.For more details, please refer to the release note: https://developers.line.biz/en/news/2026/10/27/uri-action/
(original PR is line/line-openapi#133)
Full Changelog: v12.8.0...v12.9.0
This release is prepared by @habara-k
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This version adds the templated LINE notification message (PNP) API, and lets you assign a custom aggregation unit (CAU) to LINE notification messages
This version adds the templated LINE notification message (PNP) API, and lets you assign a custom aggregation unit (CAU) to LINE notification messages.
Schema changes: https://github.com/line/line-openapi/pull/131
templateKey and substituting values into the template's emphasizedItem, items, and buttons. New endpoint: POST /v2/bot/message/pnp/templated/push.GET /v2/bot/message/delivery/pnp/templated.customAggregationUnits, so their delivery can be aggregated per unit with the existing unit-based statistics APIs.This is a partner-only feature that requires an application. For more details, see:
use LINE\Clients\MessagingApi\Api\MessagingApiApi;
use LINE\Clients\MessagingApi\Configuration;
use LINE\Clients\MessagingApi\Model\PnpTemplatedMessageRequest;
use LINE\Clients\MessagingApi\Model\PnpTemplatedMessageBody;
use LINE\Clients\MessagingApi\Model\PnpTemplatedEmphasizedItem;
use LINE\Clients\MessagingApi\Model\PnpTemplatedItem;
use LINE\Clients\MessagingApi\Model\PnpTemplatedButton;
$config = new Configuration();
$config->setAccessToken('YOUR_CHANNEL_ACCESS_TOKEN');
$messagingApi = new MessagingApiApi(client: new \GuzzleHttp\Client(), config: $config);
$request = new PnpTemplatedMessageRequest([
// Phone number normalized to E.164 and hashed with SHA256
'to' => '0123...hashed_phone_number...cdef',
'templateKey' => 'order_confirmation',
'body' => new PnpTemplatedMessageBody([
'emphasizedItem' => new PnpTemplatedEmphasizedItem(['itemKey' => 'amount', 'content' => '$42.00']),
'items' => [
new PnpTemplatedItem(['itemKey' => 'order_id', 'content' => 'A1234567']),
new PnpTemplatedItem(['itemKey' => 'shop_name', 'content' => 'LINE Store']),
],
'buttons' => [
new PnpTemplatedButton(['buttonKey' => 'detail', 'url' => 'https://example.com/orders/A1234567']),
],
]),
'customAggregationUnits' => ['promotion_a'],
]);
// The second argument is the X-Line-Delivery-Tag (16-100 chars),
// which is returned in the delivery completion webhook.
$messagingApi->pushTemplatedMessagesByPhone($request, 'order-A1234567-0001');
use LINE\Clients\MessagingApi\Api\MessagingApiApi;
use LINE\Clients\MessagingApi\Configuration;
$config = new Configuration();
$config->setAccessToken('YOUR_CHANNEL_ACCESS_TOKEN');
$messagingApi = new MessagingApiApi(client: new \GuzzleHttp\Client(), config: $config);
// GET /v2/bot/message/delivery/pnp/templated (date: yyyyMMdd, UTC+9)
$response = $messagingApi->getPNPTemplatedMessageStatistics('20240916');
echo $response->getStatus() . PHP_EOL; // ready / unready / unavailable_for_privacy / out_of_service
if ($response->getStatus() === 'ready') {
echo $response->getSuccess() . PHP_EOL;
}
<!-- Release notes generated using configuration in .github/release.yml at master -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.7.0...v12.8.0
This release is prepared by @mokuzon
This version adds the templated LINE notification message (PNP) API, and lets you assign a custom aggregation unit (CAU) to LINE notification messages.
Schema changes: line/line-openapi#131
templateKey and substituting values into the template's emphasizedItem, items, and buttons. New endpoint: POST /v2/bot/message/pnp/templated/push.GET /v2/bot/message/delivery/pnp/templated.customAggregationUnits, so their delivery can be aggregated per unit with the existing unit-based statistics APIs.This is a partner-only feature that requires an application. For more details, see:
use LINE\Clients\MessagingApi\Api\MessagingApiApi;
use LINE\Clients\MessagingApi\Configuration;
use LINE\Clients\MessagingApi\Model\PnpTemplatedMessageRequest;
use LINE\Clients\MessagingApi\Model\PnpTemplatedMessageBody;
use LINE\Clients\MessagingApi\Model\PnpTemplatedEmphasizedItem;
use LINE\Clients\MessagingApi\Model\PnpTemplatedItem;
use LINE\Clients\MessagingApi\Model\PnpTemplatedButton;
$config = new Configuration();
$config->setAccessToken('YOUR_CHANNEL_ACCESS_TOKEN');
$messagingApi = new MessagingApiApi(client: new \GuzzleHttp\Client(), config: $config);
$request = new PnpTemplatedMessageRequest([
// Phone number normalized to E.164 and hashed with SHA256
'to' => '0123...hashed_phone_number...cdef',
'templateKey' => 'order_confirmation',
'body' => new PnpTemplatedMessageBody([
'emphasizedItem' => new PnpTemplatedEmphasizedItem(['itemKey' => 'amount', 'content' => '$42.00']),
'items' => [
new PnpTemplatedItem(['itemKey' => 'order_id', 'content' => 'A1234567']),
new PnpTemplatedItem(['itemKey' => 'shop_name', 'content' => 'LINE Store']),
],
'buttons' => [
new PnpTemplatedButton(['buttonKey' => 'detail', 'url' => 'https://example.com/orders/A1234567']),
],
]),
'customAggregationUnits' => ['promotion_a'],
]);
// The second argument is the X-Line-Delivery-Tag (16-100 chars),
// which is returned in the delivery completion webhook.
$messagingApi->pushTemplatedMessagesByPhone($request, 'order-A1234567-0001');use LINE\Clients\MessagingApi\Api\MessagingApiApi;
use LINE\Clients\MessagingApi\Configuration;
$config = new Configuration();
$config->setAccessToken('YOUR_CHANNEL_ACCESS_TOKEN');
$messagingApi = new MessagingApiApi(client: new \GuzzleHttp\Client(), config: $config);
// GET /v2/bot/message/delivery/pnp/templated (date: yyyyMMdd, UTC+9)
$response = $messagingApi->getPNPTemplatedMessageStatistics('20240916');
echo $response->getStatus() . PHP_EOL; // ready / unready / unavailable_for_privacy / out_of_service
if ($response->getStatus() === 'ready') {
echo $response->getSuccess() . PHP_EOL;
}Full Changelog: v12.7.0...v12.8.0
This release is prepared by @mokuzon
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Add MessageEditedEvent webhook event to support the message editing feature.
When a user edits a message in a group that includes a LINE Official Account, a webhook event with type=messageEdited is sent.
messageEdited webhook events may arrive out of order. The event with the largest timestamp represents the latest edit state.Please also refer to the document: https://developers.line.biz/en/reference/messaging-api/#edit-event
(original PR is https://github.com/line/line-openapi/pull/129)
<!-- PR-END https://github.com/line/line-openapi/pull/129 -->
use LINE\Webhook\Model\MessageEditedEvent;
use LINE\Webhook\Model\TextMessageContent;
foreach ($parsedEvents->getEvents() as $event) {
if ($event instanceof MessageEditedEvent
&& $event->getMessage() instanceof TextMessageContent
) {
echo "Message {$event->getMessage()->getId()} was edited to: {$event->getMessage()->getText()}";
}
}
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.6.0...v12.7.0
This release is prepared by @habara-k
Add MessageEditedEvent webhook event to support the message editing feature.
When a user edits a message in a group that includes a LINE Official Account, a webhook event with type=messageEdited is sent.
messageEdited webhook events may arrive out of order. The event with the largest timestamp represents the latest edit state.Please also refer to the document: https://developers.line.biz/en/reference/messaging-api/#edit-event
(original PR is line/line-openapi#129)
use LINE\Webhook\Model\MessageEditedEvent;
use LINE\Webhook\Model\TextMessageContent;
foreach ($parsedEvents->getEvents() as $event) {
if ($event instanceof MessageEditedEvent
&& $event->getMessage() instanceof TextMessageContent
) {
echo "Message {$event->getMessage()->getId()} was edited to: {$event->getMessage()->getText()}";
}
}Full Changelog: v12.6.0...v12.7.0
This release is prepared by @habara-k
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
This release supports the new Rich Menu inshgit APIs. For details on the API, please see below.
AudienceGroupFailedType emum by @github-actions[bot] in https://github.com/line/line-bot-sdk-php/pull/857Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.5.0...v12.6.0
This release is prepared by @mokuzon
This release supports the new Rich Menu inshgit APIs.
For details on the API, please see below.
AudienceGroupFailedType emum by @github-actions[bot] in #857Full Changelog: v12.5.0...v12.6.0
This release is prepared by @mokuzon
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
This release adds wrapper methods for ChannelAccessTokenApi#issueStatelessChannelToken, making stateless channel access token issuance simpler for both JWT assertion and client secret authentication. The original method accepts all parameters for two different authentication patterns, making it unclear which to pass for each pattern. These wrappers make the distinction explicit through their names and signatures.
- $token = $client->issueStatelessChannelToken(
- grantType: 'client_credentials',
- clientAssertionType: 'urn:ietf:params:oauth:client-assertion-type:jwt-bearer',
- clientAssertion: $clientAssertion,
- );
+ $token = $client->issueStatelessChannelTokenByJWTAssertion(
+ clientAssertion: $clientAssertion,
+ );
- $token = $client->issueStatelessChannelToken(
- grantType: 'client_credentials',
- clientId: $channelId,
- clientSecret: $channelSecret,
- );
+ $token = $client->issueStatelessChannelTokenByClientSecret(
+ clientId: $channelId,
+ clientSecret: $channelSecret,
+ );
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.4.0...v12.5.0
This release is prepared by @habara-k
This release adds wrapper methods for ChannelAccessTokenApi#issueStatelessChannelToken, making stateless channel access token issuance simpler for both JWT assertion and client secret authentication. The original method accepts all parameters for two different authentication patterns, making it unclear which to pass for each pattern. These wrappers make the distinction explicit through their names and signatures.
- $token = $client->issueStatelessChannelToken(
- grantType: 'client_credentials',
- clientAssertionType: 'urn:ietf:params:oauth:client-assertion-type:jwt-bearer',
- clientAssertion: $clientAssertion,
- );
+ $token = $client->issueStatelessChannelTokenByJWTAssertion(
+ clientAssertion: $clientAssertion,
+ );- $token = $client->issueStatelessChannelToken(
- grantType: 'client_credentials',
- clientId: $channelId,
- clientSecret: $channelSecret,
- );
+ $token = $client->issueStatelessChannelTokenByClientSecret(
+ clientId: $channelId,
+ clientSecret: $channelSecret,
+ );Full Changelog: v12.4.0...v12.5.0
This release is prepared by @habara-k
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
TRACKINGTAG_WEBTRAFFIC to AudienceGroupType EnumWe have supported for the new audience‑group type TRACKINGTAG_WEBTRAFFIC (Tracking Tag Webtraffic audience) to the OpenAPI schema.
Updated AudienceGroupType enumeration
TRACKINGTAG_WEBTRAFFICThis update enables correct identification and handling of audience groups built from Tracking Tag Webtraffric.
For more information, please refer to the links provided above.
(original PR is https://github.com/line/line-openapi/pull/118)
<!-- PR-END https://github.com/line/line-openapi/pull/118 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.3.0...v12.4.0
This release is prepared by @eucyt
TRACKINGTAG_WEBTRAFFIC to AudienceGroupType EnumWe have supported for the new audience‑group type TRACKINGTAG_WEBTRAFFIC (Tracking Tag Webtraffic audience) to the OpenAPI schema.
Updated AudienceGroupType enumeration
TRACKINGTAG_WEBTRAFFICThis update enables correct identification and handling of audience groups built from Tracking Tag Webtraffric.
For more information, please refer to the links provided above.
(original PR is line/line-openapi#118)
Full Changelog: v12.3.0...v12.4.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
We have released a new Mark as Read API that allows developers to mark a user’s messages as read.
Previously, this functionality was available only to partners, but it is now publicly available.
When your server receives a user message via Webhook, the MessageContent will include a new field: markAsReadToken.
By calling the Mark as Read API with this token, all messages in the chat room up to and including that message will be marked as read.
Note: This feature assumes that your service uses the chat feature through Official Account Manager.
If chat is not enabled, messages from users are automatically marked as read, making this API unnecessary.
For more details, please refer to the release note: https://developers.line.biz/en/news/2025/11/05/mark-as-read/
(original PR is https://github.com/line/line-openapi/pull/115)
<!-- PR-END https://github.com/line/line-openapi/pull/115 -->
$bot->markAsReadByToken(new MarkAsReadByTokenRequest([
'markAsReadToken' => $message->markAsReadToken,
]))
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.2.0...v12.3.0
This release is prepared by @habara-k
We have released a new Mark as Read API that allows developers to mark a user’s messages as read.
Previously, this functionality was available only to partners, but it is now publicly available.
When your server receives a user message via Webhook, the MessageContent will include a new field: markAsReadToken.
By calling the Mark as Read API with this token, all messages in the chat room up to and including that message will be marked as read.
Note: This feature assumes that your service uses the chat feature through Official Account Manager.
If chat is not enabled, messages from users are automatically marked as read, making this API unnecessary.
For more details, please refer to the release note: https://developers.line.biz/en/news/2025/11/05/mark-as-read/
(original PR is line/line-openapi#115)
$bot->markAsReadByToken(new MarkAsReadByTokenRequest([
'markAsReadToken' => $message->markAsReadToken,
]))Full Changelog: v12.2.0...v12.3.0
This release is prepared by @habara-k
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Previously, when creating a polymorphic model, you have to set the discriminator value manually each time, even though the value is obvious.
$message = (new TextMessage())
->setType(\LINE\Constants\MessageType::TEXT) // this is redundant.
->setText('hello!');
With this release, the discriminator value will be automatically set in the constructor.
$message = (new TextMessage())
->setText('hello!');
$this->assertEquals('text', $message->getType()); // Passed
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.1.0...v12.2.0
This release is prepared by @eucyt
Previously, when creating a polymorphic model, you have to set the discriminator value manually each time, even though the value is obvious.
$message = (new TextMessage())
->setType(\LINE\Constants\MessageType::TEXT) // this is redundant.
->setText('hello!');With this release, the discriminator value will be automatically set in the constructor.
$message = (new TextMessage())
->setText('hello!');
$this->assertEquals('text', $message->getType()); // PassedFull Changelog: v12.1.0...v12.2.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
We add a new forbidPartialDelivery option to the Narrowcast Limit Object.
When set to true, this option prevents messages from being delivered to only a subset of the target audience. If partial delivery occurs, the narrowcast request will succeed but fail asynchronously. You can verify whether the message delivery was canceled by checking the narrowcast message progress.
This property can only be set to true when upToRemainingQuota is also true.
For more details, see the https://developers.line.biz/en/news/2025/10/21/narrowcast-message-update/.
$bot->narrowcast(new NarrowcastRequest([
'messages' => [
(new TextMessage(['text' => 'Hello']))->setType('text'),
],
'limit' => new Limit([
'max' => 1000,
'upToRemainingQuota' => true,
'forbidPartialDelivery' => true
])
]))
(original PR is https://github.com/line/line-openapi/pull/114)
<!-- PR-END https://github.com/line/line-openapi/pull/114 -->
Previously, when upToRemainingQuota was set to true, messages could be partially delivered if the remaining message quota was smaller than the target audience size.
With the new forbidPartialDelivery option, you can now ensure that such partial deliveries do not occur.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v12.0.0...v12.1.0
This release is prepared by @habara-k
We add a new forbidPartialDelivery option to the Narrowcast Limit Object.
When set to true, this option prevents messages from being delivered to only a subset of the target audience.
If partial delivery occurs, the narrowcast request will succeed but fail asynchronously.
You can verify whether the message delivery was canceled by checking the narrowcast message progress.
This property can only be set to true when upToRemainingQuota is also true.
For more details, see the https://developers.line.biz/en/news/2025/10/21/narrowcast-message-update/.
$bot->narrowcast(new NarrowcastRequest([
'messages' => [
(new TextMessage(['text' => 'Hello']))->setType('text'),
],
'limit' => new Limit([
'max' => 1000,
'upToRemainingQuota' => true,
'forbidPartialDelivery' => true
])
]))(original PR is line/line-openapi#114)
Previously, when upToRemainingQuota was set to true, messages could be partially delivered if the remaining message quota was smaller than the target audience size.
With the new forbidPartialDelivery option, you can now ensure that such partial deliveries do not occur.
Full Changelog: v12.0.0...v12.1.0
This release is prepared by @habara-k
This change introduces polymorphism support in API responses. ⚠️ This includes breaking changes.
<!-- Release notes generated using configuration in .github/release.yml at master -->
This change introduces polymorphism support in API responses. ⚠️ This includes breaking changes.
Polymorphic types in responses were not handled correctly. As a result, all responses were deserialized into the base class, making it impossible to access subclass-specific properties.
$api = new MessagingApiApi($client);
$richMenuListResponse = $api->getRichMenuList();
// Even if type=postback, it becomes an instance of Action, not PostbackAction
$action = $richMenuListResponse->getRichmenus()[0]->getAreas()[0]->getAction();
// Error: Call to undefined method LINE\Clients\MessagingApi\Model\Action::getData()
$data = $action->getData();
// or simply null
$data = $action["data"];
Polymorphic types in responses are now properly supported. Each response is deserialized into the correct subclass, allowing subclass properties to be accessed safely.
This change applies to all API responses, not just this specific endpoint. If your existing code depends on the base class types, you will need to update it accordingly. You can now directly access subclass-specific properties when polymorphism is involved.
When the discriminator is unknown, it is deserialized into the parent class, and no error occurs.
$api = new MessagingApiApi($client);
$richMenuListResponse = $api->getRichMenuList();
// If type=postback, it will now become an instance of PostbackAction
$action = $richMenuListResponse->getRichmenus()[0]->getAreas()[0]->getAction();
// You can now access subclass-specific properties
$data = $action->getData();
$data = $action["data"];
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.4.0...v12.0.0
This release is prepared by @eucyt
This change introduces polymorphism support in API responses.
⚠️ This includes breaking changes.
Polymorphic types in responses were not handled correctly.
As a result, all responses were deserialized into the base class, making it impossible to access subclass-specific properties.
$api = new MessagingApiApi($client);
$richMenuListResponse = $api->getRichMenuList();
// Even if type=postback, it becomes an instance of Action, not PostbackAction
$action = $richMenuListResponse->getRichmenus()[0]->getAreas()[0]->getAction();
// Error: Call to undefined method LINE\Clients\MessagingApi\Model\Action::getData()
$data = $action->getData();
// or simply null
$data = $action["data"];Polymorphic types in responses are now properly supported.
Each response is deserialized into the correct subclass, allowing subclass properties to be accessed safely.
This change applies to all API responses, not just this specific endpoint.
If your existing code depends on the base class types, you will need to update it accordingly.
You can now directly access subclass-specific properties when polymorphism is involved.
When the discriminator is unknown, it is deserialized into the parent class, and no error occurs.
$api = new MessagingApiApi($client);
$richMenuListResponse = $api->getRichMenuList();
// If type=postback, it will now become an instance of PostbackAction
$action = $richMenuListResponse->getRichmenus()[0]->getAreas()[0]->getAction();
// You can now access subclass-specific properties
$data = $action->getData();
$data = $action["data"];Full Changelog: v11.4.0...v12.0.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
With this release, developers can now optionally skip signature verification when parsing incoming webhook requests. This new capability is especially useful in scenarios where the channel secret may change, potentially causing temporary signature mismatches.
Example Usage:
$options = new EventRequestOptions(function () {
return true;
});
$parsedEvents = EventRequestParser::parseEventRequest(
$req->getBody(), $secret, $signature[0], $options
);
When signature verification is skipped, the signatureValidator will not be invoked. This allows webhook requests to be processed even if their signatures do not match the current channel secret used for verification.
This feature is particularly helpful in high-availability systems where avoiding downtime or message loss during configuration updates is critical.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.3.0...v11.4.0
With this release, developers can now optionally skip signature verification when parsing incoming webhook requests. This new capability is especially useful in scenarios where the channel secret may change, potentially causing temporary signature mismatches.
Example Usage:
$options = new EventRequestOptions(function () {
return true;
});
$parsedEvents = EventRequestParser::parseEventRequest(
$req->getBody(), $secret, $signature[0], $options
);When signature verification is skipped, the signatureValidator will not be invoked. This allows webhook requests to be processed even if their signatures do not match the current channel secret used for verification.
This feature is particularly helpful in high-availability systems where avoiding downtime or message loss during configuration updates is critical.
Full Changelog: v11.3.0...v11.4.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- PR-START https://github.com/line/line-openapi/pull/113 -->
We have supported for the new audience‑group type POP_AD_IMP (POP ad impression audience) to the OpenAPI schema.
Updated AudienceGroupType enumeration
POP_AD_IMPThis update enables correct identification and handling of audience groups built from POP ad impressions, a feature that will be released for the Taiwan market.
For more information, please refer to the links provided above.
(original PR is https://github.com/line/line-openapi/pull/113)
<!-- PR-END https://github.com/line/line-openapi/pull/113 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.2.1...v11.3.0
This release is prepared by @eucyt
We have supported for the new audience‑group type POP_AD_IMP (POP ad impression audience) to the OpenAPI schema.
Updated AudienceGroupType enumeration
POP_AD_IMPThis update enables correct identification and handling of audience groups built from POP ad impressions, a feature that will be released for the Taiwan market.
For more information, please refer to the links provided above.
(original PR is line/line-openapi#113)
Full Changelog: v11.2.1...v11.3.0
This release is prepared by @eucyt
2021/03/01
The UI of LIFF apps opened in LINE v11.3.0 will change.
Toast displayed during LIFF-to-LIFF transition will change
LIFF apps will be displayed in a modal window in LINE for iPadOS
Toast displayed during LIFF-to-LIFF transition will change
In LINE v11.3.0, the toast displayed during "LIFF-to-LIFF transitions," where users can transition to another LIFF app without closing the LIFF app opened in the LIFF browser, will change. This change makes it easier for users to identify the destination LIFF app.
The design of the toast differs between Android and iOS. The figure below shows an example of a toast when using an iPhone.
Changes Supported OS LINE v11.2.x and earlier LINE v11.3.0
Message*
iOS
Android Switched to another app. Switched to the {LIFF app name} app. **
Display location iOS only*** Center of screen Bottom of screen
** The {LIFF app name} section displays the app name specified in the LIFF app name section of the LIFF tab in the LINE Developers Console .
*** LINE v11.2.0 and earlier for Android will also display the toast at the bottom of the screen.
For more information about LIFF-to-LIFF transitions, see Opening a LIFF app from another LIFF app in the LIFF documentation.
LIFF apps will be displayed in a modal window in LINE for iPadOS
In LINE v11.3.0, to improve the experience with LIFF apps designed for many portrait modes (portrait display), LIFF apps opened on the iPad will be displayed in a formSheet size (540W x 620H pt) modal window.
Regardless of the Size setting ( Compact , Tall , or Full ) specified in the LIFF tab of the LINE Developers Console , LIFF apps will always be displayed in a formSheet size modal window in LINE v11.3.0 on iPad.
Example of a LIFF app with the screen size set to Compact :
About the screen ratio in landscape mode (landscape view)
formSheet will be displayed in portrait mode screen ratio (540W x 620H pt) even in landscape mode (landscape display).
LIFF
Previous post [Resolved] Notice about service outage for LINE Login Next post [Updated] Replace (Backward compatibility mode) has been removed from the permanent link redirect settings of the LIFF app and LINE MINI App
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
LINE Things has been closed. In this release we removed the following LINE Things related webhook code
ThingsEventThingsContentLinkThingsContentUnlinkThingsContentScenarioResultThingsContentScenarioResultActionResultAs noted in the README, deletions tied to a business shutdown are shipped as a patch version, not a major version. If your code still references any of these code, they will never be emitted again, so you should remove them.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.2.0...v11.2.1
This release is prepared by @Yang-33
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
This release introduces Coupon API support to the Messaging API, enabling developers to create, manage, and deliver coupons directly through bot integrations. These new features mirror capabilities previously only available through the LINE Official Account Manager, offering greater flexibility in automating coupon workflows via the Messaging API.
POST /v2/bot/coupon
Create a new coupon, including metadata such as title, description, validity period, image URLs, acquisition conditions, and reward details (e.g., fixed-amount discounts).
GET /v2/bot/coupon
Retrieve a list of all coupons associated with your bot.
GET /v2/bot/coupon/{couponId}
Fetch detailed metadata of a specific coupon.
PUT /v2/bot/coupon/{couponId}
Mark a coupon as expired.
type=coupon
You can now send coupons directly to users using the Messaging API, similar to sending text, image, or template messages.For detailed usage examples, see the official documentation.
LINE Developers News — Coupon API Released (2025/08/06)
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.1.1...v11.2.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Type for CreateAudienceGroupResponse#expireTimestamp is not float or double, but integer actually. This release fixes type as bugfix.
(original PR is https://github.com/line/line-openapi/pull/106)
<!-- PR-END https://github.com/line/line-openapi/pull/106 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.1.0...v11.1.1
This release is prepared by @Yang-33
Remove deprecated link by @eucyt in https://github.com/line/line-bot-sdk-php/pull/692
<!-- Release notes generated using configuration in .github/release.yml at master -->
Support a new query parameter includesOwnedAudienceGroups to the client.getSharedAudienceGroups (GET /v2/bot/audienceGroup/shared/list). This enhancement allows users to specify whether to include audience groups owned by the user in the response. It is especially useful for users who manage both shared and owned audience groups.
includesOwnedAudienceGroups parameter to the API endpoint.
true: Include audience groups owned by the LINE Official Account Manager.false: Respond only with audience groups shared by Business Manager./v2/bot/audienceGroup/{audienceGroupId}/activate and /v2/bot/audienceGroup/authorityLevel endpoints.For more information, please refer to the links provided above.
(original PR is https://github.com/line/line-openapi/pull/105)
<!-- PR-END https://github.com/line/line-openapi/pull/105 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.0.1...v11.1.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Note this patch is not related to sdk users. This release is just for our test. See https://github.com/line/line-bot-sdk-php/releases/tag/v11.0.0 about new features.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v11.0.0...v11.0.1
This release is prepared by @Yang-33
This release contains breaking changes related to how Webhook events are parsed. Specifically:
This release contains breaking changes related to how Webhook events are parsed. Specifically:
$member["userId"] but $member->getUserId(); is recommended.$parsedEvents = EventRequestParser::parseEventRequest($req->getBody(), $secret, $req->getHeader(HTTPHeader::LINE_SIGNATURE)[0]);
foreach ($parsedEvents->getEvents() as $event) {
if ($event instanceof MemberJoinedEvent) {
$joinedMembers = $event->getJoined()->getMembers();
$joinedMemberIds = array_map(function ($member) {
- return $member["userId"];
+ return $member->getUserId();
}, $joinedMembers);
}
}
message.emojis
message.emojis were defaulted to empty arrays.message.emojis were defaulted to NULL as other array fields. This means if the webhook does not contain emojis, the emojis field in the parsed event will now be NULL instead of an empty array.Please update your application code accordingly to handle these changes.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.3.0...v11.0.0
This release is prepared by @eucyt
We are delighted to announce official support for PHP 8.4. As part of this update, we have addressed changes related to PHP's new deprecations.
We are delighted to announce official support for PHP 8.4. As part of this update, we have addressed changes related to PHP's new deprecations.
Starting from PHP 8.4, the use of implicitly nullable parameters has been deprecated. Thanks to the fixes in OpenAPI Generator version 7.11.0 ( https://github.com/OpenAPITools/openapi-generator/pull/20243 ) by @77web, any occurrence of this deprecated syntax has been removed from the autogenerated files.
- function foo (array $data = null)
+ function foo (array|null $data = null)
For more information on these deprecations, please refer to the PHP 8.4 Migration Guide.
Additionally, several implementations have been refactored for improved type safety. This raised the PHPStan level from 5 to 8.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.2.1...v10.3.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
This change modifies the HTTP status code for the following audience group-related endpoints, as they were incorrect. Some http status codes are wrong. They should be 202, not 200.
POST /v2/bot/audienceGroup/upload (createAudienceGroup)PUT /v2/bot/audienceGroup/upload (addAudienceToAudienceGroup)POST /v2/bot/audienceGroup/upload/byFile (createAudienceForUploadingUserIds)POST /v2/bot/audienceGroup/click (createClickBasedAudienceGroup)POST /v2/bot/audienceGroup/imp (createImpBasedAudienceGroup)NOTE: This change is not a modification of the messaging API itself. It is simply a correction of an error in sdk.
(original PR is https://github.com/line/line-openapi/pull/87)
<!-- PR-END https://github.com/line/line-openapi/pull/87 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.2.0...v10.2.1
This release is prepared by @Yang-33
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
We have implemented and supported new API and Webhook about Membership.
You can obtain a list of user IDs for users who have joined the membership of your LINE Official Account by calling client.getJoinedMembershipUsers(...).
Documents: https://developers.line.biz/en/reference/messaging-api/#get-membership-user-ids
We have introduced new Webhook events MembershipEvent that indicates that a user has joined, left or renewed a membership of your LINE Official Account.
Documents: https://developers.line.biz/en/reference/messaging-api/#membership-event
For more details, check out the announcement: https://developers.line.biz/en/news/2025/02/13/membership-api/
(original PR is https://github.com/line/line-openapi/pull/86)
<!-- PR-END https://github.com/line/line-openapi/pull/86 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.1.0...v10.2.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- PR-START https://github.com/line/line-openapi/pull/85 -->
Add /v2/bot/audienceGroup/shared path by @github-actions in https://github.com/line/line-bot-sdk-php/pull/662
We have added and supported new API endpoints related to Shared Audiences in Business Manager.
You can obtain detailed information about a specific audience shared in Business Manager by calling the endpoint:
https://api.line.me/v2/bot/audienceGroup/shared/{audienceGroupId}You can acquire a list of audiences shared in Business Manager using the following endpoint:
https://api.line.me/v2/bot/audienceGroup/shared/listBy using the "Get Shared Audience Information" endpoint, you can retrieve more detailed data about each audience.
For more information, please refer to the links provided above.
(original PR is https://github.com/line/line-openapi/pull/85)
<!-- PR-END https://github.com/line/line-openapi/pull/85 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.0.3...v10.1.0
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- PR-START https://github.com/line/line-openapi/pull/82 -->
GET /v2/bot/message/delivery/ad_phone was sunset.
This change removes it as it's no longer necessary to include it in line-openapi.
(original PR is https://github.com/line/line-openapi/pull/82)
<!-- PR-END https://github.com/line/line-openapi/pull/82 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.0.2...v10.0.3
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- PR-START https://github.com/line/line-openapi/pull/80 -->
The Audience Match feature (/bot/ad/multicast/phone) was sunset in October 2023. This change removes it as it's no longer necessary to include it in line-openapi.
(original PR is https://github.com/line/line-openapi/pull/80)
<!-- PR-END https://github.com/line/line-openapi/pull/80 -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.0.1...v10.0.2
This release is prepared by @Yang-33
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
A new value in "NarrowcastProgressResponse#errrorCode" was defined and comments have been added to the SDK. https://developers.line.biz/en/reference/messaging-api/#get-narrowcast-progress-status
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/v10.0.0...v10.0.1
This release is prepared by @eucyt
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
*AllOf.php are deleted. See in below to understand how to migrate.EventRequestParser to use phpstan@2.0If your application uses any *AllOf.php provided in this repository, please use *.php instead. only changing class name is enough, because they are same internally.
e.g.
MessageEventAllOf -> MessageEvent.use LINE\Webhook\Model\MessageEventAllOf; -> use LINE\Webhook\Model\MessageEvent;ClipboardActionAllOf -> ClipboardActionuse LINE\Clients\MessagingApi\Model\ClipboardActionAllOf; -> use LINE\Clients\MessagingApi\Model\ClipboardAction;Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.12.0...v10.0.0
This release is prepared by @Yang-33
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Support bot mention features:
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.11.0...9.12.0
<!-- Release notes generated using configuration in .github/release.yml at 9.10.0 -->
<!-- Release notes generated using configuration in .github/release.yml at 9.10.0 -->
https://github.com/line/line-bot-sdk-php/pull/608
In the Messaging API, we've added the following values as the percentage of each age group of your LINE Official Account's friends that you can get by using the Get friend demographics endpoint:
from50to54from55to59from60to64from65to69from70Previously, we've aggregated the percentage of friends who are 50 and older as a single value, from50. With this change, you can now get statistics on the percentage of friends between the ages of 50 and 70.
We'll continue to include from50 in the response as a value that aggregates the percentage of friends who are 50 and older.
News: https://developers.line.biz/en/news/2024/09/05/age-percentage-subdivision/
https://github.com/line/line-openapi/pull/68
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.9.1...9.10.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
https://github.com/line/line-bot-sdk-php/pull/608 In the Messaging API, we've added the following values as conditions for filtering the age range of recipients in the demographic filter objects of narrowcast messages:
age_55age_60age_65age_70Until now, the upper limit was age_50, so it wasn't possible to filter ages over 50 in detail. By specifying the added age ranges, you can now filter recipients more flexibly than before.
news: https://developers.line.biz/en/news/2024/08/26/age-filter-subdivision/
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.9.1...9.10.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
php artisan vendor:publish command not working in Laravel application by @nick-lai in https://github.com/line/line-bot-sdk-php/pull/600Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.9.0...9.9.1
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
In the Messaging API, we've added a new endpoint that allows you to display a loading animation. After your LINE Official Account receives a message from a user, the response may takes some time due to message preparation or reservation processing. In such cases, you can visually tell the user that you want them to wait by displaying a loading animation.
news: https://developers.line.biz/en/news/2024/04/17/loading-indicator/
https://github.com/line/line-openapi/pull/54
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.8.0...9.9.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
We're excited to announce that the Membership API is now available in the Messaging API. With this update, our SDK also supports the use of this API. For more details, check out the announcement: https://developers.line.biz/en/news/2024/03/28/re-release-endpoints-for-membership
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.7.1...9.8.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.7.0...9.7.1
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
In the Messaging API, you can now determine whether a user has added your LINE Official Account as a friend or unblocked by a webhook follow event.
News: https://developers.line.biz/en/news/2024/02/06/add-friends-and-unblock-friends-can-now-be-determined-by-webhook/
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.6.1...9.7.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
In the Messaging API, we've added the clipboard action for users to copy text to the clipboard. This new feature allows users to more easily copy coupon codes and other text.
news: https://developers.line.biz/en/news/2024/02/05/messaging-api-updated/
Note only the latest app(version >= 14.0.0) supports this feature. Please update your LINE app to try this feature.
I made a mistake in the release procedure. In the version before the correction, you cannot use the clipboard action.(in 9.6.0)
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.6.0...9.6.1
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
In the Messaging API, we've added the clipboard action for users to copy text to the clipboard. This new feature allows users to more easily copy coupon codes and other text.
news: https://developers.line.biz/en/news/2024/02/05/messaging-api-updated/
Note only the latest app(version >= 14.0.0) supports this feature. Please update your LINE app to try this feature.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.5.0...9.6.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
There are several keywords that can be used for the properties of Template Messages and Flex Messages.
Starting from this version, these keywords are provided. In addition to keywords, you can use strings that specify percentages or pixels, so please convert the keywords to strings if necessary. The original definitions are also written in Flex Message layout and https://github.com/line/line-openapi/pull/46.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.4.4...9.5.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
(Just updating documentation)
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.4.3...9.4.4
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.4.1...9.4.3
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.4.0...v9.4.2
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.4.0...9.4.1
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
We have now added support for a Webhook (PnpDeliveryCompletionEvent) that can be received once a message is successfully sent via PNP.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.3.0...9.4.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
You can now send quote messages from your LINE Official Account and receive quote messages sent by users via webhook. news: https://developers.line.biz/en/news/2023/09/14/send-and-receive-quote-messages-using-the-messaging-api/
sentMessage field is added in push and reply APIsentMessage field is added in push API's ErrorResponsequoteToken and quotedMessageId in some Webhook eventsFull Changelog: https://github.com/line/line-bot-sdk-php/compare/9.2.0...9.3.0
<!-- Release notes generated using configuration in .github/release.yml at master -->
<!-- Release notes generated using configuration in .github/release.yml at master -->
/oauth2/v3/token (issue stateless channel token) API https://github.com/line/line-openapi/pull/30Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.1.0...9.2.0
chore(deps): update line-openapi digest to 5c1f76e by @renovate in https://github.com/line/line-bot-sdk-php/pull/496
RICHMENU_IMP/RICHMENU_CLICK type to AudienceGroupType.Full Changelog: https://github.com/line/line-bot-sdk-php/compare/9.0.0...9.1.0
chore(deps): update line-openapi digest to db2f30d by @renovate in https://github.com/line/line-bot-sdk-php/pull/488
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/8.1.0...9.0.0
https://github.com/line/line-openapi/pull/23
Changes are based on
and some libraries or minors are upgraded internally.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/8.0.0...8.1.0
LINE's SDK developer team decides to generate SDK code based on OpenAPI spec. As a result, LINE bot sdk 8.x is not compatible with 7.x. But it can fol
LINE's SDK developer team decides to generate SDK code based on OpenAPI spec. As a result, LINE bot sdk 8.x is not compatible with 7.x. But it can follow the future API changes very quickly.
line-bot-sdk-tiny is no longer supported.src/LINEBot was splitted to src/clients/, src/parser and src/webhook/ modules.For instructions on how to use the new SDK, please refer to the examples/ directory.
Full Changelog: https://github.com/line/line-bot-sdk-php/compare/7.6.1...8.0.0
Patch for this deprecation. https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Fix this issue #387 @snmatsui Thanks for your report!
Patch for this deprecation. https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
## PHP 8.0 and 8.1 were supported. #381 #386 * We supported PHP8.0 and 8.1. * Unsupported PHP5.6, 7.0, 7.1. This fixed #384 .
This fixed #384 .
Added these properties to Postback action.
Reported by @hinoguma
Added these properties to Postback action.
Added these properties to webhook event object.
Added RichMenuSwitchTemplateActionBuilder. https://developers.line.biz/en/reference/messaging-api/#richmenu-switch-action
Add component builder to use video. https://developers.line.biz/en/docs/messaging-api/create-flex-message-including-video/
Add component builder to use video. https://developers.line.biz/en/docs/messaging-api/create-flex-message-including-video/
Add some properties. Please check detail here. https://developers.line.biz/en/news/2022/03/11/flex-message-update-3-released/#text-component-2022-03-11 https://developers.line.biz/en/news/2022/03/11/flex-message-update-3-released/#box-component-2022-03-11
Fix bug of #368 @omoon thanks for your report!
Fix bug of #368 @omoon thanks for your report!
Fixed bug of #367 . @love99067333 thanks for your report !
Fixed bug of #367 . @love99067333 thanks for your report !
Support followings.
See details. https://developers.line.biz/en/news/2021/11/09/messaging-api-update/
Support imageSet property. https://developers.line.biz/en/reference/messaging-api/#wh-image
Support imageSet property.
https://developers.line.biz/en/reference/messaging-api/#wh-image
Support this features. https://developers.line.biz/en/news/2021/?month=06&day=21&article=switch-between-multiple-rich-menus
Support this feature. https://developers.line.biz/en/reference/partner-docs/#get-statistics-per-unit
Support this feature. https://developers.line.biz/en/reference/partner-docs/#get-statistics-per-unit
Add PHPStan.
Improve PHP_CodeSniffer configs.
We remove Travis CI . And use Github Actions!
We changed document generator to phpDocumentor. https://line.github.io/line-bot-sdk-php/
We updated major version with respect for semantic versioning. Fixed class name typo. BubleContainerSize → BubbleContainerSize
We updated major version with respect for semantic versioning. Fixed class name typo. BubleContainerSize → BubbleContainerSize
Fix class name typo. BubleContainerSize → BubbleContainerSize
Fix return type of EmojiInfo::getLength() PHPDoc.
Fix return type of EmojiInfo::getLength() PHPDoc.
Added toArray method to BaseEvent for debug.
Fix this issue with install on Windows. https://github.com/line/line-bot-sdk-php/issues/348
Support following API. https://developers.line.biz/ja/reference/messaging-api/#get-follower-ids
Supported activate audience API. https://developers.line.biz/en/news/2021/01/27/activate-audience-api/
Supported activate audience API. https://developers.line.biz/en/news/2021/01/27/activate-audience-api/
Supported missing defaultAction property for carousel column.
https://developers.line.biz/en/reference/messaging-api/#column-object-for-carousel
Supported mention object in TextMessageEvent which allows us to capture mentionee information.
https://developers.line.biz/en/news/2021/01/20/messaging-api-update-january-2021/#text-message-type-properties-news
Fixed an issue with custom http client usage. https://www.line-community.me/ja/question/5fd1d77b4016904e521e7020
Change behavior of \LINEBot\Response#isSucceeded .Status code 200 ~ 299 -> true, other false.
Fix doc of getMember function.
Change behavior of \LINEBot\Response#isSucceeded .Status code 200 ~ 299 -> true, other false.
Support this feature. https://developers.line.biz/en/news/2020/12/02/messaging-api-update-december-2020/#keywords-news
One column per quarter.