Function Apps vs Functions APIs
- Functions (
/functions/...) — Deploy and manage function definitions, schedules, and calls using the traditional Functions resource model (function IDs, schedules, call history, and logs). - Function Apps (
/function-apps/...) — Manage function applications by external ID, including calls, response and logs for a call, and Model Context Protocol (MCP) operations where exposed in the API reference.
Function app calls
POST /function-apps/{functionExternalId}/calls sends a request envelope: path, HTTP method, body, and a session nonce. The HTTP status is 200 when the function finishes, including when the function’s own status is not 200. A non-200 HTTP status means the API call itself failed. The function’s response envelope is returned unchanged.
Send Prefer: respond-async to receive HTTP 202 and a Location header for the poll URL. This operation is available on the beta and alpha APIs.
Function app MCP
Function app MCP endpoints are in private beta. They implement Model Context Protocol over Streamable HTTP, with JSON-RPC 2.0 and server-sent events. Pass the nonce on each call inparams._meta["com.cognite/nonce"] for methods that invoke the function, including tools/list, tools/call, and ping.
APIs in this group
- Functions — Deploy and manage serverless Python functions
- Function calls — Invoke functions and track execution
- Function schedules — Schedule recurring function invocations
- Function Apps — List and manage function applications and their calls (
/function-apps/...) as documented in the API reference for your calendar version