How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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

PEXA Plus Marketplace B2B API is one of 5 APIs that PEXA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Marketplace, Title Search, and Billing. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and API documentation.

This API exposes 5 operations across 5 paths, organized into 3 resource areas, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 1.0.2.

Requests are made against a single base URL, https://plus.pexa.com.au/api/plus/v1.

5 operations 5 paths 6 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.2
Base URL
https://plus.pexa.com.au/api/plus/v1
Resource Areas
3

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 4 GET, 1 POST. They span 3 resource areas: HealthCheck, TitleSearch, Billing. Each is listed below with its method, path, parameters, and response codes.

HealthCheck 1
GET
/health
Health check
getHealth 1 param → 200500
TitleSearch 3
POST
/title-search
Create title search
createTitleSearch 1 param body → 201400401403405500
GET
/title-search/{titleSearchId}
Retrieve title search by id
retrieveTitleSearch 2 params → 200400401403404405500
GET
/title-search/{titleSearchId}/documents
Retrieve title search documents by id
retrieveTitleSearchDocuments 2 params → 200400401403404405500
Billing 1
GET
/billing
Retrieve billing invoice
retrieveBilling 6 params → 200400401403405500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are TitleSearch (6 properties), Error (3 properties), Money (2 properties), TitleSearchDocuments (2 properties). Each schema is shown below with its type and property counts.

TitleSearch
object
Title search
6 properties 2 required
TitleSearchDocuments
object
Title search documents
2 properties
Invoice
object
Invoice
1 property
Errors
object
List of errors related to the API
1 property
Error
object
Detailed error related to the API
3 properties
Money
object
Represents an amount of money
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pexa-plus-marketplace-b2b-api-openapi.yaml Raw ↑

Other APIs PEXA publishes across the network.

PEXA Exchange API
PEXA Standalone Discharge Experience API
PEXA Notification Service [$]
PEXA Projects API
Where this information came from

This is an independent, third-party profile of PEXA Plus Marketplace B2B API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.