Sites already support passing variables through deploy webhooks:
POST /webhooks/servers/{id}/sites/{id}/deploy Body: {"variables": {"tag": "2026.03.16.3"}} → $TAG is available in the deploy script ✅
The same pattern doesn't work for Applications:
POST /webhooks/servers/{id}/applications/{id}/deploy Body: {"variables": {"tag": "2026.03.16.3"}} → $TAG is empty in the deploy script ❌
Use case: We use deploy webhooks to trigger versioned deploys from CI — passing a git tag as a variable so the deploy script can run git checkout tags/$TAG. This works great for sites but blocks us from doing the same for applications.
Ask: Bring the /applications/ webhook endpoint to parity with /sites/ for variable injection. No new interface needed — just the same body parsing behavior already implemented for sites.
This unlocks proper tag-based deploys for application servers via external CI triggers.
