Set-Up
The TAPI API requires authentication between STAFFLINK and TAPI. Please allow up to two weeks for set up to be performed. Contact your Customer Success Manager to implement this.
If there are multiple TAPI accounts, they can all be fed into the same base, or separate bases if that is preferred, each account will need to be authenticated one by one.
Once implemented, please do not change the names of any tables used by the API. Consequently, please also do not change any of the fields that the API feeds data into for each record. If you change data in any of the fields, the API will also overwrite it on the next run.
Not all data is available from TAPI, only selected data that is provided by the TAPI API.
The following jobs run to syncronise data.
Maintenance
The Maintenance job feeds listings from TAPI. The job runs every hour updating any records that have been modified in TAPI since the last run time.
Fields For Maintenance Table
TAPI Data | Field Name | Field Type |
Internal TAPI Record Id | Record_Id | Text |
When record created | Created_On | Date |
When job was closed | Closed_On | Date |
Description of the job | Description | Text |
The maintenance manager | Maintenance_Manager | Single Select |
The TAPI Jobs number | Job_Number | Text |
Link to TapI Job | Tapi_Link | URL |
Owner name | Related_Owner | Text |
Property Manager | Property_Manager | Single Select |
Status of job | Status | Single Select |
Related supplier | Related_Supplier | Text |
Property tenant | Related_Tenant | Text |
Summary of job | Summary | Text |
Job priority | Priority | Single Select |
Property Address | Tapi_Address | Text |
Postponed date | Plan_For_Later_Date | Sate |
Number of new messages on job | New_Messages | Number |
Any secondary statuses of the job | Secondary_Statuses | Multiple Select |