#Setup

Endpoint: POST /v1/{target}/resource-api/services/create | API Reference

#Example Request

curl -X 'POST' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/resource-api/services/create' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "type": "trust-registry",
  "sourceAcceptancePolicy": "REQUIRE_VALID_SIGNATURE"
}'

Path Parameters

• orgID: String - Your organization's Base URL prefix, e.g. myorg.enterprise-sandbox.waltid.dev.
• target: String - The target path for the new service: {organizationID}.{tenantID}.{serviceID}, e.g. myorg.tenant1.trust-registry.

Header Parameters

• Authorization: String - Bearer token for your organization.

Body

• type: String - Must be trust-registry.
• sourceAcceptancePolicy: String (optional) - Default admission policy for newly loaded sources. Defaults to REQUIRE_VALID_SIGNATURE. See Acceptance Policies.
• trustedSourceSignerCertificates: Array of strings (optional) - PEM or Base64-DER certificates or trust anchors authorized to sign XMLDSig TSL and compact-JWS LoTE sources. Configure them independently from the loaded artifact.
• validateSignaturesByDefault: Boolean (legacy, optional) - Compatibility setting for existing configurations. Prefer sourceAcceptancePolicy for new services.
• autoRefreshIntervalSeconds: Integer (optional) - Stored for compatibility, but no background refresh scheduler currently uses it. Refresh sources explicitly through the refresh endpoint.

#Example Response