Sending values

Last updated 2 September 2026.

You send data by putting a values object on your link/status call. Each key is a field from the catalogue; Trivela files what you sent on the player’s profile as your claim about them.

POST /api/link/status
{
  "subject": "u_8f31c2",
  "values": {
    "nationality": "se",
    "playstation": "Coach_77",
    "club": { "id": "b3c1a708", "name": "ThePretorians", "slug": "thepretorians", "sr": 1678, "rank": 4,
              "wins": 395, "losses": 253, "matchesPlayed": 648 }
  }
}

A claim, not a write

Two services can both send a value for the same field — you hold one answer, another service holds a different one. Trivela keeps both, each under the service that sent it, and the player chooses which is the truth on their Trivela account page. That choice, not who sent last, is what other services are shown.

So sending never overwrites another service’s value and never overwrites the player’s choice. You are adding your answer to a list the player controls. Send what you actually hold and let the rest be settled at the account page. A service that is the only source of a field is simply the only entry in that list.

Three things you can say about a field

You sendIt means
no values at allI did not look. Nothing changes. Send this when your own lookup failed — a database blip is not evidence the player holds nothing.
"field": nullI looked and hold nothing. Withdraws your claim. Never deletes anyone else's, never deletes the player's choice.
"field": "…"This is what I hold.

The difference between the first two is the whole safety of the protocol. A service that sends null whenever it fails to look would withdraw a true claim on every outage.

Fields that are objects

Most fields are a single string. A few are objects — an identity plus a record that changes often, carried together so the two cannot disagree. Those are an allow-list of named keys, an unknown key is a 400, and they never carry URLs: readers compose their own links from the identifiers. Which fields, and their exact keys and bounds, are in the catalogue.

Rules

  • Only fields you registered to send. Anything else is a 400, and a 400 rejects the whole call — nothing in it is applied, and the error names the field.
  • Send your own value, never one you read from Trivela. If you display a value Trivela gave you, sending it back files it as your claim too, and the player sees their own choice twice under two names.
  • Only when the player is there. Send from settings and profile pages the player is on, not when a visitor views them. Reading is fine from anywhere; sending is a statement you make on the player’s behalf.
Check the catalogue’s bounds before you send and turn anything that fails into null. A value Trivela refuses costs you the call, and the call is also how you learn whether the player is still linked.