<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Release Radar - Breaking</title><link>https://releaseradar.jp/en/</link><description>Official release notes and API changes from freee, kintone, SmartHR, LINE, and other Japanese SaaS products for AI builders.</description><language>en</language><atom:link href="https://releaseradar.jp/en/updates/latest/breaking/feed.xml" rel="self" type="application/rss+xml"/><item><title>[Sakura Cloud] Monitoring Suite metrics storage write rate and payload size limits changed</title><link>https://releaseradar.jp/en/updates/sakura/20aa623276b6/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/sakura/20aa623276b6/</guid><pubDate>Wed, 28 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Write rate and payload size limits for metrics storage in Sakura Cloud Monitoring Suite have changed.
・The write rate limit changed from 5,000 new Series per hour to 600 write requests per minute.
・The payload size limit changed from no limit to 5MiB (when compressed) per request.
https://cloud.sakura.ad.jp/news/2026/10/29/monitoring-suite-metrics-storage-limits/</description></item><item><title>[Sakura Cloud] Secret Manager secret retrieval API returns an error when specifying version=0</title><link>https://releaseradar.jp/en/updates/sakura/ba3ba147e51b/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/sakura/ba3ba147e51b/</guid><pubDate>Tue, 27 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>In Secret Manager, specifying version=0 in the secret retrieval API will return an error instead of the latest secret version.
・Specifying version=0 returns an error as an invalid nonexistent version
https://cloud.sakura.ad.jp/news/2026/10/28/change-secret-retrieval-api/</description></item><item><title>[Sakura Cloud] Network Suite on SAKURA Cloud becomes an official service</title><link>https://releaseradar.jp/en/updates/sakura/31a06fc3cc2d/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/sakura/31a06fc3cc2d/</guid><pubDate>Sun, 25 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Network Suite will become an official service, and you must apply to continue using resources created during the CR version.
・Network Suite will be available as an official service starting November 26, 2026.
・Usage fees (tax included) start on December 1, 2026: Subnet costs 1,100 yen/month (55 yen/day, 5 yen/hour), and Subnet Group costs 550 yen/month (27 yen/day, 3 yen/hour).
・If you do not apply for continued use, resources created during the CR version will be deleted on November 26, 2026.
・If you do not continue using the service, you must disconnect servers from subnets by November 26, 2026 to avoid server stoppage.
https://cloud.sakura.ad.jp/news/2026/10/26/networking-suite-formalization/</description></item><item><title>[Lolipop!] session.upload_progress is now disabled across all PHP versions</title><link>https://releaseradar.jp/en/updates/lolipop/7227ff0e42a6/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/lolipop/7227ff0e42a6/</guid><pubDate>Tue, 20 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Maintenance for PHP vulnerabilities has finished, and session.upload_progress has been disabled across all versions to ensure security.
・Official security patches were applied to PHP 8.x and PHP 7.4.
・Custom security fixes based on official patches were applied to other PHP versions.
・Suspended services including user control panels and APIs have resumed.
https://lolipop.jp/info/news/8237/</description></item><item><title>[LINE Developers] LIFF v2.31.2 release and change to handling of ? in LIFF URL query parameters</title><link>https://releaseradar.jp/en/updates/line/74961e9d11da/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/74961e9d11da/</guid><pubDate>Tue, 06 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>LIFF v2.31.2 changes how question marks in LIFF URL query parameter values are restored in the secondary redirect URL inside the LIFF browser.
・When opening a LIFF app in the LIFF browser, ? in LIFF URL query parameter values is preserved as ? instead of being replaced with &amp; in the secondary redirect URL.
・Opening a LIFF app in an external browser is not affected by this change.
・When ? in a query parameter value is percent-encoded as %3F and accessed on iOS from outside the LINE app, the secondary redirect URL now receives ? instead of &amp;.
・Users of the CDN edge path are automatically updated to v2.31.2, while users of a fixed CDN path or the @line/liff npm package must update the version manually.
・LIFF v2.20.0 through v2.31.0 are deprecated due to a bug with potential security implications.
https://developers.line.biz/ja/news/2026/10/07/release-liff-2-31-2/</description></item><item><title>[Mackerel] You can now send traces and logs via OTLP/HTTP JSON, and agent proxy handling changed</title><link>https://releaseradar.jp/en/updates/mackerel/74cac1849ab0/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/mackerel/74cac1849ab0/</guid><pubDate>Mon, 05 Oct 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Mackerel now accepts traces and logs in OTLP/HTTP JSON format, and mackerel-agent can bypass proxies by ignoring environment variables.
・You can now send traces and logs directly to Mackerel by specifying http/json as the protocol.
・Specifying direct for http_proxy or https_proxy in mackerel-agent v0.87.1 or later ignores proxy environment variables.
・Specifying -u kb in check-disk now correctly monitors thresholds in KB units in mackerel-check-plugins v0.53.0 or later.
・Specifying on_stop in host_status now reliably changes to the specified status in mackerel-agent v0.87.1 or later.
・A beta logs feature is now available on status page components.
https://mackerel.io/ja/blog/entry/weekly/20261006</description></item><item><title>[Money Forward Cloud] Integration items from Cloud Payroll to Cloud Tax Adjustment changed</title><link>https://releaseradar.jp/en/updates/moneyforward/231c6003002f/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/moneyforward/231c6003002f/</guid><pubDate>Mon, 28 Sep 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Linked items imported from Cloud Payroll to the filing office settings in Cloud Tax Adjustment have changed.
・Business owner name and furigana are no longer automatically linked when importing from Cloud Payroll or updating filing offices.
・Existing users can carry over previous year data by selecting &quot;Copy and add previous year info&quot; from &quot;+ Add&quot;.
・This applies to the &quot;Settings &gt; Business &gt; Filing Office&quot; screen for accounts with Full Administrator or General Administrator roles.
https://biz.moneyforward.com/support/tax-adjustment/news/new-feature/20260929.html</description></item><item><title>[LINE Developers] Temporary suspension of switching LINE Official Accounts on the channel consent screen</title><link>https://releaseradar.jp/en/updates/line/6129b469e168/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/6129b469e168/</guid><pubDate>Mon, 14 Sep 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>LINE MINI App temporarily suspended switching the LINE Official Account on the channel consent screen due to a technical issue.
・Adding the prompt_bot_id query parameter to a LIFF URL or permanent link does not switch the LINE Official Account on the channel consent screen
・Switching the LINE Official Account on the permission request screen or the subwindow prompting users to add or unblock an account remains available
・Service resumption is scheduled for early November 2026 and may change without notice
https://developers.line.biz/ja/news/2026/09/15/use-multiple-accounts/</description></item><item><title>[Money Forward Cloud] Employee CSV format and version changed in Money Forward Cloud Payroll</title><link>https://releaseradar.jp/en/updates/moneyforward/a40fa758a6fa/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/moneyforward/a40fa758a6fa/</guid><pubDate>Wed, 02 Sep 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Employee CSV formats and import matching criteria changed following the introduction of office codes.
・You can now manage office codes on the Office screen, which are automatically generated from existing data.
・The classification name changed from &quot;坑内夫&quot; to &quot;坑内員&quot; on the employee screen and in CSV files.
・Employee CSV files now include &quot;所属事業所コード&quot;, and the &quot;所属事業所&quot; column name changed to &quot;所属事業所名&quot;.
・CSV import matching changed from matching the office name to matching the office code exactly.
・Importing an employee CSV exported before the release causes an error and fails to import.
https://biz.moneyforward.com/support/payroll/news/new-feature/20260903-2.html</description></item><item><title>[LINE Developers] Change to handling of &quot;?&quot; in LIFF URL query parameter values in the LIFF browser</title><link>https://releaseradar.jp/en/updates/line/152ef74dcd1a/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/152ef74dcd1a/</guid><pubDate>Sun, 30 Aug 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>From LIFF v2.31.2, the LIFF browser is scheduled to keep &quot;?&quot; in query parameter values instead of replacing it with &quot;&amp;&quot; upon redirect.
・The target version was changed from LIFF v2.31.1 or later to LIFF v2.31.2 or later, scheduled for release on October 7, 2026
・The change applies only when opening a LIFF app in the LIFF browser, with no change in behavior in external browsers
・When accessing a LIFF URL containing percent-encoded &quot;%3F&quot; from outside the LINE app on iOS, the secondary redirect URL value becomes &quot;?&quot; instead of &quot;&amp;&quot;
・Behavior remains unchanged when accessing a LIFF URL containing &quot;%3F&quot; from the LINE app on iOS or from an Android device
https://developers.line.biz/ja/news/2026/08/31/liff-query-parameter-change/</description></item><item><title>[Color Me Shop] Restock behavior on cancel sale, warnings field, and stock_quantity changed</title><link>https://releaseradar.jp/en/updates/colorme/d4ac365f6dd3/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/colorme/d4ac365f6dd3/</guid><pubDate>Tue, 18 Aug 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Stock now restores when canceling single-option items, cancel responses include warnings, and stock_quantity values have changed.
・Purchased stock is now restored when canceling orders with restock set to true for single-option products with per-option inventory.
・Cancel sale responses now include warnings, returning notices when applicable or an empty array when there are none.
・The warnings array includes code for the warning type, detail_id for the sales detail ID, and message for the warning text.
・Colorme.sale.items stock_quantity on the post-purchase cart now returns the purchased option stock for single-option products.
https://developer.shop-pro.jp/news/releases/fix_v1_sales_cancel_restock_20260813</description></item><item><title>[Color Me Shop] soldout_display in product and stock APIs now returns values matching shop settings</title><link>https://releaseradar.jp/en/updates/colorme/d9d1bf94a3b9/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/colorme/d9d1bf94a3b9/</guid><pubDate>Tue, 18 Aug 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>The soldout_display boolean in Colorme Shop API now reflects actual store settings instead of returning inverted values.
・When out-of-stock display is set to display products, true is returned, and when set to not display products, false is returned.
・If the per-product out-of-stock display setting is unconfigured, the value follows the out-of-stock setting in stock display settings.
・Per-product settings take priority over stock display settings.
・Write operations are unaffected because soldout_display cannot be specified in product creation or update requests.
https://developer.shop-pro.jp/news/releases/fix_soldout_display_20260814</description></item><item><title>[CloudSign] Web API filename restrictions and Webhook URL length expansion</title><link>https://releaseradar.jp/en/updates/cloudsign/28c3f8590817/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/cloudsign/28c3f8590817/</guid><pubDate>Sun, 16 Aug 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>File uploads via Web API are now restricted for specific filenames, and you can register longer Webhook URLs.
・POST /documents/[docID]/files returns a 400 error if the filename contains &apos;\&quot;&apos; or ends with &apos;\&quot;&apos; or &apos;\\&apos;
・You can now register Webhook URLs of up to 512 characters
・You can now search for documents by specifying &apos;Status Update Date and Time&apos; on the document management screen
https://www.cloudsign.jp/releasenotes/202606_releasenote/</description></item><item><title>[Garoon] You can now get schedule comments and keyword is ignored when showPrivate is true</title><link>https://releaseradar.jp/en/updates/garoon/7a4df211cc61/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/garoon/7a4df211cc61/</guid><pubDate>Thu, 13 Aug 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>You can now get event comments in Garoon REST API, while setting showPrivate to true returns results that ignore the keyword parameter.
・You can now retrieve the list of comments posted on a specific schedule event.
・When showPrivate is set to true in the API to get multiple schedule events, keyword is ignored and results without keyword search are returned.
https://cybozu.dev/ja/garoon/news/api-updates/2026-09/</description></item><item><title>[microCMS] Partial match search queries are limited to 2,000 characters</title><link>https://releaseradar.jp/en/updates/microcms/edd8337492ee/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/microcms/edd8337492ee/</guid><pubDate>Tue, 21 Jul 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Search strings for partial match conditions in the Content API and management screen are restricted to 2,000 characters.
https://blog.microcms.io/filters-partial-match-character-limit/</description></item><item><title>[Mackerel] You can now view detailed route information on the APM HTTP server tab</title><link>https://releaseradar.jp/en/updates/mackerel/14c40f2cc04d/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/mackerel/14c40f2cc04d/</guid><pubDate>Thu, 25 Jun 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>You can now view route-level metrics in APM, and behavior changed for the notification group API and Terraform provider.
・Selecting a route on the APM HTTP server screen opens a details view with request and latency charts and a trace list.
・The type column is included in notification group registration and list API responses, returning group-default for default groups and group for others.
・Notification channels created with terraform-provider-mackerel v0.10.0 or later are no longer automatically added to the default notification group.
・You can now use the mackerel_default_notification_group resource to manage default notification groups in Terraform.
・Kubernetes 1.36 is now supported as an operating environment for mackerel-container-agent.
https://mackerel.io/ja/blog/entry/weekly/20260624</description></item><item><title>[freee] You can now use procurement and purchase order APIs, and response schemas changed</title><link>https://releaseradar.jp/en/updates/freee/e5f31dfb6a5e/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/freee/e5f31dfb6a5e/</guid><pubDate>Thu, 25 Jun 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>You can now manage procurements and purchase orders via API, while response structures for deals and sales have breaking changes.
・You can now list, create, get, update, and cancel procurements and purchase orders via API.
・The structure of partner and assignee information changed in responses for deals, deliveries, quotations, sales, and sales orders.
・You can now filter list APIs for deals, sales orders, and others using start_last_updated_date and end_last_updated_date.
・Fields such as amount_set and billing_status became required, while amount_of_withholding_tax and others became optional and nullable.
・The code and uom_name fields became nullable in the item master API.
https://developer.freee.co.jp/release-note/8115#:~:text=(6%2F26)%EF%BC%BB%E8%B2%A9%E5%A3%B2%EF%BC%BD%E4%BB%95%E5%85%A5%E3%83%BB%E7%99%BA%E6%B3%A8%E9%96%A2%E9%80%A3%E3%82%A8%E3%83%B3%E3%83%89%E3%83%9D%E3%82%A4%E3%83%B3%E3%83%88%E3%81%AE%E8%BF%BD%E5%8A%A0%E3%81%8A%E3%82%88%E3%81%B3%E3%83%AC%E3%82%B9%E3%83%9D%E3%83%B3%E3%82%B9%E6%A7%8B%E9%80%A0%E3%81%AE%E4%BB%95%E6%A7%98</description></item><item><title>[microCMS] API schema export and Management API responses are changing</title><link>https://releaseradar.jp/en/updates/microcms/552d68fd54bf/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/microcms/552d68fd54bf/</guid><pubDate>Tue, 23 Jun 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Responses returned by the API schema export and the Management API are scheduled to change.
https://blog.microcms.io/api-schema-export-management-api-response-changes/</description></item><item><title>[Mackerel] You now receive OK notifications when alerts close for retired hosts</title><link>https://releaseradar.jp/en/updates/mackerel/dcb841aef32c/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/mackerel/dcb841aef32c/</guid><pubDate>Wed, 10 Jun 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Closing alerts for retired hosts now delivers OK notifications so you can easily track state changes.
・Query graph series selections are now preserved when changing the time range in full-screen view.
・Ubuntu 26.04 LTS (Resolute Raccoon) is now supported by mackerel-agent.
・You can now skip certificate verification when collecting metrics by specifying the -tls-skip-verify option in mackerel-plugin-nginx.
・You can now use the CloudWatch GetMetricData API by specifying the -use-get-metric-data option in mackerel-plugin-aws-ec2-ebs.
・The supported version for mackerel-plugin-mongodb changed to MongoDB 4.2 or later, and versions 4.1 or earlier may stop working after updating.
https://mackerel.io/ja/blog/entry/weekly/20260611</description></item><item><title>[LINE Developers] Rate limit changed for Messaging API endpoint that gets rich menu list</title><link>https://releaseradar.jp/en/updates/line/47366a08e831/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/47366a08e831/</guid><pubDate>Mon, 25 May 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>On May 26, 2026, the rate limit for the Messaging API endpoint to retrieve the list of rich menus was reduced.
・The rate limit for the target endpoint changed from 2,000 requests/second to 10 requests/second
・Rate limits for all other endpoints remain unchanged
https://developers.line.biz/ja/news/2026/05/26/messaging-api-rate-limit/</description></item><item><title>[LINE Developers] Rate limit for Messaging API &quot;Get rich menu list&quot; endpoint is planned to change</title><link>https://releaseradar.jp/en/updates/line/92aa1065f579/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/92aa1065f579/</guid><pubDate>Wed, 06 May 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>The rate limit for the Messaging API endpoint that gets rich menu lists is scheduled to change on May 26, 2026.
・The rate limit for &quot;Get rich menu list&quot; changes from 2,000 requests per second to 10 requests per second.
・Rate limits for endpoints other than the above do not change.
・The contents and date of the change may change without notice.
https://developers.line.biz/ja/news/2026/05/07/messaging-api-rate-limit/</description></item><item><title>[LINE Developers] Edge-to-edge applies to Android LINE, extending WebView area to the bottom of the screen</title><link>https://releaseradar.jp/en/updates/line/42ca7c0acddb/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/42ca7c0acddb/</guid><pubDate>Wed, 11 Feb 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Edge-to-edge in Android LINE extends the WebView to the screen bottom, which may overlap app content with the gesture navigation bar.
・Applies to all LIFF and LINE mini apps on Android LINE version 26.3.0 or later
・WebView area extends to the bottom of the screen during gesture navigation
・WebView area at the top status bar does not change
・Safe-area-inset and --android-safe-area-inset on the left and right are always set to 0 in landscape mode
・Use safe-area-inset-bottom for WebView 144 or later and --android-safe-area-inset-bottom for versions below 144
https://developers.line.biz/ja/news/2026/02/12/edge-to-edge-support/</description></item><item><title>[KOMOJU] Tax calculation method changed in KOMOJU API POST payments</title><link>https://releaseradar.jp/en/updates/komoju/fca358d565cc/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/komoju/fca358d565cc/</guid><pubDate>Mon, 26 Jan 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>In API version v.2026-01-27, the tax calculation method for the payments endpoint has changed.
・Taxes are automatically calculated in POST payments only when auto is explicitly specified
https://docs.komoju.com/ja/changelog#:~:text=v.2026%2D01%2D27</description></item><item><title>[LINE Developers] Simplified channel consent is permanently enabled for new LINE Mini Apps in Japan</title><link>https://releaseradar.jp/en/updates/line/9248676e3dbe/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/line/9248676e3dbe/</guid><pubDate>Wed, 07 Jan 2026 15:00:00 GMT</pubDate><category>Breaking</category><description>Simplified channel consent is now permanently enabled and cannot be disabled for new LINE Mini App channels in Japan.
・Simplified channel consent is permanently enabled for new LINE Mini App channels in Japan
・The toggle button for simplified channel consent was removed from the Web app settings tab
・Channels with only the openid scope no longer show consent screens or friend add prompts
・Prompting friend addition now requires scopes other than openid or permission request methods
・Channels created before the change or with Thailand or Taiwan as service regions are unaffected
https://developers.line.biz/ja/news/2026/01/08/channel-consent-simplification/</description></item><item><title>[Chatwork] Chatwork API stops accepting query parameters for POST/PUT and removes method parameter</title><link>https://releaseradar.jp/en/updates/chatwork/568f5ba2c6ce/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/chatwork/568f5ba2c6ce/</guid><pubDate>Wed, 02 Apr 2025 15:00:00 GMT</pubDate><category>Breaking</category><description>Chatwork API is scheduled to stop reading query parameters on POST and PUT requests and remove HTTP method overrides via method.
・Eleven POST and PUT operations, such as creating group chats and posting messages, will read only application/x-www-form-urlencoded body parameters instead of query parameters.
・Specifying an HTTP method different from the actual HTTP request via the method parameter will be removed.
・Sending requests using the removed formats will return a status code 400 error.
https://developer.chatwork.com/changelog/202501-notice</description></item><item><title>[Chatwork] End of support for TLS 1.0 and TLS 1.1 in Chatwork API</title><link>https://releaseradar.jp/en/updates/chatwork/5bcbe232204b/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/chatwork/5bcbe232204b/</guid><pubDate>Mon, 25 Nov 2024 15:00:00 GMT</pubDate><category>Breaking</category><description>To strengthen security, Chatwork API is scheduled to end support for TLS 1.0 and TLS 1.1 on February 3, 2025.
・From the scheduled end date of February 3, 2025, Chatwork API cannot be used with TLS 1.0 or TLS 1.1
・No action is required if programs already communicate using TLS 1.2 or above
https://developer.chatwork.com/changelog/20241126-notice</description></item><item><title>[Color Me Shop] Order API specifications change with the order segment feature</title><link>https://releaseradar.jp/en/updates/colorme/2e4607d3db27/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/colorme/2e4607d3db27/</guid><pubDate>Wed, 15 Feb 2023 15:00:00 GMT</pubDate><category>Breaking</category><description>You can now retrieve split order data via the APIs, while rules for updating and cancelling orders have changed.
・You can reference split status and parent order IDs from the segment field in order responses.
・A negative order amount is returned if the total discount exceeds an individual split order.
・For split orders, you can update the point status only on the parent order.
・Cancelling a parent order also cancels related split orders, and specifying a child order returns an error.
・Specifying a child order returns an error when sending order or payment confirmation emails.
https://developer.shop-pro.jp/news/releases/release_segment</description></item><item><title>[Chatwork] Chatwork API Changes for Free Plan Group Chat Limit Removal and Message Restrictions</title><link>https://releaseradar.jp/en/updates/chatwork/078347a6824a/</link><guid isPermaLink="true">https://releaseradar.jp/en/updates/chatwork/078347a6824a/</guid><pubDate>Mon, 05 Sep 2022 15:00:00 GMT</pubDate><category>Breaking</category><description>Chatwork plans to update the Chatwork API for the Free Plan to remove the group chat limit and restrict message retrieval.
・In the Free Plan, the limit of 7 group chats in total will be removed, allowing users to create and join 8 or more group chats via API.
・In the Free Plan, viewable messages will be limited to the latest 5,000 messages posted within the past 40 days per organization, so some or all messages may not be retrievable via API.
・When the message retrieval API returns restricted results, the response headers chatwork-message-limitation (set to true) and chatwork-message-limitation-summary will be added; if not restricted, both headers are omitted.
・For retrieving the message list, the HTTP status code will be 200 when some messages are restricted, and 204 when all messages are restricted.
・For retrieving a single message, the HTTP status code will be 404 when the specified message ID is restricted.
https://developer.chatwork.com/changelog/2022-09-06-notice</description></item></channel></rss>
