PropertyMe
PropertyMe is an Australian cloud property management and trust accounting platform for residential real estate agencies, founded in 2013 and operated by MePay Holdings Pty Ltd (AFCA member ID 81095, AFS licence no. 528836), with roughly 1.7 million properties under management across Australia and New Zealand. In the Australian property value chain it sits on the PROPERTY MANAGEMENT rail rather than the listing or settlement rails — it does not operate a portal like REA Group's realestate.com.au or Domain, and it is not a PEXA conveyancing participant; it is the system of record for the rental portfolio, holding lots, tenancies, owners, tenants, suppliers, trust transactions, inspections, maintenance jobs and documents, plus its own MePay payments product and the Grow CRM and AiMe assistant products. Its API posture is unusually honest for this sector — the machine-readable contract is genuinely open while the credentials are not. A Swagger 2.0 document describing 75 paths, 86 operations and 296 definitions is served anonymously with no login at https://app.propertyme.com/api/openapi.json, rendered by a public Swagger UI at https://app.propertyme.com/api/swagger-ui/, and the OpenID Connect discovery document at https://login.propertyme.com is also served anonymously and advertises the full scope list. But no self-serve developer signup, app registration route or public client-credential issuance path exists anywhere on propertyme.com.au, app.propertyme.com or any developer/developers/docs/api subdomain (none of which resolve); a developer must approach PropertyMe to be issued an OAuth client_id and client_secret, and every call is additionally scoped to one customer's portfolio that the agency itself connects and can disconnect. RESO is absent — PropertyMe does not appear in the RESO certification directory, there is no OData service, no $metadata document and no Universal Property Identifier, which is the expected Australian answer because RESO is a North American NAR/MLS construct with no Australian counterpart. PropertyMe publishes no open data.
PropertyMe publishes 6 APIs on the APIs.io network, including Connection API, Scope: Activities API, Scope: Bills API, and 3 more. Tagged areas include Real-Estate, Australia, Property Management, Rentals, and PropTech.
PropertyMe’s developer surface includes authentication, documentation, API reference, signup flow, pricing, support, engineering blog, and 34 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
PropertyMe Connection API
The Connection API from PropertyMe — 1 operation(s) for connection.
PropertyMe Scope: Activities API
The Scope: Activities API from PropertyMe — 43 operation(s) for scope: activities.
PropertyMe Scope: Bills API
The Scope: Bills API from PropertyMe — 2 operation(s) for scope: bills.
PropertyMe Scope: Contacts API
The Scope: Contacts API from PropertyMe — 11 operation(s) for scope: contacts.
PropertyMe Scope: Messages API
The Scope: Messages API from PropertyMe — 1 operation(s) for scope: messages.
PropertyMe Scope: Properties API
The Scope: Properties API from PropertyMe — 17 operation(s) for scope: properties.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
PropertyMe
OPEN COLLECTIONArazzo Workflows 3
Multi-step API workflows described with the Arazzo specification.
Connect a PropertyMe portfolio and run a change-since sync
PropertyMe publishes no webhooks, so an integration keeps a portfolio current by polling the six change-since collections with an int64 Timestamp cursor. This workflow seeds the...
ARAZZOSchedule, conduct, report and close a PropertyMe inspection
The routine and entry/exit inspection lifecycle. Requires activity:read for the reads and activity:write for every transition. The permitted transition graph is not published, s...
ARAZZORaise, quote, approve and complete a PropertyMe maintenance job
The maintenance work-order flow, using the v2 job-task shape for create and read and the shared v1 sub-resources for quotations, transitions and attachments. Requires activity:r...
ARAZZOSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.