UDA endpoints
How to call the connector, grouped by resource. The formal schema is the OpenAPI specification under
openapi/source/connector/; these pages are the call contract. Internal processing is in
the architecture reference; caveats in the implementation notes.
Authentication & context
All /v1/* business routes require a bearer token (OAuth2 client-credentials JWT). Most also require
party context (partyId), which the connector uses to resolve the customer in ULTRACS. Health
endpoints are unauthenticated probes; GET /health runs a (heavy)
ULTRACS reachability check, while /health/readiness and /health/liveness return 204
(see the architecture reference).
{accountId}, {cardId}, etc. in paths are Ark ids, not ULTRACS ids.
Resource groups
| Group | Path prefix | Page |
|---|---|---|
| Accounts | /v1/accounts | accounts |
| Cards | /v1/cards | cards |
| Parties | /v1/parties | parties |
| Payments | /v1/payments | payments |
| Payees | /v1/payees | payees |
| Statements | /v1/parties/statements | statements |
| Products | /v1/products | products |
| Admin | /admin/mapping | admin |
Errors
Errors use the domain-coded ErrorResponse envelope (ACC*, PAR*, PAY*, GEN*). Each group page
lists the codes it raises. Note two cross-cutting behaviours: an ULTRACS fault with no mapping surfaces
as 500 (see the implementation notes), and "customer not found" is handled
inconsistently across groups (see the implementation notes).