PEXA

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.

PEXA publishes 5 APIs on the APIs.io network, including Exchange API, Projects API, Notification Service API, and 2 more. Tagged areas include Real Estate, Australia, Conveyancing, Property Settlement, and Land Registry.

The PEXA catalog on APIs.io includes 1 event-driven AsyncAPI specification.

PEXA’s developer surface includes authentication, developer portal, documentation, signup flow, pricing, support, engineering blog, and 44 more developer resources.

🌐 Visit website 📡 Source on GitHub
60.1/100 strong ▬ flat Agent 87/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
5 APIs 1 MCP Servers
Real EstateAustraliaConveyancingProperty SettlementLand RegistryTitlePropTechMortgageDigital SigningWebhooks

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 60.1/100 · strong
Contract Quality 17.6 / 25
Developer Ergonomics 14.8 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 7.2 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 87/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/pexa: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

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 Projects API

The PEXA Projects API (v4) supports multi-lot development settlements — creating and managing projects, project lots, project statuses and related participants for property deve...

PEXA Notification Service API

The PEXA Push Notifications Service delivers event notifications to subscribers via webhook and manages registration for specific events, including creating, updating and deleti...

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...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Candidate MCP tool surface derived from PEXA operations

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Pexa Notification Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Pexa Authentication

oauth2/mutualTLS · 3 schemes

SECURITY

Pexa Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Pexa Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Pexa Scopes

11 scopes · clientCredentials/authorizationCode

11 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Pexa Agentic Access

87 operations · 43 acting

87 operations · 43 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Portal
Portal
 SignUp
SignUp
 Sandbox
Sandbox
 DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted

Documentation 3

Reference material describing how the API behaves

Documentation
Documentation
 Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 WellKnown
WellKnown
 MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 ErrorCodes
ErrorCodes
 Lifecycle
Lifecycle
 Conformance
Conformance
 DataModel
DataModel
 Components
Components
 Webhooks
Webhooks

Scroll for all 9

Build 2

SDKs, sample code, and the tooling you integrate with

Packages
Packages
 GitHubOrganization
GitHubOrganization

Access & Security 8

Authentication, authorization, and security posture

VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 OAuthScopes
OAuthScopes
 Authentication
Authentication
 Authentication
Authentication
 SecurityTxt
SecurityTxt
 Security
Security
 Compliance
Compliance

Scroll for all 8

Operate 5

Status, limits, changes, and where to get help

StatusPage
StatusPage
 Support
Support
 ChangeLog
ChangeLog
 ChangeLog
ChangeLog
 HelpCenter
HelpCenter

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 4

The organization behind the API

Website
Website
 Blog
Blog
 About
About
 InvestorRelations
InvestorRelations

Other 7

Properties that don't map to a standard resource type

Overlay
Overlay
 Overlay
Overlay
 Overlay
Overlay
 Overlay
Overlay
 Overlay
Overlay
 Overlay
Overlay
 Overlay
Overlay

Scroll for all 7

Source (apis.yml)

