Versioning lifecycle developer guide + outbound caller-ID note
Versioning lifecycle developer guide + outbound caller-ID note
A new developer-guide page documents the full create → draft → publish → activate flow against the public API in curl + Python, with the seven endpoints involved and six common pitfalls (publish does not auto-activate; activate fails inside the security-check window; etc.).
The API reference for POST /agent now points to the drafts flow instead of the deprecated PATCH /workflow/{workflowId} path.
The API reference for POST /conversation/outbound now documents the caller-ID fallback: if you omit fromProductId and the agent has no telephony product attached, the call dispatches from a Smallest-managed Plivo trunk with a default outbound number. The response is still 200 + conversationId, but the recipient sees the default number, not yours. For production traffic, pass fromProductId explicitly or attach a phone-number product to the agent.