v1.0.24

terms_signed_at is now returned on Customer GET endpoints

The following endpoints now include a terms_signed_at field in the response, indicating when the customer accepted the Terms of Service. The field is omitted when the customer has not signed yet.

• GET /v1/customers — field added to each item in customers[] (endpoint page)
• GET /v1/customers/{customer_id} — field added to the response (endpoint page)
• POST /v1/customers — field added to the response (endpoint page)
• PUT /v1/customers/{customer_id} — field added to the response (endpoint page)

Example response:

{
  "customer_id": "550e8400-e29b-41d4-a716-446655440000",
  "email": "[email protected]",
  "status": "PENDING_REVIEW",
  "terms_signed_at": "2026-04-15T10:00:00.000000Z", // ISO 8601, UTC
  "...": "..."
}

terms_signed_at can now be updated via PUT

The PUT /v1/customers/{customer_id} endpoint now accepts an optional terms_signed_at field in the request body, allowing you to update the Terms of Service acceptance timestamp after the customer has been created.

Example payload:

{
  "terms_signed_at": "2026-04-15T10:00:00.000Z"
}

Note: only allowed for entities using the Reliance model. Timestamp must not be in the future.

🔄 Backwards compatibility

All changes are additive and do not break existing integrations:

• Clients that ignore the new terms_signed_at field continue to work as before.
• The field is optional in every request — no existing payload needs to be changed.