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 11 APIs on the APIs.io network, including Contacts API, Properties API, Tenancies API, and 8 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 33 more developer resources.
Read the contact records in a connected PropertyMe portfolio — owners, tenants, suppliers and the agency contact itself — with change-since-timestamp polling, contact alerts by ...
The lot (property) record in a connected PropertyMe portfolio — list all lots changed since a timestamp, or filter to rentals, active sales, vacancies and archived lots, retriev...
Read-only access to the tenancies in a connected PropertyMe portfolio and to tenancy balances, including a single tenancy balance record by id. This is the lettings ledger surfa...
The full routine and entry/exit inspection lifecycle — create, query, search by contact or lot, filter by status, and drive an inspection through schedule, reschedule, inspect, ...
Maintenance work orders, in both a v1 and a newer v2 shape. Create and update jobs, search by due date, created date and status, move a job through approve, assign, complete, re...
General property management tasks distinct from maintenance jobs — list tasks changed since a timestamp, create and update a task, find a task by id, read the assigned task mana...
Create a new bill in a connected PropertyMe portfolio, including the supporting document, against the trust accounting ledger. This is the only transaction-writing operation exp...
Typed dashboard aggregates over a connected portfolio — activities, communications, lots and transactions, each retrieved by dashboard item type. The read model behind the Prope...
The file surface, exposed as sub-resources rather than a standalone collection — create documents against contacts, lots, owner and tenant folios, inspections, tasks and jobs, a...
The agency staff directory inside a connected portfolio — list all members, and resolve the responsible member for a lot, a task, a job or an inspection. Requires the contact:re...
The consent seam. A single DELETE /v1/portfolios/disconnect operation severs the integration's connection to the customer's current portfolio. Every other operation in the API i...
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...
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...
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...
aid: propertyme
url: https://raw.githubusercontent.com/api-evangelist/propertyme/refs/heads/main/apis.yml
name: PropertyMe
kind: company
description: 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.
image: https://www.propertyme.com.au/wp-content/themes/PropertyMe/assets/dist/favicons/android-icon-192x192.png
tags:
- Real Estate
- Australia
- Property Management
- Rentals
- PropTech
- Tenancy
- Trust Accounting
- Inspections
- Maintenance
- Documents
- Payments
- New Zealand
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.19'
apis:
- aid: propertyme:propertyme-contacts-api
name: PropertyMe Contacts API
description: Read the contact records in a connected PropertyMe portfolio — owners, tenants, suppliers and the agency contact
itself — with change-since-timestamp polling, contact alerts by type, images, and write access for comments and documents
attached to a contact. Requires the contact:read scope; comment and document creation require contact:write.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Contacts
- Owners
- Tenants
- Suppliers
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-properties-api
name: PropertyMe Properties API
description: The lot (property) record in a connected PropertyMe portfolio — list all lots changed since a timestamp, or
filter to rentals, active sales, vacancies and archived lots, retrieve lot detail, contact alerts, images and the managing
member, and attach comments and documents to a lot or to an owner or tenant folio. Requires the property:read scope; writes
require property:write.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Properties
- Lots
- Rentals
- Vacancy
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-tenancies-api
name: PropertyMe Tenancies API
description: Read-only access to the tenancies in a connected PropertyMe portfolio and to tenancy balances, including a
single tenancy balance record by id. This is the lettings ledger surface that most listing-oriented real estate APIs omit
entirely. Requires the property:read scope.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Tenancies
- Leases
- Balances
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-inspections-api
name: PropertyMe Inspections API
description: The full routine and entry/exit inspection lifecycle — create, query, search by contact or lot, filter by status,
and drive an inspection through schedule, reschedule, inspect, close and reopen transitions, plus inspection reports,
comments, documents, images and the assigned inspection manager. Requires activity:read and, for the state transitions,
activity:write.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Inspections
- Reports
- Compliance
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-job-tasks-api
name: PropertyMe Job Tasks API
description: Maintenance work orders, in both a v1 and a newer v2 shape. Create and update jobs, search by due date, created
date and status, move a job through approve, assign, complete, reject and reopen, manage supplier quotations and quotation
documents, and attach comments, documents and images. The largest write surface in the API. Requires activity:read and
activity:write.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Maintenance
- Jobs
- Work Orders
- Quotations
- Suppliers
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-tasks-api
name: PropertyMe Tasks API
description: General property management tasks distinct from maintenance jobs — list tasks changed since a timestamp, create
and update a task, find a task by id, read the assigned task manager, and attach comments, documents and images. Requires
activity:read and activity:write.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Tasks
- Workflow
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-bills-api
name: PropertyMe Bills API
description: Create a new bill in a connected PropertyMe portfolio, including the supporting document, against the trust
accounting ledger. This is the only transaction-writing operation exposed in the published contract and it requires the
transaction:write scope.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Bills
- Trust Accounting
- Transactions
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-dashboards-api
name: PropertyMe Dashboards API
description: Typed dashboard aggregates over a connected portfolio — activities, communications, lots and transactions,
each retrieved by dashboard item type. The read model behind the PropertyMe dashboard, drawing on the activity, communication,
property and transaction read scopes.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Dashboards
- Reporting
- Analytics
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-documents-and-images-api
name: PropertyMe Documents and Images API
description: The file surface, exposed as sub-resources rather than a standalone collection — create documents against contacts,
lots, owner and tenant folios, inspections, tasks and jobs, and list images for contacts, lots, inspections, tasks and
jobs. Document creation is governed by the write scope of the parent resource.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Documents
- Images
- Files
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-members-api
name: PropertyMe Members API
description: The agency staff directory inside a connected portfolio — list all members, and resolve the responsible member
for a lot, a task, a job or an inspection. Requires the contact:read scope.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Members
- Property Managers
- Staff
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
- aid: propertyme:propertyme-portfolio-connection-api
name: PropertyMe Portfolio Connection API
description: The consent seam. A single DELETE /v1/portfolios/disconnect operation severs the integration's connection to
the customer's current portfolio. Every other operation in the API is implicitly scoped to the one portfolio the agency
connected, which is what makes this a per-customer, revocable integration rather than market-wide data access.
humanURL: https://app.propertyme.com/api/swagger-ui/
baseURL: https://app.propertyme.com/api
tags:
- Connection
- Portfolios
- Consent
properties:
- type: OpenAPI
url: openapi/propertyme-openapi.json
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: Authentication
url: authentication/propertyme-openid-configuration.json
common:
- type: AgenticAccess
url: agentic-access/propertyme-agentic-access.yml
- type: DomainSecurity
url: security/propertyme-domain-security.yml
- type: Authentication
url: authentication/propertyme-authentication.yml
- type: Website
url: https://www.propertyme.com.au/
- type: About
url: https://www.propertyme.com.au/about
- type: Documentation
url: https://app.propertyme.com/api/swagger-ui/
- type: APIReference
url: https://app.propertyme.com/api/swagger-ui/
- type: OpenAPI
url: https://app.propertyme.com/api/openapi.json
- type: OpenIDConnect
url: authentication/propertyme-openid-configuration.json
- type: SignUp
url: https://www.propertyme.com.au/request-a-demo
- type: Pricing
url: https://www.propertyme.com.au/pricing
- type: Security
url: https://www.propertyme.com.au/security
- type: TermsOfService
url: https://www.propertyme.com.au/terms
- type: PrivacyPolicy
url: https://www.propertyme.com.au/privacy
- type: Support
url: https://support.propertyme.com/hc/en-us
- type: StatusPage
url: https://status.propertyme.com/
- type: Blog
url: https://www.propertyme.com.au/blog
- type: BlogRSS
url: https://www.propertyme.com.au/feed
- type: Integrations
url: https://www.propertyme.com.au/integrations
- type: Partners
url: https://www.propertyme.com.au/partner-directory
- type: GitHubOrganization
url: https://github.com/PropertyMe
- type: SampleCode
url: https://github.com/PropertyMe/HelloPropertyMe.NET
- type: LinkedIn
url: https://www.linkedin.com/company/propertyme
- type: YouTube
url: https://www.youtube.com/channel/UC99HN1NFPAYyXvyKyRhHkJQ
- type: Contact
url: https://www.propertyme.com.au/contact
- type: WellKnown
url: well-known/propertyme-well-known.yml
- type: OAuthScopes
url: scopes/propertyme-scopes.yml
- type: Conformance
url: conformance/propertyme-conformance.yml
- type: ErrorCatalog
url: errors/propertyme-problem-types.yml
- type: Lifecycle
url: lifecycle/propertyme-lifecycle.yml
- type: Conventions
url: conventions/propertyme-conventions.yml
- type: DataModel
url: data-model/propertyme-data-model.yml
- type: MCPServer
url: mcp/propertyme-mcp.yml
- type: ToolCrosswalk
url: mcp/propertyme-tool-crosswalk.yml
- type: LLMsTxt
url: llms/propertyme-llms.txt
- type: Overlay
url: overlays/propertyme-openapi-overlay.yaml
- type: Packages
url: packages/propertyme-packages.yml
- type: AgentSkill
url: skills/_index.yml
- type: Arazzo
url: arazzo/propertyme-connect-and-sync.yml
name: Connect a PropertyMe portfolio and run a change-since sync
- type: Arazzo
url: arazzo/propertyme-maintenance-job.yml
name: Raise, quote, approve and complete a PropertyMe maintenance job
- type: Arazzo
url: arazzo/propertyme-inspection-cycle.yml
name: Schedule, conduct, report and close a PropertyMe inspection
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com