HTTP Entry Point

This entry point accepts HTTP requests from an Air for Cellular device and forwards the request to the forwarding destination via HTTP or HTTPS. You can create multiple HTTP entry point configurations, provided the path parameter is unique for each configuration.


Entry Point

Your device should be configured to send data to:{my-custom-path}.


Refer to the Header Manipulations documentation for additional details.


Request Behavior

When Beam receives an HTTP request, it will close the original request and forward the request to the forwarding destination.

Response Behavior

When Beam receives an HTTP response from the forwarding destination, it will transfer the response directly to the device.


$ curl -v -X POST -H 'Content-Type: application/json' -d '{"key":"value"}'
>*   Trying
>* Connected to ( port 8888 (#0)
>> POST / HTTP/1.1
>> Host:
>> User-Agent: curl/7.49.0
>> Accept: */*
>> Content-Type:application/json
>> Content-Length: 15
>* upload completely sent off: 15 out of 15 bytes
>< HTTP/1.1 200 OK
>< Content-Type: application/json
>< Date: Wed, 21 Dec 2016 02:25:01 GMT
>< Connection: close
>< Transfer-Encoding: chunked
>* Closing connection 0

Advanced Configuration

The HTTP entry point can also be configured through the Soracom API or CLI by using the SoracomBeam namespace.

Configuration should be performed using as the configuration key value.



    "key": "",
    "value": {
      "name": "My Beam config",
      "destination": "",
      "enabled": true,
      "addSubscriberHeader": true,
      "addSimIdHeader": true,
      "addMsisdnHeader": true,
      "customHeaders": {
        "X-Group-Name": {
          "action": "replace",
          "headerKey": "X-Group-Name",
          "headerValue": "My header value"
      "addSignature": true,
      "psk": {
        "$credentialsId": "CredentialsID"
      "addAuthorizationHeader": {
        "enabled": false