PEXA Subscriber API is one of 18 APIs that PEXA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Subscriber. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and API documentation.
This API exposes
6 operations
across 6 paths,
and defines 46 schemas.
It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, https://localhost/.
6 operations6 paths46 schemas6 GET
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.pexa.com.au
Resource Areas
1
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.
The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are au.net.pexa.api.schema._2.NotificationType (13 properties), au.net.pexa.api.schema._2.NotificationDetailsType (11 properties), au.net.pexa.api.schema._2.NotificationInvitationOutstandingDetailsType (10 properties), au.net.pexa.api.schema._2.SubscriberDetailsType (7 properties). Each schema is shown below with its type and property counts.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of PEXA Subscriber 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.
