Complete guide for integrating with Prop360's external API system
Available integration endpoints
Create, Read, Update, Delete
Multi-image upload
API token authentication
https://prop360.pro/api/integration/id from create/list responses{ error: "..." } with standard HTTP status codesThe Contacts API uses your existing API token. No new credentials are needed. PUT requests perform a partial merge — only the fields you send are changed; all other fields are preserved.
List all available contact fields and their types
List contacts (paginated, max 100) or create a new one
Fetch, partially update, or soft-delete a contact by its MongoDB ID
isPublic flag — contacts are always private CRM recordsdata must match userFriendlyName from the fields call.Existing tokens with create can insert these records. Property requests stay the same. Cash flow Document Type is Invoice or Bank Transaction.Accrual/Payment is Accrual or Payment. An accrual Matching Number is set to the new pid unless you pass the source-payment keys.
List cash flow records (max 100 per page) or create an accrual or payment
Fetch, partially update, or soft-delete a cash flow record
List timetable records (max 100 per page) or create one
Fetch, partially update, or soft-delete a timetable record
The API now uses hierarchical location fields instead of simple "City" field. This provides better geographic accuracy and supports multilingual location names.
Existing integrations using "City" field will continue to work, but we recommend updating to the new hierarchical location system for better accuracy and features.
Use human-readable field names instead of internal IDs
Cryptographically secure API tokens with granular permissions
Multi-image upload with S3 integration and validation
Structured location data with Region/SubRegion/Area hierarchy
Complete audit trail for all API operations
Complete documentation with examples and best practices
Full CRUD for contacts with safe partial updates via the same API token
Create accruals, payments, and timetable rows with the same token and field-name body
Contact a Prop360 administrator to generate an API token with appropriate permissions for your broker/agent.
Use the Fields API to get the list of available fields and their types for your broker/agent.
Use the Properties API with hierarchical location fields (Region, SubRegion, Area) and user-friendly field names.
Use the Image Upload API to add images to your properties with automatic validation.
Use the Contacts API with the same token to create and manage client contacts. Call GET /api/integration/contacts/fields first to discover available fields, then POST to create contacts.
Call GET /api/integration/cashflows/fields or GET /api/integration/timetables/fields, then POST to the matching collection with the same token.