# PEXA

**Canonical:** https://apis.io/providers/pexa/  
**Website:** https://www.pexa.com.au/  
**APIs profiled:** 5

PEXA (Property Exchange Australia) operates Australia's dominant Electronic Lodgement Network (ELN), the digital rail on which property is settled and title dealings are lodged with the state land registries. Where the Australian real estate value chain splits into a listings duopoly (REA Group and Domain) sitting over progressively privatised state land registries, PEXA occupies the transaction layer underneath both — electronic conveyancing, settlement funds movement, digital signing and lodgement — and e-conveyancing is now effectively mandated for most dealings in most Australian jurisdictions, making PEXA the closest thing in the property sector to a required, national, machine-readable rail. Its API posture is correspondingly unusual: PEXA publishes a genuine developer portal at developer.pexa.com.au with Swagger UI reference documentation and machine-readable OpenAPI/Swagger contracts for the Exchange, Projects, Notification (webhooks), Standalone Discharge and PEXA Plus Marketplace APIs, and the ARNECC Model Operating Requirements oblige it to offer API access to third parties on an equivalent basis. But that surface is not self-serve: PEXA states plainly that access to the Developer Portal and to test or production credentials is contingent on having signed PEXA's API Agreement, so a developer registers via a form, is validated and approved, signs an agreement, and is then issued OAuth 2.0 client credentials (or mutual TLS). RESO is absent — it is a North American MLS standard with no bearing on Australian e-conveyancing — so there is no RESO Web API or Data Dictionary certification here, and none should be expected. This is a well-documented, regulated, licensed-access API estate rather than an open one.

## Kin Score — 59.6 / 100 (strong)

Scored 2026-08-17 under rubric 0.11.0. Trend: flat (+0.0 from 59.6).

| Facet | Score |
|---|---|
| Discoverability | 92.6 |
| Contract Quality | 67.2 |
| Governance | 20.8 |
| Operational Transparency | 55.3 |
| Developer Ergonomics | 66.8 |
| Commercial Clarity | 52.6 |

## Agent readiness — 57.0 (agent-native)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| MCP Server | derived |
| Auth Clarity | yes |
| Idempotency | documented |
| Error Semantics | verified |
| OpenAPI Examples | verified |
| Rate Limit Signal | no |
| Event Surface Described | yes |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | yes |
| Agent Card | no |
| Dry Run Mode | no |

## APIs (5)

- **PEXA Exchange API** — The PEXA Exchange API covers key facets of PEXA Exchange e-conveyancing functionality — creating and updating workspaces, invitations, participants, land title references, docum...
- **PEXA Standalone Discharge Experience API** — An OpenAPI 3.1.0 experience API supporting consolidated standalone mortgage discharge, used by financial institutions discharging a mortgage outside of a full transfer workspace...
- **PEXA Plus Marketplace B2B API** — The PEXA Plus Marketplace B2B API exposes marketplace services to business partners — health check, title search ordering and billing — under the PEXA Plus product. Published as...
- **PEXA Notification Service [$]** — PEXA Notification Service [$] from PEXA — 6 path(s) described in OpenAPI.
- **PEXA Projects API** — PEXA Projects API from PEXA — 10 path(s) described in OpenAPI.

## MCP servers (1)

- **Candidate MCP tool surface derived from PEXA operations**

## Agentic access (1)

- **Pexa Agentic Access** — 87 operations · 43 acting

## Security (3)

- **Pexa Authentication** — oauth2/mutualTLS · 3 schemes
- **Pexa Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC
- **Pexa Vulnerability Disclosure** — Hackerone · security.txt · contact published

## Tags

Real Estate, Australia, Conveyancing, Property Settlement, Land Registry, Title, PropTech, Mortgage, Digital Signing, Webhooks

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/pexa/). Scores are computed from the provider's own public artifacts under a published rubric.