Ask for an integration

Tell us what your agency needs Briesa to connect to, and what it would save you. A person reads every request.

Questions

  • What does Briesa connect to today?

    A group can sign its people in through its own identity provider, by OpenID Connect or SAML. Other software can use Briesa's own API with a key an owner or admin makes, limited to what that key is allowed to do; webhooks tell a receiver when something recorded in the audit log changes; and AI clients can reach the assistant's tools over MCP with the same keys.

  • What about accounting, listing portals, calendars and bank feeds?

    They are listed in Settings and not connectable yet. Xero and MYOB, the listing portals, calendar sync and a bank feed for the trust reconciliation are all planned, and none has a date we are ready to commit to. If one of them is what you need, say so here: it is the reason this form exists.

  • Which bank feed will the trust accounts use?

    The provider has not been chosen. The trust module deliberately leaves the feed and its matching out until it is, so receipts, disbursements and the monthly reconciliation work without one.

  • Can we connect something ourselves?

    Yes, with an API key. There is no second API: a key works against the same routes the screens use, bounded by its scopes, and everything it writes is recorded in the audit log under the person who made it, so nothing it does is anonymous.

  • Which services does Briesa itself rely on?

    Those are subprocessors rather than integrations: the providers that handle data on Briesa's behalf, and where they hold it. They are listed on their own page.

  • What happens after I send a request?

    It is filed with a reference you can quote, and a person reads it. We will not promise a date we cannot keep; if what you asked for is already planned, we will tell you where it stands.