Connect your LookinBody Web account

• An active LookinBody Web subscription.
• An approved API key, generated from your LookinBody Web setup menu.
• An Eco Systems account with owner access.

1. Open the integration screen. Sign in to the Eco Systems portal as the owner and go to Settings > InBody / Scan station.
2. Allowlist our API address, then enter the account ID and API key. LookinBody only accepts API calls from addresses on your account's allowlist, and requires the list before it will save a key. In LookinBody Web, enter the Eco Systems API address in Step 2: IP Whitelist. Then paste your account ID and API key into the portal. The key is write-only: masked after saving and never displayed again.

   Eco Systems API address: 134.199.179.62 (enter as 134.199.179.62 or 134.199.179.62/32). This single static address is the only source of LookinBody API calls from Eco Systems. Nothing else is needed.

3. Run the connection test. Press Test LookinBody connection. The portal calls the LookinBody test endpoint with your saved credentials and reports success, or the reason it failed. A refusal usually means the API address is missing from your allowlist.
4. Register the webhook. Set a webhook key in the portal. The portal shows your webhook URL; add that URL with your key in LookinBody Web so completed tests notify the platform automatically.
5. Map each device to a location. Multi-site facilities enter each InBody unit's serial number against the store it lives in, so results are attributed to the right site. Single-site facilities can skip this.
6. Verify with one test. Run a scan on a member whose phone number matches their Eco Systems record. The result should appear on that member's profile, and on the in-store display, within seconds.

Once the connection is live, a completed test notifies the platform and the result is fetched and stored against that member. Four things follow, within seconds and without staff input:

• The result lands on the member record, alongside their previous scans.
• Points are awarded for the scan.
• The leaderboard updates.
• The result appears on the in-store display.

Members are matched on phone number. The single most common cause of a missing scan, by a wide margin, is that the phone number entered on the InBody device does not match the number on the member's Eco Systems record.

Your support is handled by Eco Systems directly, at the address on our contact page. We escalate to InBody only where the issue is on the LookinBody Web side, such as API access or subscription state.

• Credentials are write-only. Your LookinBody API key and webhook key are masked after saving, never logged, and stored only in your own business's database, never exposed to another client.
• One database per client. Each business's data is physically separate. There is no shared scan table, so cross-client access is not possible by construction.
• No aggregation, no resale. Scan data serves only your own members. It is not aggregated across clients, sold, or shared with third parties.
• Transport. All traffic is HTTPS. The ingest webhook requires a per-client shared secret, and posts without it are rejected. Outbound calls to the LookinBody API come only from the single Eco Systems API address in step 2.