An application programming interface, or API, provides a defined way for software systems to communicate. TWPRR™, the Worldwide Property Rights Registry, is being developed with a federated, API-first approach. APIs are the intended approach to connecting information across participating sources and systems while preserving the role of authoritative sources.
What an API does
When systems need to communicate, an API defines an interface through which information can be requested or exchanged. It gives a connection a defined form instead of depending only on people moving records manually.
The practical question is what information a connection supplies and how it helps answer the intended rights question. An interface does not itself determine ownership, permission, or authority.
What API-first means for TWPRR
API-first means the system connections are designed around those interfaces. Within TWPRR’s design, this approach is intended to support interoperability: systems exchanging and making use of information meaningfully.
This is an architecture direction. Specific interfaces, available integrations, access methods, and supported capabilities require approved technical definitions and a stated released scope. This page is an explanation, not an API reference or a promise of developer access.
A connection preserves source context
TWPRR’s federated approach is intended to connect information across participating sources and systems while preserving authoritative sources. The role of the source remains important when information is exchanged.
Who maintains a record, what it supports, and which conditions govern access affect how it should be understood. An API connection does not automatically change a source’s authority, make all records equally authoritative, or resolve conflicting information.
A membership example makes the connection practical
Imagine an association offering current members a benefit through a partner organization. The partner needs information relevant to whether a particular member holds the benefit required for a session.
In the intended API-first approach, a defined system connection could support exchange of relevant issuer information within the permitted scope. The partner still needs to understand the issuer, membership status, benefit rules, and applicable conditions. This hypothetical example does not imply a released TWPRR endpoint, live integration, or automatic verification.
Relationships and evidence explain the information
The Rights Graph™ is the relationship structure connecting rights-related objects, parties, evidence, and other relevant elements. It helps explain how information relates to an asset, right, holder, intended action, and conditions.
The Trusted Evidence Chain™ is the evidence and provenance concept used to connect and support rights-related proof. Provenance means the source and history of information. These concepts provide context for examining what information exchanged through a connection supports.
Authority and access need a defined purpose
An institutional connection needs clarity about who may provide, access, use, or disclose information and for what purpose. Identity alone does not establish authority to act for an organization or release its records.
Privacy, confidentiality, jurisdiction, source responsibilities, and disclosure conditions need attention in the relevant implementation. Marketing contact data is separate from authoritative rights data. Permission to receive educational updates is separate from permission to disclose supporting records.
Begin with the integration question
Identify the source or system your organization maintains. Describe the rights-related relationship you want to make more useful, the intended action, and the information another participating party would need to understand.
Clarify source responsibilities, authority, permitted access and use, information boundaries, and evidence context before discussing an integration. Technical discussions can then address the approved interface and the released capability relevant to that purpose.
Availability follows released capabilities
UREWPS is developing TWPRR and related capabilities in stages. The planned direction begins with ownership search for some asset types, expands coverage, and later supports asset recording in the database and subsequently blockchain recording as appropriate.
Each released capability needs a stated scope, sources, coverage, access conditions, and limitations. This page does not establish API availability or operational coverage of every asset category. Exchanging, connecting, or recording information does not automatically verify ownership, permission, authority, or legal validity. Defined connections can support understanding and responsible participation in the broader Rights Economy™.
Common questions
What does API stand for?
Application programming interface: a defined way for software systems to communicate.
What does API-first mean?
Connections are designed around those interfaces. Within TWPRR, this is the intended approach to participating system connections.
Is this developer documentation?
This is an educational architecture page. Technical interfaces, access methods, and implementation details require approved documentation for a released capability.
Does an API connection grant permission?
Authority, access, use, and disclosure conditions still apply. A connection does not automatically establish permission or verified rights.
Can my organization connect today?
Operational availability depends on released capabilities. Identify the intended use and relevant source, then review the stated scope, access conditions, and available integration documentation.