Learn about the Baack content experiences APIs using the use cases guides and reference docs below.
The reference docs for endpoints and the representations below provide detailed examples.
See below for details of the reference documentation for the supported concepts in the API. These are intended to be used during development as a reference rather than providing guidance on how to combine them for specific use cases.
Explore details of the API endpoints supported by Baack which you can use to build experiences for your app or product.
Lookup specific representation fields and constraints for the objects used in the Baack APIs. These docs provide low level details of every field, their use and constraints.
Explore solution focused guides to understand use cases to build experiences for your product. These guides are intended to be scoped to a specific problem space, our APIs are designed to be combined across different spaces as your usage expands.
Headless CMS supports general page like entities with multiple content types available for the entity. Content concepts can be used standalone to deliver sophisticated content experiences with support for multiple content types including text, boolean, date/time, images and templates.
Headless CRM allows enables managing, customers, associated companies and leads all integrated with the tools sales teams already use. Effortlessly push opportunities and engagements to one or multiple systems through a single API.
Leverage our rich role based access control model to power access control and permissions in your tools. Even if all you need is a model of access control you can use our role based access controls to model your permissions and roles. Our RBAC also supports managing groups for roles and assigning profiles to them to streamline access management.