Kleber connector — overview
The Kleber connector is Ark's address connector. It exposes Ark's address API — autocomplete and metadata lookup — and fulfils each call against the Kleber (DataTools) address service over SOAP, backed by the Australia Post PAF (Postal Address File).
It is a thin, stateless proxy + mapper: it holds no database, stores no lookup history, and exists largely to keep the Kleber credentials server-side and to translate Kleber's XML into Ark's common address schema.
What it does
| Capability | Endpoint | Notes |
|---|---|---|
| Autocomplete search | GET /v1/address/autocomplete?query= | Free-text suggestions; query needs ≥ 4 alphabetic characters |
| Address metadata | GET /v1/address/metadata?id= | Full structured PAF detail for a selected suggestion |
The typical flow is two calls: autocomplete returns a list of suggestions each with an id, then
metadata resolves one id to a full address. See endpoints for how to call
them.
Shape
- Stateless. No database, no
lifecycle— there is no resource that lives across calls. Each request is a single SOAP round-trip and mapping. - REST in, SOAP out. Ark callers use REST/JSON; the connector wraps Kleber's single SOAP operation, exposing autocomplete and metadata over it.
- Billed per request. Kleber charges per call, which shapes how the health probe is wired (see the connector notes).
Where to read next
| You want… | Doc |
|---|---|
| How to call the API | endpoints (non-dev) |
| How it's built and the per-endpoint internals | architecture (dev) |
| How to build, run, test, and regenerate clients | development (dev) |
| Quirks, gaps, and provider caveats | notes (dev) |
The formal request/response contract is the connector's OpenAPI specification (the Address API,
openapi/source/connector/address/address.yml); this doc set does not restate it.