We are pleased to announce that Metadata Service now supports HTTPS connections.

Previously, IoT devices could only connect to Metadata Service using unencrypted HTTP, with network security provided by Soracom Air's closed carrier network.

With this update, IoT devices can now connect to Metadata Service using HTTPS, enabling support for device applications that are required to access Metadata Service using a secure connection.

This update also provides support for Cross-Origin Resource Sharing (CORS), allowing browser-based applications to access Metadata Service. When developing a browser-based application that will call Metadata Service, be sure to configure the appropriate CORS settings.

Note: HTTPS connections to Metadata Service still require an active Soracom Air connection. Connecting to Metadata Service using a separate internet connection is not supported.

For more information, please refer to the Metadata Service documentation.

Soracom Launch Support is a service where you can consult directly with Soracom's IoT professionals about developing your IoT application. You can ask questions like "Where should I start?" or "What decisions should I make?" and our IoT experts will work with you to consider everything from technical architecture to project planning.

Starting today, June 25, 2025, we are accepting applications for Soracom Launch Support.

Monthly Fee

11,000 yen (tax included)

How to Apply

If you would like to use Soracom Launch Support to help get your IoT project up and running, sign in to the User Console as your root user, switch to Japan Coverage, then click the Support menu, choose Soracom Launch Support, and follow the on-screen instructions. The application process takes only a few minutes.

If you don't already have a Soracom account, please refer to the Create a Soracom Account documentation for creating an account and registering a payment method prior to applying.

For more details, please refer to the User console (Japanese).

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

We have added a new Soracom Cloud Camera Services (SoraCam) Image Action to Soracom Flux, making it easier to automatically capture images from your SoraCam-compatible cameras as part of a Flux app.

This action allows you trigger a SoraCam-compatible camera to grab an image. For example, you can trigger it when the camera detects motion or sound (Japanese), or at a fixed periodic interval, and then retrieve the image for processing with additional Flux actions. You can also optionally store the image in Soracom Harvest Files for easy access and archiving.

Note: The SoraCam Image Action is currently available only in Japan Coverage.

For setup details, please refer to the SoraCam Image Action (Japanese) documentation.

We are excited to announce a new Test Mode feature which allows devices to connect to cellular networks and send and receive a limited amount of data and SMS without incurring usage fees. This allows customers to perform network communication tests and initial device provisioning when manufacturing IoT devices, independent of when those devices will be deployed and activated.

This feature introduces a new Testing status for Soracom Air IoT SIMs, with the following behavior:

• When an IoT SIM in the Ready status makes its first connection to a network, the SIM status is automatically changed to Testing.
• While the SIM is in Testing, data and SMS usage fees are waived up to a certain limit of data, SMS, or time spent in the Testing status.
• Once the SIM exceeds any of the data, SMS, or time limits, the SIM status is automatically changed to Active, or another IoT SIM status you designate.

For more details, please refer to the Test Mode documentation.

How to apply

In order to enable Test Mode for your Soracom account, please contact us and submit an application with the following information:

• Your Soracom Operator ID
• The Soracom Air IoT SIM subscription(s) (such as plan01s) where you would like Test Mode enabled
• Your preferred data, SMS, and time limits
• The status to apply once Test Mode limits are exceeded

We are pleased to announce that the following actions have been added to the Soracom User Console:

• Send command via HTTP/S
• Send command via SSH

Traditionally, sending cloud-to-device data or commands via IP communication has been difficult due to firewall and routing restrictions that require complicated network configurations or device-side applications.

These new actions are based on the previously announced Downlink HTTP and SSH APIs and allow you to send HTTP/HTTPS requests or SSH commands to your device and view the response from a device directly from the User Console

To use these actions, simply select a SIM, click Actions, select Send command via HTTP/S or Send command via SSH, and enter the command details.

Please note: Pricing for these actions is scheduled to be announced in June 2025. Until then, these actions are free to use.

For more information, please see the Remote Command documentation.

We have released a new Soracom Cloud Camera Services (SoraCam) Network Diagnostic Tool to help you quickly check if your network is ready to support SoraCam.

Until now, making sure that your Wi-Fi network meets the necessary requirements for SoraCam required some technical know-how and manual testing, as described in the 3 Key Points to Check When Connecting SoraCam via Wi-Fi (Japanese) documentation.

Now, with this new tool, anyone can easily run a quick check. Just connect your smartphone or PC to the network you plan to use, open the SoraCam Network Diagnostic Tool (Japanese), and click the button to start the test.

The tool will check:

• If there's enough upload bandwidth for cloud video recordings.
• If the required network ports are open for communication.

If the tool finds any issues, we recommend checking with your network administrator to make the necessary adjustments.

For any questions or assistance, feel free to contact Soracom Support.

We are pleased to announce that support for the following advanced AI models has been added to Soracom Flux AI Actions:

• Azure GPT‑4.1, GPT‑4.1-mini, and GPT‑4.1-nano
• OpenAI GPT‑4.1, GPT‑4.1-mini, and GPT‑4.1-nano
• Amazon Bedrock - Anthropic Claude 3.7 Sonnet

These models are available starting today and can be selected when configuring Soracom Flux AI Action settings.

Note that the Azure GPT-4.1, GPT-4.1-mini, GPT-4.1-nano, and Amazon Bedrock - Anthropic Claude 3.7 Sonnet models will consume a number of credits per request.

On the other hand, OpenAI GPT‑4.1, GPT‑4.1-mini, and GPT‑4.1-nano models allow for providing your own license (API key) and therefore do not consume credits.

The number of credits consumed per request for the newly supported models is as follows.

