Open APIs

Dear Community,

I am seeking clarification on the best practices for linking a PartyRole (TMF669) with a PartyAccount (TMF666). According to the TMF669 specification, a PartyRole can reference zero or more AccountRef objects.

I am considering two approaches for creating a relationship (e.g., a "signer" or "administrator" role for a specific account):

1. Account-Centric (Method A): POST/PATCH to the relatedParty property on the PartyAccount resource. In this case, should the backend service automatically update/populate the account property on the corresponding PartyRole?

2. Role-Centric (Method B): POST/PATCH the PartyRole resource directly with the account reference. Is this considered a valid implementation of the mapping according to the SID model?

Additionally, I would appreciate your insights on the lifecycle management of the partyRole.account reference. Is it common practice to maintain these as bi-directional links in the API layer, or should one resource (e.g., PartyAccount) act as the "Source of Truth"?

Thank you for your expertise!

Hi Calin MARIAN

My Take:

Party / PartyRole should act as the system of record, as an Account has no standalone business meaning without an associated Party. Once an Account exists, it can establish relationships with other Parties, each assigned a specific role (e.g., moderator, joint owner).

Thanks