Websites and dynamic content
Caraer’s website capabilities connect published pages with business records. Public website APIs expose the content and supporting data needed by the relevant website runtime, including pages, navigation, branding, and published paths.
Why integrate
Section titled “Why integrate”The customer’s operational data can also supply website content. A directory or vacancy website can draw from the records the company maintains, while editors manage page content and design within the supported CMS experience.
What you could build
Section titled “What you could build”Build a record-backed listing and detail experience, add an application form, and use company branding and menus to keep the website coherent. For CMS v2, use app-provided modules for the website components editors select.
Start integrating
Section titled “Start integrating”Read Dynamic content, forms, and CMS modules. Inspect the relevant Webpages or CMS v2 public operations in the API reference, starting with a published sandbox page and its environment.
CMS v1 and CMS v2 have different page and runtime contracts. Use the company’s actual CMS version rather than combining their payloads. Public APIs expose published content according to its protection rules; private API access is not a reason to publish a field. Test the final public URL and missing-data cases before launch.