description: TrustNet reference: endpoints, discovery, scopes, claims, errors and generated API contracts.
Reference
The reference section is the exact contract for RP integrators. The API pages are generated from the OpenAPI documents in the product repository on every build, so a spec change in the same commit changes the published reference.
- Endpoints and discovery — the OIDC, machine-plane and portal surfaces, with parameters and response shapes.
- Scopes and claims — the requestable claim catalog and the scope model.
- Error codes — the closed error sets for each surface.
- RP machine plane API — generated from
rp.yaml. - RP portal API — generated from
rp-portal.yaml. - Changelog and deprecation policy.
Discovery
https://id.trustnet.app/.well-known/openid-configuration
Use discovery as the source of endpoint URLs and capabilities. The issuer is
permanent: https://id.trustnet.app.
!!! note "claims_parameter_supported"
The discovery document advertises claims_parameter_supported: false
because the protocol layer does not interpret the parameter. TrustNet does
parse the standard claims request parameter from the authorization
request. Send it; it is how per-claim requests work.
Support, status and security
| Need | Where |
|---|---|
| Contact (support, incidents and general enquiries) | privacy@trustnet.app |
| Security vulnerability disclosure | TrustNet security disclosure |
| Machine-readable security contact | https://trustnet.app/.well-known/security.txt |
| Service status | No public status page is published yet. Report an incident through the contact address. |
Versioning
The docs cover a single latest version. Versioned documentation archives are
deferred until the first breaking API change. The API version is in the path
(/api/rp/v1, /api/v1/rp); see the changelog for the
deprecation policy.