Private API Boundary
Veoveo has private operational routes for callbacks, signed source reads, and runtime materialization. They are not public integration surfaces.
What Public Clients Should Do
- Use documented public API groups for workspace, artifact, blob, event, search, bot, tool, and operation workflows.
- Use webhooks and tool callbacks only through documented setup flows.
- Request a public route or webhook contract when an integration needs stable external access.
- Do not depend on private callback paths, signed-source helper routes, or provider-specific runtime plumbing.
Why This Boundary Exists
Private operational routes are shaped around short-lived tokens, callback verification, provider contracts, and runtime materialization. Those details can change without notice and may expose implementation assumptions that are not appropriate for customer integrations.
Media To Add
- Diagram: public client/API surface separated from private callback and materialization paths. It helps developers choose stable integration points. Source: public API groups and webhook flow.