Trust & Schema Governance
What is the Trust Registry?
Section titled “What is the Trust Registry?”The Trust Registry is the root of trust within a TCS deployment. Before an organization can issue or verify credentials in that deployment, it must register and receive an approved identity. This ensures every credential traces back to a known, registered entity within the deployment — eliminating anonymous issuance.

TCS operates a scoped issuer allowlist: each tenant (e.g. Turing Certs) is added to the allowlist on registration, and verifiers configured against the same Trust Registry will accept their credentials. This is intentionally a centralized governance model — it is not OpenID Federation, EBSI TIR, or an ETSI/eIDAS Trusted List. Cross-ecosystem trust (e.g. presenting a TCS-issued credential to a verifier in another ecosystem) bridges through the X.509 / x5c path with an externally-anchored CA — see Architecture & Security and the Standards Compliance.

When a verifier receives a credential, it checks the iss claim against the Trust Registry’s approved issuer list — ensuring every credential traces to an organization the registry lists.
Registration Flow
Section titled “Registration Flow”Step 1: Get an account
Section titled “Step 1: Get an account”To open an account, contact help@turingspace.co.
Your account comes with two distinct credentials, and they are not interchangeable:
- The API key — your normal means of authenticating as a machine, sent in the
X-API-Keyheader onPOST /v1/offersandPOST /v1/verifier/authorization-request. - Your account identifier (your account UUID or registered email) and password — exchanged for a short-lived access token used only for DID management (
POST /v1/auth/loginbelow, then/v1/did/*).
Step 2: Log In
Section titled “Step 2: Log In”Exchange your account identifier and password for an ES256-signed JWT access token, valid for one hour. The Trust Registry rate-limits this endpoint to 5 attempts per 60 seconds.
curl -X POST https://trust-registry.turingspace.co/v1/auth/login \ -H "Content-Type: application/json" \ -d '{ "identifier": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "password": "SecurePass123" }'Success (200 OK):
{ "access_token": "eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InRjcy10ci0xIn0.eyJzdWIiOiJmNDdhYzEwYi01OGNjLTQzNzItYTU2Ny0wZTAyYjJjM2Q0NzkiLCJ1c2VyX2lkIjoxLCJ0ZW5hbnQiOiJhY21lLXVuaXZlcnNpdHkiLCJpc19pc3N1ZXIiOnRydWUsImlzX3ZlcmlmaWVyIjp0cnVlLCJpc3MiOiJ0Y3MtdHIiLCJpYXQiOjE3MTk0MDAwMDAsImV4cCI6MTcxOTQwMzYwMH0.signature", "expires_in": 3600, "token_type": "Bearer"}Error (401 Unauthorized) — the identifier or the password is wrong:
{ "statusCode": 401, "message": "Invalid uuid or password"}An account that is not approved also gets 401, with the message Unauthorized.
| Parameter | Type | Required | Description |
|---|---|---|---|
identifier | string | Yes | Your account UUID or registered email |
password | string | Yes | Your account password |
Step 3: Create a DID
Section titled “Step 3: Create a DID”Create a new DID (Decentralized Identifier) anchored on the IOTA network. Send an empty body with your JWT in the Authorization header.
curl -X POST https://trust-registry.turingspace.co/v1/did \ -H "Authorization: Bearer eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InRjcy10ci0xIn0.eyJzdWIiOiJmNDdhYzEwYi01OGNjLTQzNzItYTU2Ny0wZTAyYjJjM2Q0NzkiLCJ1c2VyX2lkIjoxLCJ0ZW5hbnQiOiJhY21lLXVuaXZlcnNpdHkiLCJpc19pc3N1ZXIiOnRydWUsImlzX3ZlcmlmaWVyIjp0cnVlLCJpc3MiOiJ0Y3MtdHIiLCJpYXQiOjE3MTk0MDAwMDAsImV4cCI6MTcxOTQwMzYwMH0.signature" \ -H "Content-Type: application/json"Success (201 Created):
{ "did": "did:iota:0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890", "key_id": "did:iota:0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890#Xh5bQm4n0yJ2kVq8T1pWc7rLs3dZaE9gUoF6iK0jHvY", "public_key_jwk": { "kty": "OKP", "use": "sig", "key_ops": ["verify", "sign"], "alg": "EdDSA", "kid": "Xh5bQm4n0yJ2kVq8T1pWc7rLs3dZaE9gUoF6iK0jHvY", "crv": "Ed25519", "x": "11qYAYKxCrfVS_7TyWQHOg7hcvPapiMlrwIaaPcHURo" }, "private_key": "nwKZ3iFzL7pZJK5pPJ-8k9vXcL2vL7pZJK5pPJ-8k9s"}Error (401 Unauthorized):
{ "statusCode": 401, "message": "Unauthorized"}Error (403 Forbidden) — the account is not approved:
{ "statusCode": 403, "message": "User account is not approved"}Error (503 Service Unavailable) — this deployment has no IOTA connection:
{ "statusCode": 503, "message": "DID management requires an IOTA connection: IOTA is disabled in this deployment (IOTA_ENABLED=false)"}Error (500 Internal Server Error) — the DID could not be published on the IOTA network:
{ "statusCode": 500, "message": "Internal server error"}Step 4: Import an Existing DID (Alternative)
Section titled “Step 4: Import an Existing DID (Alternative)”If your organization already owns a DID anchored on the IOTA network, import it instead of creating a new one. This registers the DID in the Trust Registry without generating new key material.
curl -X POST https://trust-registry.turingspace.co/v1/did/import \ -H "Authorization: Bearer eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InRjcy10ci0xIn0.eyJzdWIiOiJmNDdhYzEwYi01OGNjLTQzNzItYTU2Ny0wZTAyYjJjM2Q0NzkiLCJ1c2VyX2lkIjoxLCJ0ZW5hbnQiOiJhY21lLXVuaXZlcnNpdHkiLCJpc19pc3N1ZXIiOnRydWUsImlzX3ZlcmlmaWVyIjp0cnVlLCJpc3MiOiJ0Y3MtdHIiLCJpYXQiOjE3MTk0MDAwMDAsImV4cCI6MTcxOTQwMzYwMH0.signature" \ -H "Content-Type: application/json" \ -d '{ "did": "did:iota:0x9876543210fedcba9876543210fedcba9876543210fedcba9876543210fedcba", "private_key": "nwKZ3iFzL7pZJK5pPJ-8k9vXcL2vL7pZJK5pPJ-8k9s" }'Success (201 Created):
{ "did": "did:iota:0x9876543210fedcba9876543210fedcba9876543210fedcba9876543210fedcba", "method": "IOTA", "status": "active"}Error (400 Bad Request) — the private key does not match a verification method of the DID, or the DID cannot be resolved on IOTA:
{ "statusCode": 400, "message": "The provided private key does not match any verification method in the DID Document"}A malformed private key returns 400 with Invalid private key format. A did that does not start with did:iota: returns 400 with DID must be a valid IOTA DID (must start with "did:iota:").
Error (403 Forbidden):
{ "statusCode": 403, "message": "User account is not approved"}Error (409 Conflict):
{ "statusCode": 409, "message": "This DID has already been imported"}Error (503 Service Unavailable) — this deployment has no IOTA connection:
{ "statusCode": 503, "message": "DID management requires an IOTA connection: IOTA is disabled in this deployment (IOTA_ENABLED=false)"}| Parameter | Type | Required | Description |
|---|---|---|---|
did | string | Yes | Fully qualified IOTA DID |
private_key | string | Yes | Base64url-encoded Ed25519 private key for the DID |
DID Management
Section titled “DID Management”You have two options for establishing your DID identity:
| Create (POST /v1/did) | Import (POST /v1/did/import) | |
|---|---|---|
| Use when | Starting fresh with no existing DID | You already own a DID on IOTA |
| Key generation | TCS generates the Ed25519 keypair | You supply the existing private key |
| Network interaction | TCS anchors a new DID document on IOTA | TCS verifies the DID exists on IOTA |
| Key custody | You receive and store the private key | You already hold the private key |
In both cases, the DID is registered in the Trust Registry and linked to your organization’s account. You use this DID as the issuer identity when creating credential offers.
Get your DID
Section titled “Get your DID”GET /v1/did returns the most recently created active DID of your account. Send your JWT in the Authorization header.
curl https://trust-registry.turingspace.co/v1/did \ -H "Authorization: Bearer <access_token>"Success (200 OK):
{ "did_url": "did:iota:0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890", "method": "IOTA", "status": "active"}Errors: 401 (Unauthorized) for a missing, invalid or expired token; 403 (User account is not approved); 404 (No active DID found for this account) when the account has no DID yet.
DID Configuration
Section titled “DID Configuration”The Trust Registry exposes a Well-Known DID Configuration endpoint for each tenant. This follows the DIF Well Known DID Configuration specification, allowing external parties to verify the link between your domain and your DID.
curl https://trust-registry.turingspace.co/.well-known/did-configuration.json/acme-universitySuccess (200 OK):
{ "@context": "https://identity.foundation/.well-known/did-configuration/v1", "linked_dids": [ "eyJhbGciOiJFZERTQSIsImtpZCI6ImRpZDppb3RhOjB4YWJjZGVm..." ]}Each linked_dids entry is a Domain Linkage Credential in JWT form, one per DID of the tenant. This endpoint is public and requires no authentication. Wallets and verifiers use it to confirm that a DID is controlled by the entity operating the domain.
Schema Registry
Section titled “Schema Registry”The Schema Registry serves VCT (Verifiable Credential Type) metadata for all credential types supported by TCS. It is a read-only discovery service — you query it to understand the structure of credential types before issuing or verifying them.

Both issuers and verifiers reference VCT metadata from the Schema Registry: issuers validate credential offers before issuance; verifiers understand credential structure during presentation verification. All credential types must be registered before issuance.
List Credential Types
Section titled “List Credential Types”GET /schemas returns a paginated list of credential types. It is public and requires no authentication.
curl "https://schema-registry.turingspace.co/schemas?status=active&limit=20"Success (200 OK):
{ "data": [ { "name": "University Degree", "type": "UniversityDegree", "version": "v1", "status": "active", "updated_at": "2026-01-15T08:00:00.000Z" } ], "meta": { "offset": 0, "limit": 20, "total": 1 }}| Query Parameter | Description |
|---|---|
offset | Number of records to skip. Default 0 |
limit | Maximum number of records to return, 1–100. Default 20 |
sort_by | updated_at or created_at. Default updated_at |
order | asc or desc. Default desc |
status | Filter by lifecycle status (for example active) |
type | Filter by credential type (partial match, case-insensitive) |
name | Filter by credential name (partial match, case-insensitive) |
An invalid query parameter returns 400.
Discover a Credential Type
Section titled “Discover a Credential Type”curl https://schema-registry.turingspace.co/schemas/TuringCerts_Standard_Credential/v2Success (200 OK):
{ "vct": "https://schema-registry.turingspace.co/schemas/TuringCerts_Standard_Credential/v2", "name": "Turing Certs Standard Credential", "description": "A general-purpose verifiable credential issued through the Turing Credential Service.", "status": "active", "use_case": ["professional_qualification"], "claims": [ { "path": ["credentialName"], "mandatory": true }, { "path": ["expiredTime"], "mandatory": false } ], "schema": { "type": "object", "properties": { "credentialName": { "type": "string" }, "expiredTime": { "type": "string", "format": "date-time" } }, "required": ["credentialName"] }, "updated_at": "2026-01-15T08:00:00.000Z"}Error (404 Not Found):
{ "statusCode": 404, "message": "VCT type metadata not found"}| Path Parameter | Description |
|---|---|
type | The credential type identifier (matches the vct field in issued SD-JWT VCs) |
version | The schema version, in the form v<N> (e.g., v2) |
What’s Next
Section titled “What’s Next”- Issuing Credentials — Issue SD-JWT credentials using your API key and DID
- Verifying Credentials — Verify credential presentations
- Authentication Reference — Understand all authentication patterns