apis.yml Raw ↑ 
aid: pexa
url: https://raw.githubusercontent.com/api-evangelist/pexa/refs/heads/main/apis.yml
name: PEXA
kind: company
description: '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.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/pexa.png
tags:
- Real Estate
- Australia
- Conveyancing
- Property Settlement
- Land Registry
- Title
- PropTech
- Mortgage
- Digital Signing
- Webhooks
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.19'
apis:
- aid: pexa:pexa-exchange-api
  name: PEXA Exchange API
  description: The PEXA Exchange API covers key facets of PEXA Exchange e-conveyancing functionality — creating and updating
    workspaces, invitations, participants, land title references, documents, conversations, financial settlement line items,
    settlement dates and settlement completion records. Documented as a Swagger 2.0 contract across versioned paths (/v2 through
    /v6). Authenticated with OAuth 2.0 (client credentials or authorization code) or mutual TLS; each endpoint requires specific
    scopes. Access requires a signed PEXA API Agreement.
  humanURL: https://developer.pexa.com.au/Exchange/api/apireference/
  baseURL: https://api.pexa.com.au
  tags:
  - Conveyancing
  - Property Settlement
  - Workspace
  - Land Registry
  - Title
  properties:
  - type: Swagger
    url: openapi/pexa-exchange-api-swagger.json
  - type: Swagger
    url: openapi/pexa-exchange-api-legacy-swagger.json
  - type: APIReference
    url: https://developer.pexa.com.au/Exchange/api/apireference/
  - type: Documentation
    url: https://developer.pexa.com.au/Exchange/docs/documentation/
  - type: Pricing
    url: https://www.pexa.com.au/api-pricing/
  - type: AgentSkill
    url: skills/pexa-create-workspace-and-settle.md
    name: Create a PEXA workspace and take it to settlement
  - type: Overlay
    url: overlays/pexa-exchange-overlay.yaml
  - type: Overlay
    url: overlays/pexa-exchange-legacy-overlay.yaml
  - type: Authentication
    url: authentication/pexa-authentication.yml
  - type: Conventions
    url: conventions/pexa-conventions.yml
  - type: Sandbox
    url: sandbox/pexa-sandbox.yml
  - type: ErrorCatalog
    url: errors/pexa-error-codes.yml
    name: OB* exception registry (135 codes)
  - type: Components
    url: components/pexa-components.yml
    name: PEXA Web deep links
  - type: ChangeLog
    url: https://developer.pexa.com.au/Exchange/docs/changelog/
  - type: OAuthScopes
    url: scopes/pexa-scopes.yml
- aid: pexa:pexa-projects-api
  name: PEXA Projects API
  description: The PEXA Projects API (v4) supports multi-lot development settlements — creating and managing projects, project
    lots, project statuses and related participants for property developers settling many lots through PEXA. Published as
    an OpenAPI 3.0.3 contract with OAuth 2.0 authorizationCode and clientCredentials flows and named scopes such as au:projects:project:write.
  humanURL: https://developer.pexa.com.au/Projects/api/apireference/
  baseURL: https://api.pexa.com.au
  tags:
  - Project
  - Property Development
  - Conveyancing
  properties:
  - type: OpenAPI
    url: openapi/pexa-projects-api-v4-openapi.yaml
  - type: APIReference
    url: https://developer.pexa.com.au/Projects/api/apireference/
  - type: Documentation
    url: https://developer.pexa.com.au/Projects/docs/documentation/
  - type: AgentSkill
    url: skills/pexa-settle-a-multi-lot-project.md
    name: Settle a multi-lot development through PEXA Projects
  - type: Overlay
    url: overlays/pexa-projects-overlay.yaml
  - type: Authentication
    url: authentication/pexa-authentication.yml
  - type: Conventions
    url: conventions/pexa-conventions.yml
  - type: Sandbox
    url: sandbox/pexa-sandbox.yml
  - type: ChangeLog
    url: https://developer.pexa.com.au/Projects/docs/changelog/
  - type: OAuthScopes
    url: scopes/pexa-scopes.yml
