Advanced integration: agent API access

Documentation / Agentic editing and connections

The agent API is the authenticated content interface used by the Beeboo MCP package. Integrators should use its supported routes instead of scripting private storage or assuming browser-admin endpoints accept the same credentials. Every request needs valid authentication, the required scope, and access to its selected website.

Establish an authorized connection

The local MCP package calls /api/beeboo/agent on its configured gateway, documented as https://r.beeboo.app. PAT requests use an Authorization: Bearer header. Keep the credential in private configuration; never put it in a URL, source-controlled file, or conversation.

For a credential-free illustration, a read request has this shape:

GET /api/beeboo/agent/pages?site=example.com
Authorization: Bearer [supplied privately]

This is a request sketch, not a runnable authenticated example. Replace the sample website only after confirming the real domain through an authorized site inventory.

Use the supported resources

The implementation includes my-sites, pages, roots, settings, templates, languages, translations, image-upload preparation, legal settings, and shells. Methods and payloads differ by route. Read the corresponding schema before integrating; for example, root reordering and root transfers use different methods and require current root versions.

For page changes, read the current content first and include expectedPageModifiedAt. Custom-design updates require that version. Ordinary direct updates affect saved content immediately and do not manipulate editor cloud drafts.

Handle failures deliberately

Treat 401 as an authentication problem, 403 as a scope or access problem, and version conflicts as a requirement to read again. Honor Retry-After on rate limiting. Multi-resource mutations can return partial results, so do not retry blindly.

Hosted OAuth has separate discovery and token endpoints. Let a compatible client manage that exchange. See agentic editing and connections for authorization and saving and recovery for revision boundaries.