Using our API via a dedicated deployment? Just replace
api.langdock.com with your deployment’s base URL: <deployment-url>/api/publicRequired Scopes
This endpoint requires theINTEGRATION_API scope.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
integrationId | string | Yes | UUID of the integration |
actionId | string | Yes | UUID of the action to update |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Action name (max 100 characters) |
description | string | No | Action description (max 1,000 characters) |
code | string | No | JavaScript code to execute |
inputFields | array | No | Input fields for the action |
requiresConfirmation | boolean | No | Whether the action requires user confirmation before running |
When you update an action, input fields are replaced with the values you send. If an input field omits
jsonSchema, the existing JSON Schema on that field (matched by slug) is preserved. To remove a JSON Schema, send jsonSchema: null explicitly.Example
Response Format
Success Response (200 OK)
Error Handling
| Status Code | Description |
|---|---|
| 400 | Invalid request body or IDs |
| 401 | Invalid or missing API key |
| 403 | No access to this integration |
| 404 | Integration or action not found |
| 409 | Action with this name already exists |
| 429 | Rate limit exceeded |
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.