BriefCatch for developers
Curated architecture and API guidance for approved BriefCatch integrations.
System overview
The moving parts and how a document travels through them.
Authentication
How an approved integration proves who it is and stays authorized.
Integration architecture
Where an integration attaches, and the boundaries it must respect.
Word add-in
What the Microsoft Word client does, and what it does not.
Scope of the API reference
The API reference is generated from a six-operation allowlist. Omission is intentional: an endpoint present in BriefCatch’s applications or internal services is not automatically an integration contract. If an operation you need is missing, treat that as a question for BriefCatch rather than an endpoint to call.