Setup documentation
Connect your LookinBody Web account
This is the process your facility follows to connect its own LookinBody Web account to Eco Systems, so completed InBody tests land on the right member record without anyone retyping them. It is self-service: no InBody credentials are shared between facilities, and none are handled by Eco Systems staff.
01 / Before you start
What you need
- An active LookinBody Web subscription.
- An approved API key, generated from your LookinBody Web setup menu.
- An Eco Systems account with owner access.
Be clear on the subscription. The LookinBody Web API is a paid InBody service and the subscription is yours, not ours. Eco Systems does not resell it, and cannot generate an API key on your behalf: you create it in your own LookinBody Web account and paste it into your portal.
02 / The steps
Six steps, once
- Open the integration screen. Sign in to the Eco Systems portal and go to Settings > Integrations > InBody.
- Enter the LookinBody account ID and API key. Both are stored encrypted and are never displayed again after saving.
- Run the connection test. The portal calls the LookinBody connection endpoint and confirms success before saving. A failure reports the reason rather than saving a broken connection.
- Register the webhook. The portal displays your webhook URL and shared secret. Add these in LookinBody Web so completed tests notify the platform automatically.
- 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.
- 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.
03 / After a scan
What happens when someone tests
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.
04 / If something looks wrong
Troubleshooting
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.
| Symptom | Cause and resolution |
|---|---|
| Scan does not appear | The member's phone number on the InBody device does not match their Eco Systems record. Members are matched on phone number. Correct it and rescan. |
| Results appear for the wrong site | The device serial is not mapped. Add it under the integration screen. |
| Connection test fails | Usually an expired or regenerated API key, or a lapsed LookinBody subscription. The error message names which. |
| Nothing arrives at all | The webhook is not registered in LookinBody Web, or the shared secret was changed on one side only. |
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.
05 / Security
How your credentials and your data are held
- Credentials are write-only. Your LookinBody account ID and API key are stored encrypted, never displayed after saving, never logged, and 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, and the ingest webhook requires a per-client shared secret. Unauthenticated posts are rejected.
06 / Questions
Straight answers.
Do I need my own LookinBody Web subscription?
Yes. The LookinBody Web API is a paid InBody service, and the subscription is yours, not ours. You generate the API key from your own LookinBody Web setup menu, so no InBody credentials are ever shared between facilities or handled by Eco Systems staff.
Can anyone at Eco Systems see my API key after I save it?
No. Your LookinBody account ID and API key are stored encrypted, never displayed again after saving, never logged, and never exposed to another client. If you need to change them, you enter the new values rather than reading back the old ones.
A scan did not show up. What do I check first?
The phone number on the InBody device. Members are matched on phone number, so a number that does not match their Eco Systems record is by far the most common cause. Correct it and rescan.
Who do I contact if setup fails?
Eco Systems handles your support directly, at the contact address on our site. We escalate to InBody only where the issue is on the LookinBody Web side, such as API access or subscription state.