A new group setting called "Skip Status Code" (skipStatusCode) has been added to the Soracom Funk UDP entry point and TCP entry point. When you enable this setting, Funk responses sent to devices omit the leading HTTP status code and the following space.

Background

Previously, when using the Funk UDP entry point or TCP entry point (*1), Funk responses always included a prefix in the Soracom Funk format: HTTP status code + space + response body returned by the Function as a Service (FaaS) function.

For simple device implementations that did not use the status code, or for custom protocols where leading numeric characters created compatibility issues, additional processing was required to remove this prefix.

(*1) This also applies when using a Unified Endpoint with the response format set to SORACOMFunk.

Added functionality

When you enable "Skip Status Code" in the group settings:

• The leading HTTP status code + space is removed from responses returned via the UDP entry point and TCP entry point.
• Whether the HTTP status code is in the 200 range or 400 and above, only the response body returned by the Function as a Service (FaaS) function is returned.
• Unified format responses (when using a Unified Endpoint with response format set to Unified) are not affected; the statusCode field remains included.

The Soracom CLI and Soracom API now include the skipStatusCode configuration parameter (Boolean). Set it to true to apply the same behavior programmatically.

For configuration steps and response examples, refer to the documentation below.

Documentation

• Soracom Funk Configuration

If you have any questions, please contact Soracom Support.

As of September 11, 2025, the price of the aiwa tab AB10L Android tablet on the Soracom IoT Store has been revised as follows. All prices are in Japanese Yen (¥) and include consumption tax.

aiwa tab AB10L

• Old price: ¥21,670 (including ¥1,000 Soracom service coupon)
• New price: ¥14,850 (including ¥1,000 Soracom service coupon)

For more details, visit the product page (Japanese).

Please note that this product is currently only available for customers located in Japan. If you are located outside of Japan and are interested, please contact us.

We are pleased to announce that a new RTSP Camera Image Action is available for Soracom Flux. This action allows you to retrieve a still image from a network camera as part of a Flux App.

• Uses RTSP (Real Time Streaming Protocol), a standard protocol for network cameras
• Retrieves images from RTSP-enabled cameras connected to Soracom using Soracom Air or Soracom Arc

For more information, please refer to RTSP Camera Image Action documentation.

If you have any questions, please contact Soracom Support.

We would like to inform customers that the coverage change date for Soracom Air for Cellular planP1 in Singapore, originally scheduled for September 15, 2025, has been adjusted to September 11, 2025. We apologize for any inconvenience this may cause and appreciate your understanding. Please see the details below.

planP1

Country	Networks	Before	After	Remarks
Singapore	SingTel	3G, 4G (LTE)	-	Network closed

Connectivity in Singapore is still available through StarHub 4G (LTE). Note that 3G-only devices will not be able to connect in Singapore after the above network closure.

For complete details about data rates, supported carriers and radio types, and coverage in other countries, please refer to the Supported Carriers documentation.

We are excited to announce that Remote Command now supports RTSP-enabled devices, enabling seamless control of network cameras and other RTSP-compatible devices directly from the Soracom platform.

Key Features

• Snapshot Command: You can send a snapshot command to the Remote Command API to get the current snapshot from an RTSP video stream.

This new feature simplifies the integration of RTSP-enabled devices into your IoT workflows, providing greater flexibility and control.

For more details, please visit the Remote Command documentation.

We are pleased to release an new improved API for Soracom Napter which allows for On-Demand Remote Access permissions to be controlled on a per-SIM basis.

With the existing API, Napter On-Demand Remote Access sessions are created by specifying the SIM ID in the body of the API request. The new API places the SIM ID parameter in the URL path instead, making it possible to control remote access to specific SIMs for administrators or field personnel by using path variables when configuring SAM user permissions.

The following APIs can now be used to create On-Demand Remote Access sessions:

• PortMapping:createPortMapping API: SIM ID specified in the request body
• PortMapping:createPortMappingForSim API: SIM ID specified in the request URL path

Since this update introduces a second API for creating remote access sessions, please review the following details to ensure your existing user permissions continue to work as expected.

Required Action: Update SAM User Permissions

1. Check if any of your SAM User, Role, or Default permissions currently specify the existing PortMapping:createPortMapping API (allow or deny).
2. Update each permission to add the new PortMapping:createPortMappingForSim API, following the desired allow or deny behavior.
3. (Optional) If you wish to restrict a user's access to a specific SIM, add a condition to the new PortMapping:createPortMappingForSim API to match the particular SIM, and ensure that the existing PortMapping:createPortMapping API is set to deny.

