What Trivela Link is

Trivela is the account a GOALS player uses across the community’s services. Trivela Link is how your service plugs into it. Once a player has connected your service, you can send what you know about them to their Trivela profile, and read what other services have sent — with the player deciding what is shared where.

  your service                     Trivela                    other services
  ────────────                     ───────                    ──────────────
  1. set up the link  ──────────▶  one profile per player
  2. send data        ──────────▶  holds each value once  ◀──  they send theirs
  3. read data        ◀──────────  shares what the player  ──▶  they read yours
                                   has switched on

Three things to build, in order:

1. Link the account — a player presses a button on your site, confirms on Trivela, and comes back. You store their Trivela id. One handshake, four calls.
2. Send data — put what you hold about them in avalues object — any field in the catalogue you are the source of. Trivela keeps one copy per player and knows it came from you.
3. Read data — ask about a player and get back what they have chosen to share with you from everywhere else, ready to display.

The player owns the profile. Two services can send a value for the same field; Trivela keeps both, and the player picks which is the truth — and which services may see it — on their Trivela account page. What you read is that choice, not whoever wrote last.

Sending and reading are the same call — POST /api/link/status — so most services need to build very little. The API reference has every field and every error string once you are past the shape of it.

What it is not. Not OAuth — no scopes, no token for the user, and Trivela never sees your credentials. Not a feed — nothing is pushed to you except a nudge to re-read. Not a lookup service — every call is about a user you already hold, and a user who is not yours looks identical to one who never linked.