How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fixflo Property API

The Property API from Fixflo — 15 operation(s) for property.

Fixflo Property API is one of 24 APIs that Fixflo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Property. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 19 operations across 15 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api-sandbox.fixflo.com/api/v2, https://plus.dev.fixflo.com/api/v2.

19 operations 15 paths 20 schemas 1 DELETE11 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api-sandbox.fixflo.com/api/v2
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Fixflo Property API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer). By default, every request must be authenticated.

Paths & Operations 19

Across 15 paths, the API surfaces 19 operations — 1 DELETE, 11 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Property 19
GET
/Property/{Id}/Addresses
Property / addresses
get-property-id-addresses 2 params → 200
GET
/Property
Property
get-property 2 params → 200
POST
/Property
Property / save
post-property body → 200
GET
/Property/{Id}/Issues
Property / issues
get-property-Id-issues 4 params → 200
GET
/Property/Issues
Property / issues
get-property-Issues?externalPropertyRef=-ExternalPropertyRef 4 params → 200
GET
/Property/{Id}/Tags
Property / tags
get-Property-Id-Tags 1 param → 200
POST
/Property/{Id}/Tags
Property / tags
post-property-Id-Tags 1 param body → 200
GET
/Property/{Id}/Notes
Property / notes
get-Property-Id-Notes 1 param → 200404
POST
/Property/{Id}/Notes
Property / notes
post-property-Id-Notes 1 param body → 200404409
DELETE
/Property/{Id}/Notes
Property / notes
delete-Property-PropertyId-Notes 1 param → 200404
GET
/Property/{Id}/Tenants
Property / tenants
get-property-id-tenants 1 param → 200
GET
/Property/{PropertyId}/LandlordProperties
Property / landlord properties
get-property-propertyId-landlordproperties 2 params → 200
GET
/PropertyAddress/{Id}
Property address
get-propertyaddress-Id 1 param → 200
POST
/PropertyAddress/Merge
Property address / merge
post-propertyaddress-merge body → 200
POST
/PropertyAddress/Split
Property address / split
post-propertyaddress-split body → 200
GET
/PropertyAddress/Search
Property address / search
get-propertyaddress-search 5 params → 200
POST
/Property/UpdateAddress
Property / update address
post-Property-UpdateAddress body → 200
GET
/Property/Search
Property / search
get-Property-Search 9 params → 200
POST
/Property/{propertyId}/ServiceProgramme/{serviceProgrammeId}/ServiceEvent
Create Service Event
post-Property-propertyId-ServiceProgramme-serviceProgrammeId-ServiceEvent 3 params body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ServiceEvent (22 properties), Contractor (17 properties), Tenant (15 properties), ServiceProgrammeDef (14 properties). Each schema is shown below with its type and property counts.

Tag
object
1 property
ServiceEvent
object
22 properties
Property
object
14 properties
Tenant
object
15 properties
Envelope
object
This object is used to carry/return responses following post operations.
4 properties
LandlordProperty
object
7 properties
InvoiceDetails
object
This object is for use by contractor networks for submitting invoice details
4 properties
ServiceProgrammeDef
object
14 properties
IssueSummary
object
This DTO (data transfer object) provides summary information of issues.
8 properties
AssignedAgent
object
8 properties
PrevNextPager
object
5 properties
LineItem
object
This is an object in use only for contractor networks for providing invoice details
7 properties
Team
object
3 properties
Warranty
object
7 properties
Address
object
6 properties
ContractorCertification
object
3 properties
ContractorService
object
3 properties
Contractor
object
17 properties
PropertyAddress
object
This object is used to hold propery address information. It contains both address and property data.
5 properties
Brand
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fixflo-property-api-openapi.yml Raw ↑

Other APIs Fixflo publishes across the network.

Fixflo Agency API
Fixflo Agent API
Fixflo Asset API
Fixflo Block API
Fixflo Brand API
Fixflo Contractor API
Fixflo Contractor networks API
Fixflo Cost code API
Fixflo Estate API
Fixflo Fault Tree API
Fixflo Issue API
Fixflo Issue draft API
Where this information came from

This is an independent, third-party profile of Fixflo Property 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.