Configuration with a custom server
o configure the Efento LTE Gateway to send data to a custom server, use the free Efento mobile application for Android or iOS.
Configure the Gateway
The gateway’s configuration is split into five tabs (you can switch the tabs by selecting them from the upper bar):

Network Parameters:
APN (Access Point Name): Enter the APN provided by your SIM card provider. If login and password are required, check “Use username and password,” or select “Automatic” to use the default APN.
PLMN (Public Land Mobile Network): Enter the unique code for your mobile network or select “Obtain automatically.”
DNS (Domain Name System): Set the address of the DNS server. By default it is set to 8.8.8.8
NTP (Network Time Protocol): Set the address of the NTP server. By default it is set to pool.ntp.org
Server settings:
Server address: Address of the server to which the Gateway sends the data. Both IP and domain address are accepted
Server port: Port to which the data is sent
TLS: Enable or disable secure communication between the Gateway and the server. We strongly recommend enabling TLS to ensure secure, encrypted data transmission and protect your infrastructure from unauthorized access. If required, you can add custom CA certificates.
Organization token: Optional API token sent to the server in HTTP header by the Gateway along with the data.
Configure optional parameters:
Custom Heartbeat endpoint: The Efento Gateway can send heartbeat messages to a user-defined endpoint at regular intervals. These messages allow the server to monitor the gateway’s status, including whether it is online, its uptime, battery status, and the number of loggers within range. Specify the endpoint where the messages should be sent. By default the heart beat messages are sent to /api/v2/gateways/heartbeat. The structure and details of the heartbeat message payload are described in the API Documentation section of this manual.
Custom API endpoint: By default, the Efento Gateway sends measurements to the /api/v4/measurements endpoint. If needed, you can override this and specify your preferred endpoint address.
Custom headers:
By default, the Efento Gateway includes the value from the “Token” field in the HTTP "X-Api-Token" header. The default headers are:
Content-Type: application/json charset=UTF-8 X-Api-Token: <value of the “Token” field>If needed, you can configure the gateway to use custom headers that will overwrite the default "X-Api-Token" header. To do this, enable the “Custom headers” toggle and add the desired header names and values. You can define up to ten custom headers, which will be sent in the same order as they appear in the list. The headers “Content-Type” and “charset” are always included automatically.

Verify the connection
After saving the settings, the gateway will attempt to connect to the server. You can verify the current network and server communication status in Status (three dots in the upper-right corner → Status). The Registration status should show REGISTERED or REGISTERED_ROAMING, and the Communication status should display Success.
Hands-on tutorial: Build a server for Efento Gateways
If you want to see a complete, working example of how to receive measurements from Efento Gateways and store them in a database, make sure to check out our step-by-step tutorial. It includes sample Python code, a simple server application, and instructions for saving incoming data to PostgreSQL - perfect as a starting point for your own integration.
Last updated
