Terra

Integration

API
Unified API
SDK
SDK
Authentication
Authentication
Streaming
Streaming
Blood
Blood Report API
Planned Workout
Planned Workout
AI Interface
AI Interface

User engagement

Graph API
Graph API
Scores
Health Scores
Rewards
Health Rewards

Use cases

Enterprise
Enterprise
Insurance
Insurance

Developers

Wearable Data
Wearable Data
Community
Community
Documentation
Documentation

Learn

Blog
Blog
Podcast
Podcast
Events
Events
Reports
Reports

Company

Customers
Customers
Careers
Careers
Partners
Partners
Support
Support
Become an integration
Become an integration


Cookie Preferences

Essential CookiesAlways On
Advertisement Cookies
Analytics Cookies

Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.

zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

In my terra dashboard, i have 2 users with same reference id. both are from same provider - apple. Is is possible? How to stop it from happening?

All

GiantHeron9 months ago

In my terra dashboard, i have 2 users with same reference id. both are from same provider - apple. Is is possible? How to stop it from happening?

terra

Vanessaadmin8 months ago

hi !

Thanks for flagging this.

Here is what happened, it’s quite an edge case but can be easily avoided moving forward:

While rebuilding the app locally during testing (common with React/Flutter), Apple assigns a new vendor ID for the same device.

Each new vendor ID looked like a new connection to Terra API (even though the reference ID was the same). That’s why you saw multiple active connections.

How to avoid this:

Use Terra’s testing/staging environment during app builds → capped at 50 connections, so you’ll never get overcharged :)