Connect to TRIDENT: Turn Shared Capabilities into Better Services
Government entities and participating organisations can use TRIDENT APIs, guidance and integration resources to bring trusted identity into their own services.
Knowing what TRIDENT offers is one thing. Getting a working service connected to it is another.
The path from idea to live service is deliberately structured, so teams can explore and build early, while the decisions that matter, what a service is allowed to do with national identity, happen formally and on the record.
The same path applies whether it's a ministry moving an application process online or a bank connecting its customer onboarding.
It starts with the service, not the technology
The first question isn't which API to call. It's what the service actually needs to do: confirm who someone is, let them sign in, receive verified details, capture a signature, or check a credential.
Most services need one or two of those, not all of them. Starting from the business need keeps the integration proportionate to the problem.
Explore before committing
The Integration Portal is open for teams to look through: available APIs, technical documentation, integration guides, authorisation mechanisms and the scopes that define what a connected service can request.
This is where a technical lead can judge the effort involved before anyone commits to a timeline.
Build and validate in a test environment
Institutions and organisations can register for TRIDENT's testing environment, where developers integrate their own applications, systems and processes against the real capabilities without touching anything live.
Integration is a process rather than a single connection. Teams build, test, find the gaps between how they assumed a journey would work and how it actually behaves, and adjust.
Register formally to go live
Production is a separate step, and a formal one. Before operating with real citizens, an organisation must be registered as a relying party in the TRIDENT ecosystem: an approved participant, with its purpose, permitted capabilities, scopes and endpoints defined and recorded.
Participation is approved, not open by default. That's what allows a citizen to trust that a service asking for their identity has been authorised to do so.
Then keep going
A first integration is rarely the last. Teams that connect one service typically reuse what they learned for the next, and new capabilities, credentials and use cases are added to the framework as the ecosystem grows.
Throughout, the service stays yours. TRIDENT provides trusted identity outcomes. Whether a citizen qualifies, what happens next, and how the process runs remain entirely with the organisation that owns the service.
Not sure which capabilities your service needs?
The article Building Blocks: What Services Can Use from TRIDENT sets out each capability and how services combine them. Technical documentation and APIs are available in the TRIDENT Integration Portal.