Why are multiple user_ids created for one reference_id?

Each Terra user_id represents a single user-provider connection, and every data request is scoped to one user_id (one call returns one provider's data).

Each Terra user_id represents a single user-provider connection, and every data request is scoped to one user_id (one call returns one provider's data).

reference_id is purely metadata to help you reconcile users on your side. It carries no dedup logic, so reference_id + provider does not guarantee a unique record. A previous user_id is only replaced (via a reauth event) when the same provider account is authenticated again under the same developer ID.

Two active connections sharing a reference_id and provider but with different user_ids usually means the user connected from two different devices or accounts.

To combine providers for one end user:

• Make separate calls per user_id.

• Map them via the reference_id supplied at authentication.

Filtering below the data-type level must be done in your own application logic.