Model	Credits consumed per request
Azure OpenAI (GPT-4.1)	71 credits
Azure OpenAI (GPT-4.1-mini)	15 credits
Azure OpenAI (GPT-4.1-nano)	4 credits
OpenAI (GPT-4.1)	(*1)
OpenAI (GPT-4.1-mini)	(*1)
OpenAI (GPT-4.1-nano)	(*1)
Amazon Bedrock - Anthropic Claude 3.7 Sonnet	120 credits

(*1): These models allow you to use your own API key and therefore do not consume Flux credits.

For more information, see the Soracom Flux documentation.

Soracom Orbit is a bi-directional inline data processing service that allows you to write your own AssemblyScript, Rust, C/C++, or TinyGo function for modifying IoT device data as it is sent from or to a device and Unified Endpoint.

Previously, Orbit allowed for reading IoT SIM tags when executing your function. This lets you incorporate tag values into your function logic, such as appending the IoT SIM name to the data, or applying different data processing logic based on the value of a device model, firmware, or other tag.

With this update, Orbit now also allows for writing and deleting IoT SIM tags. This new functionality enables new use cases, such as updating an IoT device's tags based on the data it sends. You can then utilize existing User Console and Soracom API features such as searching for and sorting SIMs based on a specific tag to streamline SIM and device management workflows.

The Orbit SDKs have been updated for this new functionality. Below is a summary of updates for each SDK:

AssemblyScript SDK

• Added setTagValue(name: string, value: string): void
• Added deleteTag(name: string): void
• Added getOriginalRequest(): string

Rust SDK

• Added set_tag_value(name: &str, value: &str)
• Added delete_tag(name: &str)
• Added get_original_request() -> String

C/C++ SDK

• Added void soracom_set_tag_value(const char* name, const char* value)
• Added void soracom_delete_tag(const char* name)
• Added int32_t soracom_get_original_request_as_string(const char** buf, size_t* siz)
• Added void soracom_release_buffer(const char* buf)
• Deprecated void soracom_release_input_buffer(const char* buf) (use soracom_release_buffer() instead)
• Deprecated void soracom_release_userdata(const char* buf) (use soracom_release_buffer() instead)

TinyGo SDK

• Added func SetTagValue(name string, value string)
• Added func DeleteTag(name string)
• Added func GetUserdata() ([]byte, error)
• Added func GetOriginalRequest() ([]byte, error)

For additional details, refer to the Orbit: SDK Reference documentation.

We have expanded the set of characters that can be used when sending SMS messages to devices from the Soracom User Console or using the Soracom API/CLI.

Previously, when specifying GSM-7 (GSM 7-bit default alphabet) encoding, SMS messages only supported characters in the GSM-7 Basic Character Set. With this update, SMS messages can now include additional characters such as {, }, [, ], |, ^, and ~. The full list of supported characters is shown in the two tables below.

GSM-7 Encoding Basic Character Set

These are standard characters that are transmitted using 7 bits per character.

	0x0_	0x1_	0x2_	0x3_	0x4_	0x5_	0x6_	0x7_
0x_0	@	Δ	SP	0	¡	P	¿	p
0x_1	£	_	!	1	A	Q	a	q
0x_2	$	Φ	"	2	B	R	b	r
0x_3	¥	Γ	#	3	C	S	c	s
0x_4	è	Λ	¤	4	D	T	d	t
0x_5	é	Ω	%	5	E	U	e	u
0x_6	ù	Π	&	6	F	V	f	v
0x_7	ì	Ψ	'	7	G	W	g	w
0x_8	ò	Σ	(	8	H	X	h	x
0x_9	Ç	Θ	)	9	I	Y	i	y
0x_A	LF	Ξ	*	:	J	Z	j	z
0x_B	Ø		+	;	K	Ä	k	ä
0x_C	ø	Æ	,	<	L	Ö	l	ö
0x_D	CR	æ	-	=	M	Ñ	m	ñ
0x_E	Å	ß	.	>	N	Ü	n	ü
0x_F	å	É	/	?	O	§	o	à

LF, CR, and SP represent the following control characters (with their Unicode code points):

• LF: Line Feed (U+000A)
• CR: Carriage Return (U+000D)
• SP: Space (U+0020)

GSM-7 Encoding Basic Character Set Extension

Note that these characters are sent using 14 bits per character (escape sequence 0x1B + extended character).

	0x0_	0x1_	0x2_	0x3_	0x4_	0x5_	0x6_	0x7_
0x_0					|
0x_1
0x_2
0x_3
0x_4		^
0x_5							€
0x_6
0x_7
0x_8			{
0x_9			}
0x_A	FF
0x_B
0x_C				[
0x_D				~
0x_E				]
0x_F			\

• FF represents the form feed character (U+21A1).

Please note that the interpretation and display of these characters on the device receiving the SMS message may vary depending on the device's implementation.

If you need to send characters that are not listed in the tables, consider using UCS-2 encoding.

We are excited to announce three new functions for customizing the output behavior of Flux Actions: Transform Data, Send event for each, and Delay.

Transform Data

The Transform Data function lets you customize the format of the data that will be sent to the next Flux channel, using data from both the action input and the action result. This allows you to remove any data in the action result that is unnecessary, as well as pass along data that was part of the original action input.

Send event for each

If data in an action result contains a JSON array, the Send event for each function lets you repeat subsequent actions for each item in the array. This allows you to generate multiple events from a single action, passing each item of the array as the action input data to the next Flux channel.

Delay

The Delay function allows you to set a duration (in seconds) that an action should wait before sending data to another channel. This allows you control of the timing of specific behavior, such as to ensure one action completes before another, or to adhere to rate limiting.

For more information, please refer to the Flux Action Output: Advanced Settings documentation.