DELETE /v1/projects/{project}/workflows/{workflow}
Remove a step from a custom workflow.
curl -X DELETE https://serpon.ai/v1/projects/1/workflows/504 \
-H "Authorization: Bearer $SERPON_TOKEN" \
-H "Accept: application/json"
const res = await fetch('https://serpon.ai/v1/projects/1/workflows/504', {
method: 'DELETE',
headers: {
Authorization: `Bearer ${process.env.SERPON_TOKEN}`,
Accept: 'application/json',
},
});
const { success } = await res.json();
import os, requests
r = requests.delete(
"https://serpon.ai/v1/projects/1/workflows/504",
headers={
"Authorization": f"Bearer {os.environ['SERPON_TOKEN']}",
"Accept": "application/json",
},
)
ok = r.json()["success"]
{
"success": true,
"message": "Workflow step deleted successfully."
}
{
"message": "Workflow not found for this project."
}
Delete one workflow step.
DELETE https://serpon.ai/v1/projects/{project}/workflows/{workflow}
Deleting the last remaining step deletes the workflow with it, removing that article type from the project — subsequent article requests using it fail validation. The step and the workflow are removed in one transaction, so a failure leaves neither half-done.
Authentication
Bearer token in the Authorization header. Requires update access to the project. See Authentication.
Path parameters
The project ID.
The workflow step ID. Must belong to that project.
Example
Response fields
Always true on 200.
Confirmation text.
Errors
| Status | When |
|---|---|
401 | Missing, invalid, or expired token |
402 | Account has no active subscription |
403 | No update access to the project |
404 | No such step, or it belongs to another project |
429 | Rate limit exceeded |
See Errors for the full reference.
Tips
Deletion leaves a gap in the numbering — removing step 2 of four leaves steps 1, 3, and 4. Execution still follows ascending order, so the pipeline keeps working, but any prompt referencing {step_2_output} now resolves to nothing. Fix those references, and use reorder to close the gap.