Create custom integration
Create a custom HTTP integration (an operator-defined API an agent's tools can call). authType 'none' (no auth) is created fully here. authType 'api_key' or 'oauth2' need a SECRET that must never pass through a model, those create the integration SHELL (name + base URL + auth type) and return { needsSecret:true, settingsUrl } pointing to Settings → Connections to add the key/secret in the app. Requires workspace-admin.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/create_workspace_integration" \ -H "Content-Type: application/json" \ -d '{ "workspace": "string", "name": "string", "authType": "none" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Create test profile POST
Create a named test profile, a reusable caller-identity bundle that backs the {{test_profile["…"]}} variables a scenario references (full_name, order_number, suburb, postcode, etc.). Two sections mirror the call-time split: testingAgentVariables are what the simulated CALLER states on the call; mainAgentVariables are handed to the AGENT UNDER TEST at call time. Use this so one scenario can be replayed against different caller/fixture data without rewriting it; attach the returned profileId to scenarios via create_scenario / update_scenario. The profile is workspace-scoped and is TEST-HARNESS data only, it never feeds the agent's own variables or runtime. Names are unique per workspace; a duplicate is rejected.
Create workspace POST
Create a new workspace (you become its owner) and return its slug. The slug is derived from the name. Use rename_workspace to change the name later.