Reapit
Last updated 19 October 2026
PMSAvailable
TerraTecton connects to Reapit through the Foundations API — Reapit’s public platform API. The integration is server-to-server and read-only: TerraTecton pulls your properties, tenancies, safety certificates and outstanding rent transactions on a schedule, and never writes anything back to Reapit.
What TerraTecton reads
| Reapit resource | What we request | What it becomes in TerraTecton |
|---|---|---|
/properties | Lettings properties, with the landlord embedded | Your property list — address, letting status, rent, landlord name, gas supply flag |
/tenancies | Tenancies, with related parties embedded | Tenant and guarantor names and contact details per tenancy |
/certificates | Safety certificates (category=safetyCertificate) | The compliance register — Gas Safety, EICR, EPC and other certificate expiry dates |
/transactions | Outstanding rent transactions (status=outstanding, type=rent) | One arrears row per tenancy — total owed, oldest due date, days overdue |
The sync runs hourly. Every pull is idempotent — a row that has not changed in Reapit changes nothing in TerraTecton — and each property is resolved to a verifiable property identifier (a UPRN where the address allows) so arrears, certificates and repairs line up on the same record.
Authentication
TerraTecton authenticates with OAuth 2.0 client credentials against Reapit Connect — the flow Reapit provides for machine-to-machine, server-side integrations. There is no browser redirect and no user in the loop; your Reapit users never share their sign-in with us. Requests carry the api-version: 2020-01-31 and reapit-customerheaders, pages are read at the maximum page size, and the connector stays inside Reapit’s published platform rate limits.
The app requests read-only permissions only:
agencyCloud/properties.readagencyCloud/tenancies.readagencyCloud/certificates.readagencyCloud/transactions.read
Connecting your agency
- Get credentials. Ask your Reapit customer success manager to install the TerraTecton app for your organisation (or, while our AppMarket listing is in review, to issue Connect client credentials with the four read scopes above). You will have three values: your customer code (for example
SBOX), a client ID and a client secret. - Enter them in TerraTecton. In the app, open Integrations → Reapit and paste the three values. The secret is encrypted at rest on our servers the moment it is saved; it is never stored in or sent to the browser.
- Test and sync. Press Test connection, then Sync now. The card shows row counts per resource and the result of every run. From then on the pull repeats hourly.
Sample mode. Before credentials are saved, the Reapit card runs on realistic sample data and says so with a Sample data badge. Everything downstream — the compliance register, the arrears list, the dashboards — works the same way, so your team can evaluate the product before anything is connected.
Certificate types
Reapit lets each customer define their own certificate type codes. TerraTecton maps the codes seen most often across UK agencies (GS, GSC, LGSR and CP12 to Gas Safety; EIC, EICR and ELEC to EICR; EPC; FRA; LEG/LRA to legionella; smoke/CO, PAT and asbestos codes) and falls back to keyword matching on the certificate notes. A code we cannot map is kept, visibly, as other:<code> — never dropped — and shows up in the register for a person to classify. If your agency uses house codes we do not recognise, tell us and we will add them.
Data handling
- Read-only.The integration holds no write permissions. Any update that should reach your PMS goes through TerraTecton’s write journal, where a person on your team reviews and applies it.
- Credentials are encrypted at rest (envelope encryption) and readable only by the sync service. They are shown masked everywhere in the product.
- Hosting is Microsoft Azure, UK South. See the privacy policy for the full picture, including our controller/processor roles.
- Audit. Every sync run is recorded — when, what changed, what failed — and every action taken on the data (a chase approved, a letter sent) lands on a tamper-evident record.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Test connection fails with “Connect refused the client credentials” | Client ID or secret mistyped, or the Connect app was created without the client-credentials grant |
| Test passes but a resource syncs zero rows | The matching read scope was not granted to the app — check all four permissions |
Certificates appear as other:<code> | Your agency’s certificate type codes are custom — send us the codes and what they mean |
| Card still says Sample data | One of the three credential fields is empty; all three are required for live mode |
Stuck? Email hello@terratecton.com — include your customer code (never your client secret) and the time of the failed sync.