Integrations
One integration surface, and it is the honest one: an HTTP API with keys, scopes and webhooks. There is no marketplace of one-click connectors — what you build against the API, you own and you can take with you.
Keys and webhook endpoints live in the app under Settings → Integrations. Every plan, the free one included, can issue them.
One integration, built properly
A tenant-scoped REST API and outbound webhooks — not a wall of logos we could not support.
The tribe.one API
Keys are issued per community, carry read and write scopes, and can be revoked or given an expiry date. A key only ever sees the community it was issued for — there is no cross-tenant read, by design.
- Bearer API keys with separate read and write scopes
- Tenant-scoped responses — one key, one community
GET /api/v1/meto verify a key and read its scopes- Outbound webhooks with a per-event filter and automatic retries
- Full data export of a community's records
- A public catalogue endpoint for prices, caps and modules
What people build with it
Small pieces of glue, usually.
- Levy reconciliation into the accounting stack the auditor already trusts
- Payment events pushed into an ops or security tool
- Owner and tenant portals fed from the export
- Dashboards for a managing agent's portfolio
Sign in, or start on the free plan — no card.
What is not available yet
We would rather write this down than let you discover it in a sales call. Each one is a promise about someone else's product, so it is on the list and not in the product.
Slack
No Slack app. Notices reach members in the app, by email and by SMS — not into a workspace channel.
Zapier and Make
No ready-made Zaps or scenarios. The API is the same door those would use, and it is open today.
Xero, Sage and QuickBooks
No accounting connector. The ledger export and the API carry the rows; the connector is on your side or in a script.
WhatsApp Business
No WhatsApp integration. The platform exists to replace the group chat, not to feed it.
Gate and access hardware
No vendor integrations for boom gates or biometric readers. Visitor passes stay in the app and on the gate log.
A public developer portal
No published reference docs yet. The endpoints are stable and few; we will write the page when there are more of them.
Requested often enough, one of these becomes a connector and moves up into the section above. Until then the API is the answer.
How it works
Four steps, no partnership programme and no revenue share.
Authorization: Bearer trk_… to /api/v1/me to prove it works.Questions we get
Is there an API?
Yes. Keys are issued per community with read and write scopes, and /api/v1/me returns the tenant and the scopes a key holds. Further endpoints follow the same pattern.
Can I get levies into my accounting software?
Not through a ready-made connector. The ledger export and the API give you the rows; your accountant's tool or a small script does the rest. We will help you scope it.
Are there webhooks?
Yes. A subscription carries a per-event filter and receives JSON payloads; a delivery that fails is retried from a queue rather than lost.
Can I build against something real first?
Spin up a demo community in about a minute, or stay on the free plan — both can issue keys.
Build the integration you actually need.
Tell us what has to reach what, and we will tell you whether the API already does it — or exactly where it falls short.