Start with the workflow — not an endpoint count.
Tell us which systems and tenancy records need to move. We confirm the supported scope, access rules and event flow before rollout.
Keep supported records in sync
Read approved rental-workflow records without opening access to the rest of your workspace.
Data families in the current contract
- Deals
- Properties
- Contacts
React to important changes
Use signed webhooks for supported deal, payment, document, party, task and compliance changes.
Event families
- compliance
- deal
- document
- party
- payment
- task
Control every credential
Limit each key by permission, endpoint and optional IP allowlist, then revoke or expire it when needed.
See what happened
Review API usage and webhook delivery history when monitoring or troubleshooting an integration.
How Enterprise integration access works
- 1
Confirm the supported scope
Share the systems, records and actions your integration needs. We confirm what belongs in the approved external contract.
- 2
Create a limited company key
An agency admin creates a company-scoped, read-only key with approved endpoints, an expiry date and an optional IP allowlist.
- 3
Connect and monitor
Authenticate each request with the API key, validate webhook signatures and use the available logs to monitor the connection.
CONTROL THE BOUNDARY
Give each integration only the access it needs.
Company isolation, read-only access, endpoint allowlists, expiry dates and optional IP restrictions keep each integration inside its approved scope.
- Company scoped
- Read-only access
- Endpoint allowlist
- Optional IP allowlist
- Expiry and revocation
Use the API for records. Use webhooks for change.
External API
Read the supported records made available to your integration. Authentication uses a company API key over HTTPS.
Signed webhooks
Receive supported changes without polling. Each delivery includes an event identifier, timestamp and HMAC-SHA256 signature for verification.
Delivery history and retries help your team investigate failed webhook calls.
Build against an approved integration contract.
During rollout, your technical team receives the approved resource and event scope, authentication requirements, error behaviour, limits and webhook verification guidance for that integration.
Approved API scope
See only the resources and methods confirmed for your agency's integration.
Authentication and limits
Receive the company-key requirements, permissions, error behaviour and limits that apply to the rollout.
Webhook verification
Configure an approved endpoint, verify signed payloads and understand delivery and retry behaviour.
Frequently asked questions
- Is API access included in the self-serve plans?
- API keys and webhooks are Enterprise capabilities. Contact Sales with the systems and workflow you need so the supported scope can be confirmed before rollout.
- How does an integration authenticate?
- An agency admin creates a company-scoped API key. The integration sends that key in the documented HTTPS request header; it does not exchange the key for a user JWT.
- Can we restrict what an API key can access?
- Yes. Keys can be limited by permission, approved endpoints, expiry and an optional IP allowlist, then revoked when they are no longer needed.
- Which records can we connect?
- The available resources depend on the external contract confirmed for your rollout. Your technical handoff lists only the resources and methods approved for your agency's integration.
- How are webhook calls protected?
- TenancyDesk sends supported events to HTTPS endpoints with a timestamped HMAC-SHA256 signature. Your integration verifies the signature before processing the payload.
- Does the API replace Property Finder or Bayut imports?
- No. Property Finder uses your agency's API credentials, while Bayut / dubizzle uses a Profolio Excel import. The Enterprise API is for approved connections to your internal systems. See Integrations for each connection method.
- Can we test the API during the standard free trial?
- The 14-day trial covers the Professional product experience. API keys and webhooks are scoped separately with Enterprise Sales.
Plan the integration around your real workflow.
Tell us which systems and records need to move. We will confirm the supported scope, controls and rollout path.