Migrating a client to v3 and hit a gap I can’t work around: there seems to be no v3 equivalent of:
POST /api/v2/workflow/{workflow-id}/approve/{approval-request-id}
This looks like an oversight rather than a decision, because v3 already models approval jobs. Is an approve endpoint planned?
In a related note, v3 also does not expose a job dependencies. For a job gated behind an approval, v2 returns dependencies and requires which is useful.
2 posts - 2 participants
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Missing docs - V2 API tests endpoint | 0 | 14.38 | 21-08-2026 |
| 2 | Feature Request: Custom Workflow/Pipeline Labels in the Web UI | 0 | 7.47 | 21-09-2026 |
| 3 | How can I mark a deploy as "canceled" when its workflow got canceled? | 0 | 6.17 | 03-08-2026 |
| 4 | How to get email PDF invoices back? | 0 | 10.61 | 25-09-2026 |
| 5 | Customise pipelines vie | 0 | 19.59 | 09-08-2026 |
| 6 | Boolean parameters as environment variables | 0 | 5.83 | 20-08-2026 |
| 7 | Enable auto-cancel but exclude branches | 0 | 14.16 | 07-08-2026 |
| 8 | Choose OpenAI or xAI Grok to Power 3CX AI Agents | 0 | 5.92 | 17-09-2026 |
| 9 | RFC: Procedure Manifests - Mechanism for AI Agents to Resolve Contractual Disputes | 0 | 9.98 | 28-09-2026 |
| 10 | Cache of prefix-dev/pixi orb appears to grow indefinitely - where do I report issues with this orb? | 0 | 8.78 | 04-09-2026 |