Add Functions API documentation for the commit flow

[c1-dev-bot]

Summary

Add a new documentation page (product/admin/functions-api.mdx) that documents how to manage functions programmatically via the C1 REST API.

The existing Functions docs cover only the web UI workflow. This page documents:

• The three-step commit flow for editing function code via API: CreateInitialCommit (to get signed upload URLs) → upload files to the signed URLs → CreateFinalCommit
• Creating functions with optional inline initialContent
• Publishing commits by updating publishedCommitId
• A complete bash example showing the full create-upload-finalize-publish sequence
• Other operations: list/get/delete functions, invoke, test, list commits, get commit content

Why

The API reference (auto-generated from the OpenAPI spec) advertises a content field on the commit endpoint that the server does not accept (HTTP 400). Without documentation of the working three-step flow, API users are forced to delete and recreate functions to update code — which generates new function IDs and breaks bound hooks, vault secrets, egress allowlists, and saved references.

Fixes: FN-524

---

Automated PR Notice

This PR was automatically created by c1-dev-bot as a potential implementation.

This code requires:

• Human review of the implementation approach
• Manual testing to verify correctness
• Approval from the appropriate team before merging

[linear-code]

FN-524

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
conductorone	🟢 Ready	View Preview	Jul 7, 2026, 5:17 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.