Please note that if you do not update your permissions, a SAM user whose PortMapping:createPortMapping API permission is currently denied may be able to access Napter using the new PortMapping:createPortMappingForSim API instead.

We recommend updating SAM User, Role, or Default permissions as soon as possible to avoid unexpected behavior.

Additional User Console Updates

On October 9, 2025, the On-Demand Remote Access function in the User Console will be updated to use the new PortMapping:createPortMappingForSim API.

If you do not update SAM user permissions as above, users may encounter the following issues:

• A user who previously could create On-Demand Remote Access sessions may no longer be able to do so until their permission is updated to allow the new API
• A user who previously was not able to create On-Demand Remote Access sessions may be able to do so because their permission has not been updated to deny the new API

We will provide a separate announcement once the User Console has been updated.

If you have any questions, please feel free to contact Soracom Support.

We are pleased to announce that the Soracom Flux SoraCam Image Action now supports the SoraCam Real-time Access (Japanese) feature.

Previously, the SoraCam Image Action was limited to accessing still images that have already been uploaded to the cloud using the SoraCam cloud recording function. With this update, you can now capture live images directly from SoraCam compatible cameras in real time.

For more details, please refer to the SoraCam Image Action (Japanese) and Soracom Flux (Japanese) documentation.

Note: To use this new feature, you must enable Real-time Access (Japanese) for your SoraCam compatible cameras, which will incur additional fees per camera. For additional pricing details, see SoraCam Pricing (Japanese).

If you have any questions, please contact Soracom Support.

Please note that this service is currently only available for customers located in Japan.

We are pleased to announce new 60-day and 90-day Cloud Always Recording Licenses for Soracom Cloud Camera Services (SoraCam).

With these new licenses, videos uploaded from a SoraCam compatible camera device will be stored for 60 and 90 days, respectively, allowing users to review footage from over a month ago, such as when managing construction sites, building projects, or other use cases that span several months.

These new license options are now available in addition to the existing 7-day, 14-day, and 30-day licenses. Note that 60-day and 90-day licenses are charged on a monthly basis per camera.

For more information, please refer to the pricing information (Japanese) or the SoraCam product page (Japanese).

If you have any questions, please contact Soracom Support.

Please note that this service is currently only available for customers located in Japan.

We would like to inform customers that pricing and service terms for certain Soracom services will be revised, effective December 1, 2025. These updates help ensure the Soracom platform remains reliable and sustainable as IoT use cases and deployments continue to grow and diversify.

Overview of Changes

• Soracom Air for Cellular (Japan Coverage) - plan-D (no bundle): Sales of new subscriptions will be discontinued. Existing subscriptions will remain operational, however pricing will be revised.
• Soracom Air for Cellular (Japan Coverage) - plan-D (D-300MB) and plan-K2 (K2-300MB): Data allowance will be increased to 500MB for both new and existing subscriptions, and pricing and plan names will be revised accordingly.
• Soracom Air for Cellular (Japan Coverage) - plan-DU, plan-K, and plan-KM1: Pricing will be revised.
• Soracom Air for Cellular (Japan Coverage/Global Coverage) - All subscriptions: Measurement of downlink data usage will be revised to include IP headers, UDP headers, and GTP headers, matching the measurement applied to subscriptions launched since May 2023. For more information, refer to Data Communication Subject to Billing (Japanese).
• Virtual Private Gateway (Japan Coverage/Global Coverage) - All types: Pricing structure for VPG and related features will be revised from hourly to monthly billing.

All other pricing and service terms will remain unchanged.

Effective Date

These changes will automatically take effect for customers located in Japan starting December 1, 2025. No action is required.

For details, please refer to the detailed pricing table (PDF) (Japanese).

Inquiries

If you have any questions or concerns, please contact your sales representative or the Soracom support team.

We appreciate your understanding and continued support of Soracom.

We would like to inform customers of the following coverage changes for Soracom Air for Cellular connectivity. These changes will take effect on September 11, 2025.

planP1

Country	Networks	Before	After	Remarks
Singapore	SingTel	3G, 4G (LTE)	-	Network closed

Connectivity in Singapore is still available through StarHub 4G (LTE). Note that 3G-only devices will not be able to connect in Singapore after the above network closure.

For complete details about data rates, supported carriers and radio types, and coverage in other countries, please refer to the Supported Carriers documentation.

---

September 5, 2025 Update

This announcement was corrected as follows:

Before correction:

Scheduled date: September 15, 2025

After correction:

Scheduled date: September 11, 2025