RECIBIDO → REVISION → FIRMA → IMPLEMENTACION → COMPLETADO (see XC Statuses). Status changes are tracked in XC Status Histories and can trigger notification emails and downstream automation (e.g. via the DocuSign webhook).PUT /xc/requests/draft) with relaxed validation (requester name/email may be blank, no status assigned) and later finalized. Re-submitting the same draft id updates it in place; omitting id creates a new one.REVISION and undoes SOW-related state in one transaction — deletes the contract setting, relabels SOW documents to EXTRA, and voids open DocuSign envelopes.external_opportunity_parent_id/external_opportunity_parent_optional_id reference Salesforce opportunities; the corresponding _number fields are auto-resolved from Salesforce rather than meant to be set directly.List XC requests returns not just paginated data, but also a summary object keyed by canonical status code (e.g. COMPLETA, FALTA_INFO) with total and delayed counts, computed over the same filters as the list (minus pagination). If a text search matches nothing locally, it automatically retries against Salesforce opportunities.Create and the draft upsert both accept an initial connections array (up to 100), using the same fields as XC Connections — see that folder for the full Side A/Side B field reference.GET /v1/xc/requestsPOST /v1/xc/requestsPUT /v1/xc/requests/draftGET /v1/xc/requests/{id}GET /v1/xc/requests/{id}/detailsPATCH /v1/xc/requests/{id}PATCH /v1/xc/requests/{id}/statusPATCH /v1/xc/requests/{id}/revert-to-revisionDELETE /v1/xc/requests/{id}routes/v1/xc/requests.router.jscontrollers/xc/requests.controller.jsservices/xc/requests.service.jsentities/xc-request.js