API basics
YCloud resolves the tenant and Meta access token from your API key. Do not send a Meta access token in these requests.
Recommended lifecycle
Follow the Build and launch guides in order. They connect the individual API resources into an end-to-end rollout process.- Prepare and check eligibility.
- Onboard and configure the agent in a restricted test state.
- Test and evaluate single-turn, multi-turn, and representative business scenarios.
- Roll out safely from allowlisted recipients to the full audience.
- Operate and troubleshoot the live agent.
Resources covered by the workflow
Each API Reference directory has its own landing page and links to every endpoint in that area.
This release documents 62 REST operations. API-created Agents can also emit
echo and handover webhook events.
Ownership and isolation
Except for eligibility, phone-number-scoped operations require an active Public API agent binding owned by the same YCloud tenant. YCloud returns404 when the binding is missing, belongs to another tenant, or was created through an incompatible origin. This prevents one tenant or integration surface from accessing another agent.
