Blissbook gives you two ways to connect your content and compliance data to your own systems: a REST API for pulling reports and an MCP server that lets AI tools read and write your content on your behalf.
This article covers what each one does and how to switch it on. The full technical reference lives at blissbook.com/developers, which is the page to hand your IT or development team.
Which one do you need?
The two interfaces solve different problems.
Reach for the REST API when a system needs to pull data out of Blissbook on a schedule. It covers signature records, signed PDFs, saved report exports, and your audit log. Your IT team authenticates with a key and secret they store in their own system. This is the right choice for feeding a BI dashboard, archiving acknowledgements, or piping events into your SIEM.
Reach for the MCP server when you want an AI tool to work with Blissbook directly. Connect Claude, ChatGPT, or your company's own chatbot. Authentication happens over OAuth, so there is no key to copy, and the connection acts as the person who authorized it.