Invoke resource
POST
/v1/servers/{serverId}/invokeInvoke a deployed function or HTTP resource by forwarding an HTTP request to its service URL.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| serverId | path | string | Yes | Resource ID |
Query parameters
None.
Body schema
Content type: application/json · Optional
| Field | Type | Required | Description |
|---|---|---|---|
| method | GET | POST | PUT | PATCH | DELETE | No | — |
| path | string | No | Workspace-relative file path. |
| body | object | No | — |
| expectedRevision | string | No | Optional immutable deployment revision. Invocation fails with 409 if the currently deployed function no longer matches it. |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Invocation resultapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| status | integer | No | Current lifecycle status. |
| ok | boolean | No | — |
| url | string | No | — |
| body | object | No | — |
| text | string | No | — |
| headers | object | No | — |
| deploymentRevision | string | No | — |