- aid: pexa:pexa-notification-service-api
  name: PEXA Notification Service API
  description: The PEXA Push Notifications Service delivers event notifications to subscribers via webhook and manages registration
    for specific events, including creating, updating and deleting notification registrations and rotating the shared secret
    used to sign webhook deliveries. Published as an OpenAPI 3.1.0 contract that declares two outbound webhooks — SubscriberNotification
    and NonSubscriberNotification. PEXA documents this as a premium, billed API.
  humanURL: https://developer.pexa.com.au/Webhooks/api/apireference/
  baseURL: https://api.pexa.com.au
  tags:
  - Webhooks
  - Notifications
  - Events
  properties:
  - type: OpenAPI
    url: openapi/pexa-notification-service-openapi.yaml
  - type: APIReference
    url: https://developer.pexa.com.au/Webhooks/api/apireference/
  - type: AgentSkill
    url: skills/pexa-subscribe-to-workspace-events.md
    name: Subscribe to PEXA workspace events over webhooks
  - type: Overlay
    url: overlays/pexa-notification-service-overlay.yaml
  - type: Authentication
    url: authentication/pexa-authentication.yml
  - type: Conventions
    url: conventions/pexa-conventions.yml
  - type: Sandbox
    url: sandbox/pexa-sandbox.yml
  - type: Webhooks
    url: asyncapi/pexa-notification-webhooks.yml
    name: PEXA Webhooks event catalogue (110 events)
  - type: ErrorCatalog
    url: errors/pexa-error-codes.yml
    name: GA.NOTIF.* error registry
  - type: OAuthScopes
    url: scopes/pexa-scopes.yml
- aid: pexa:pexa-standalone-discharge-experience-api
  name: PEXA Standalone Discharge Experience API
  description: 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. Declares production and test servers and OAuth 2.0 authorizationCode
    and clientCredentials flows.
  humanURL: https://developer.pexa.com.au/EXP_ConsolidatedDischarge/api/apireference/
  baseURL: https://api.pexa.com.au
  tags:
  - Mortgage
  - Discharge
  - Financial Institutions
  properties:
  - type: OpenAPI
    url: openapi/pexa-standalone-discharge-experience-api-openapi.yaml
  - type: APIReference
    url: https://developer.pexa.com.au/EXP_ConsolidatedDischarge/api/apireference/
  - type: AgentSkill
    url: skills/pexa-discharge-a-mortgage.md
    name: Discharge a mortgage through PEXA
  - type: Overlay
    url: overlays/pexa-standalone-discharge-overlay.yaml
  - type: Authentication
    url: authentication/pexa-authentication.yml
  - type: Conventions
    url: conventions/pexa-conventions.yml
  - type: Sandbox
    url: sandbox/pexa-sandbox.yml
  - type: OAuthScopes
    url: scopes/pexa-scopes.yml
- aid: pexa:pexa-plus-marketplace-b2b-api
  name: PEXA Plus Marketplace B2B API
  description: 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 an OpenAPI 3.0.3 contract (an OpenAPI 3.0.0 variant of
    the same document is also shipped in the portal) with a documented server at https://plus.pexa.com.au/api/plus/v1.
  humanURL: https://developer.pexa.com.au/Marketplace/api/apireference/
  baseURL: https://plus.pexa.com.au/api/plus/v1
  tags:
  - Marketplace
  - Title Search
  - Billing
  properties:
  - type: OpenAPI
    url: openapi/pexa-plus-marketplace-b2b-api-openapi.yaml
  - type: OpenAPI
    url: openapi/pexa-plus-marketplace-b2b-api-oas300-openapi.yaml
  - type: APIReference
    url: https://developer.pexa.com.au/Marketplace/api/apireference/
  - type: AgentSkill
    url: skills/pexa-order-a-title-search.md
    name: Order a title search and reconcile billing
  - type: Overlay
    url: overlays/pexa-plus-marketplace-overlay.yaml
  - type: Overlay
    url: overlays/pexa-plus-marketplace-oas300-overlay.yaml
  - type: Authentication
    url: authentication/pexa-authentication.yml
  - type: Conventions
    url: conventions/pexa-conventions.yml
  - type: Sandbox
    url: sandbox/pexa-sandbox.yml
  - type: Documentation
    url: https://developer.pexa.com.au/Marketplace/api/apireference/
  - type: OAuthScopes
    url: scopes/pexa-scopes.yml
common:
- type: AgenticAccess
  url: agentic-access/pexa-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/pexa-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/pexa-domain-security.yml
- type: OAuthScopes
  url: scopes/pexa-scopes.yml
- type: Authentication
  url: authentication/pexa-authentication.yml
