Search
K

Make the Connection with PEXA APIs

Our APIs are easy to integrate and streamline the mortgage journey for lenders, conveyancers and software providers.

APIs for every need

Powerful and easy to integrate, our APIs allow you to seamlessly integrate our industry-leading settlement and lodgement capabilities into your existing end-to-end processes. With automation at the heart of our solution, you’ll spend less time on re-keying of data and more time on the things that matter–your customers.

Within our Developer Portal you’ll find everything you need to begin working with our PEXA APIs including comprehensive API documentation and implementation resources, all created with our developer community in mind.

Innovative

PEXA is the world’s first digital settlement platform. We’re on a journey to revolutionise the way people buy and sell property​

Secure

PEXA API access is securely managed using industry best practices built around the OAuth 2.0 security framework

Seamless

Our APIs unlock the potential for seamless collaboration between Lenders and Law Firms, maximising interoperability and efficiency

Getting started

Authentication

PEXA adheres to industry best practices to authenticate and authorise access to the PEXA APIs. PEXA supports the Client Credentials OAuth 2.0 authentication methods.

What is the Client Credentials flow?

The OAuth 2.0 Client Credentials flow is designed for Machine-to-Machine (M2M) authentication. This method provides a way for applications or systems to securely authenticate and access APIs on behalf of the client application itself, rather than a specific user. Authentication is granted by passing an access token in the request header of the API. An access token is received by passing a series of client-specific credentials to the authentication server.

How to get credentials?

To authenticate using OAuth 2.0 Client credentials, the client applications need to follow the steps outlined below.

  1. The client makes a request to the authorisation server sending the client ID, the client secret, along with the audience and other claims. (Details of these parameters are explained below.)
  2. The authorisation server validates the request, and, if successful, sends a response with an access token.
  3. The client can now use the access token to send requests to the resource server (i.e. the PEXA API).
  4. The resource server sends back the response.

How to get credentials for the client credentials flow?

If you're:

  • New to PEXA and would like a set of credentials to access our PEXA Labs APIs or
  • Have an enquiry relating to credentials or authentication

Please email implementation@pexa.com.au with your company and contact information as well as any other relevant details and one of the team will be in touch.

Important information