TRIDENT Opens for Early Integration
Government agencies and approved organisations can now explore TRIDENT APIs and build integrations in a controlled environment, ahead of formal approval for production.
The TRIDENT Testing Sandbox is open.
Government agencies and approved organisations can use it to explore available APIs, work through integration patterns, and understand how trusted identity capabilities fit their own services, before committing to a design or a timeline.
It is a place to learn, build and test. Nothing in it touches live services or real citizen data.
What teams can do there
Review the APIs currently exposed and the integration approaches available. Try out how authentication, electronic signing, verified identity data and credential capabilities behave in practice. Identify dependencies and implementation considerations early, while they are still cheap to address.
The point is to answer the questions that only surface once someone actually builds something.
Where it sits in the path
The Testing Sandbox is where integration work happens: exploring, building and validating against the real capabilities. What follows isn't another environment, it's approval. Before a service can operate with real citizens, the organisation must be formally registered as a relying party, with its purpose and permitted capabilities defined.
Getting access
Access is granted rather than self-service. Government agencies and organisations should first contact the TRIDENT ID Project Team, which enables access for approved participants.
Once enabled, technical documentation, integration guidance and the available APIs are published in the TRIDENT Integration Portal.
What comes after the Testing Sandbox?
The article Connect to TRIDENT sets out the full path from first exploration to a live service. APIs and documentation are in the TRIDENT Integration Portal.