- type: Website
  url: https://www.pexa.com.au/
- type: Portal
  url: https://developer.pexa.com.au/
- type: Documentation
  url: https://developer.pexa.com.au/
- type: SignUp
  url: https://www.pexa.com.au/pexa-apis/
- type: Pricing
  url: https://www.pexa.com.au/api-pricing/
- type: Documentation
  url: https://www.pexa.com.au/staticly-media/2024/10/PEXA_Integration_Principles-sm-1728949058.pdf
- type: Authentication
  url: https://auth.pexa.com.au/.well-known/openid-configuration
- type: StatusPage
  url: https://status.pexa.com.au/
- type: Support
  url: https://www.pexa.com.au/contact-us/
- type: Blog
  url: https://www.pexa-group.com/content-hub/news/
- type: About
  url: https://www.pexa-group.com/about/
- type: InvestorRelations
  url: https://www.pexa-group.com/investor-centre/
- type: WellKnown
  url: well-known/pexa-well-known.yml
- type: SecurityTxt
  url: well-known/pexa-security.txt
- type: Security
  url: https://www.pexa.com.au/security/
- type: Conventions
  url: conventions/pexa-conventions.yml
- type: Idempotency
  url: conventions/pexa-conventions.yml
  name: Webhook delivery idempotency (webhook-id)
- type: ErrorCatalog
  url: errors/pexa-error-codes.yml
  name: PEXA exception and error code registries
- type: ErrorCodes
  url: errors/pexa-problem-types.yml
  name: Derived 4xx/5xx response map
- type: Lifecycle
  url: lifecycle/pexa-lifecycle.yml
- type: ChangeLog
  url: changelog/pexa-changelog.yml
- type: ChangeLog
  url: https://developer.pexa.com.au/Exchange/docs/changelog/
  name: PEXA Exchange APIs Changelog
- type: Sandbox
  url: sandbox/pexa-sandbox.yml
- type: Conformance
  url: conformance/pexa-conformance.yml
- type: Compliance
  url: https://compliance.pexa.com.au/
  name: PEXA Compliance Hub
- type: DataModel
  url: data-model/pexa-data-model.yml
- type: Components
  url: components/pexa-components.yml
  name: PEXA Web deep links
- type: Packages
  url: packages/pexa-packages.yml
- type: MCPServer
  url: mcp/pexa-mcp.yml
  name: Candidate MCP tool surface derived from PEXA operations
- type: LLMsTxt
  url: llms/pexa-llms.txt
- type: AgentSkill
  url: skills/_index.yml
  name: PEXA agent skills
- type: Webhooks
  url: asyncapi/pexa-notification-webhooks.yml
  name: PEXA Webhooks event catalogue (110 events)
- type: Overlay
  url: overlays/pexa-exchange-overlay.yaml
- type: Overlay
  url: overlays/pexa-exchange-legacy-overlay.yaml
- type: Overlay
  url: overlays/pexa-projects-overlay.yaml
- type: Overlay
  url: overlays/pexa-notification-service-overlay.yaml
- type: Overlay
  url: overlays/pexa-standalone-discharge-overlay.yaml
- type: Overlay
  url: overlays/pexa-plus-marketplace-overlay.yaml
- type: Overlay
  url: overlays/pexa-plus-marketplace-oas300-overlay.yaml
- type: DeveloperPortal
  url: https://developer.pexa.com.au/
- type: APIReference
  url: https://developer.pexa.com.au/Exchange/api/apireference/
- type: GettingStarted
  url: https://www.pexa.com.au/pexa-apis/
  name: PEXA API onboarding - six step integration path
- type: HelpCenter
  url: https://help.pexa.com.au/s/
- type: TermsOfService
  url: https://www.pexa.com.au/terms-conditions/
- type: PrivacyPolicy
  url: https://www.pexa.com.au/privacy-policy/
- type: GitHubOrganization
  url: https://github.com/PEXA-AU
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com