The Swagger documentation can be found here.
Once you have a JWT Token generated via the auth endpoint, enter "bearer {jwt_token}" into the Swagger api_key field located on the top of the page and click Explore. You will now be able to test all endpoints within Swagger.Each Acquaint customer has their own separate relational database. Each customer database will have a unique API Key and Site Prefix.
The Contacts table in Acquaint is used to store types of people such as Users, Applicants, Landlords, Vendors etc. determined by the TypeID field. Note that customers can also define their own custom Types, Statuses, Sources, Titles etc.
Endpoint such as /Contacts/list will allow filtering on TypeID and various other fields. For instance, you can request a list of Current Applicants called John Smith (using filter fields of status, type, firstNames and lastName).
Most tables will cross reference other tables by means of IDs. e.g. Properties are owned by a Landlord or Vendor so the ContactID field within the Properties model can be used to obtain the full Contact details via /Contacts/{id}.
Tables like PropertyOffers will be linked to Properties and also to multiple Contacts – contactId (the applicant making the offer), solicitorId, addedByUserid.All list endpoints are paginated. Pagination can be accessed via the following request query parameters:
Name | Default Value | Max Value |
---|---|---|
currentPage | 1 | N/A |
pageSize | 1000 | 1000 |
The response of each list endpoint is wrapped in a 'pagination envelope' defining the details of the pagination.
e.g.
If the currentPage request query parameter is greater than the total number of pages, the 'pagination envelope' response will be returned with a blank data array.
All dates on the API are in GMT, and must be provided as GMT. They're displayed in the standard ISO 8601 format. For example, October 1st 2024 at 4:05PM is 2024-10-01T16:05:00.