Compute
Run governed outbound work for your organisation: prepared, parameterised APIs and one-off generic HTTP calls, all bounded by a layered egress allow-list and Vault credential indirection so secrets are resolved server-side and never exposed to the caller. Functions (managed serverless handlers) and a Browser family are coming soon.
/api/v1/computeAutomation triggers: view every Compute event, payload field, and predicate.
APIs
An API is a federated zone holding shared config — base URL, variables, default headers, an auth strategy — plus the Vault credential references its requests may use. APIs sit directly under the company (registered in IAM as org/{company_id}/api/{id}). An API references a Vault credential by {namespace, credential} only; it never stores a secret value. The API is the zone you grant on to cover all of its requests. Every request and call must stay under the API's base URL. APIs are strict by default (only saved requests run); a non-strict API also takes direct calls limited by its allowed_methods and denied_paths.
/api/v1/compute/apisCreate API
Create an API. This is an org-border operation: the API becomes its own zone and the creator receives the API bundle. Provide base config and, optionally, the Vault credential its calls are sent with (a reference only).
Bearer <token> + X-Company-Id header required. Permission: compute:apis:create (on org/{company_id})
Request Body
| Name | Type | Description |
|---|---|---|
name* | string | Display name |
description | string | null | Optional description |
base_url | string | null | Base URL prepended to each relative request path. Every request and direct call must stay under it (same scheme, host and port, at or below its path). Required when strict is false. |
variables | object | API-level variables referenced as {{vars.*}}Default: {} |
default_headers | object | Headers applied to every request unless overriddenDefault: {} |
credential_ref | CredentialRef | null | The Vault credential calls are sent with, or null for none. Its Vault type and config decide how it is sent: an api_key in its config.name header (after config.prefix and a space, when set) or query parameter, a bearer_token, a JWT Vault signs for a signed_jwt, or an OAuth access token as Authorization: Bearer, a basic_auth as Authorization: Basic with config.username. Other types fail the invocation with credential_unsupported. |
strict | boolean | Only the saved requests run. false enables direct calls (POST /apis/{api_id}/call) and needs a valid http(s) base_url, otherwise 422.Default: true |
allowed_methods | string[] | Methods a direct call may use, from GET, HEAD, POST, PUT, PATCH, DELETE.Default: ["GET", "HEAD"] |
denied_paths | string[] | Paths a direct call can never reach, each starting with /. A path also covers everything below it; matching ignores case and percent-encoding, and * matches any characters.Default: [] |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | API ID |
company_id* | string | Company ID |
name* | string | Display name |
description* | string | null | Description, or null |
base_url* | string | null | Base URL, or null |
variables* | object | API variables |
default_headers* | object | Default headers |
credential_ref* | CredentialRef | null | The Vault credential calls are sent with, or null (a reference only). An API saved before IDs were required may hold names; its calls fail with credential_unavailable until the credential is picked again. |
principal_id* | string | null | The API's own IAM principal, minted by the first public invoke of a credential-bearing request (internal invoke never mints), or by a connector install. Null until then. |
strict* | boolean | Whether only the saved requests run |
allowed_methods* | string[] | Methods a direct call may use |
denied_paths* | string[] | Paths a direct call can never reach |
connector* | string | null | Catalog slug the API was installed from (see Connectors); null for an ordinary API |
connector_connection_method* | string | null | The catalog connection method the connector was installed with, e.g. user or installation for GitHub; null for an ordinary API |
managed_namespace_id* | string | null | The Vault namespace a connector API owns; null otherwise |
connector_account* | object | null | The connected account from the last successful identity refresh: {login, name, avatar_url, refreshed_at}; null otherwise |
created_by* | string | null | Principal ID of whoever created or installed the API |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{
"name": "Stripe",
"base_url": "https://api.stripe.com",
"default_headers": {"Accept": "application/json"},
"credential_ref": {
"namespace": "11111111-1111-4111-8111-111111111111",
"credential": "22222222-2222-4222-8222-222222222222"
}
}'Response
201 Created{
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"name": "Stripe",
"description": null,
"base_url": "https://api.stripe.com",
"variables": {},
"default_headers": {"Accept": "application/json"},
"credential_ref": {
"namespace": "11111111-1111-4111-8111-111111111111",
"credential": "22222222-2222-4222-8222-222222222222"
},
"principal_id": null,
"strict": true,
"allowed_methods": ["GET", "HEAD"],
"denied_paths": [],
"connector": null,
"connector_connection_method": null,
"managed_namespace_id": null,
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
}/api/v1/compute/apisList APIs
List the company's APIs. Results are filtered by view access.
Bearer <token> + X-Company-Id header required. Filtered by compute:apis:view
Response Fields
| Name | Type | Description |
|---|---|---|
[]* | Api[] | APIs the caller may view (same shape as Get API) |
curl https://platform.ergondata.ai/api/v1/compute/apis \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK[
{
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"name": "Stripe",
"description": null,
"base_url": "https://api.stripe.com",
"variables": {},
"default_headers": {"Accept": "application/json"},
"credential_ref": {"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"},
"principal_id": null,
"strict": true,
"allowed_methods": ["GET", "HEAD"],
"denied_paths": [],
"connector": null,
"connector_connection_method": null,
"managed_namespace_id": null,
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
}
]/api/v1/compute/apis/{api_id}Get API
Retrieve a single API by ID, including its config and credential references.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:view (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | API ID |
company_id* | string | Company ID |
name* | string | Display name |
description* | string | null | Description, or null |
base_url* | string | null | Base URL, or null |
variables* | object | API variables |
default_headers* | object | Default headers |
credential_ref* | CredentialRef | null | The Vault credential calls are sent with, {namespace, credential} by ID, or null (a reference only, never the value). An API saved before IDs were required may hold names; its calls fail with credential_unavailable until the credential is picked again. |
principal_id* | string | null | The API's IAM principal, or null until the first public invoke of a credential-bearing request |
strict* | boolean | Whether only the saved requests run |
allowed_methods* | string[] | Methods a direct call may use |
denied_paths* | string[] | Paths a direct call can never reach |
connector* | string | null | Catalog slug the API was installed from (see Connectors); null for an ordinary API |
connector_connection_method* | string | null | The catalog connection method the connector was installed with, e.g. user or installation for GitHub; null for an ordinary API |
managed_namespace_id* | string | null | The Vault namespace a connector API owns; null otherwise |
connector_account* | object | null | The connected account from the last successful identity refresh: {login, name, avatar_url, refreshed_at}; null otherwise |
created_by* | string | null | Principal ID of whoever created or installed the API |
curl https://platform.ergondata.ai/api/v1/compute/apis/{api_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"name": "Stripe",
"description": null,
"base_url": "https://api.stripe.com",
"variables": {"api_version": "2024-06-20"},
"default_headers": {"Accept": "application/json"},
"credential_ref": {"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"},
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"strict": true,
"allowed_methods": ["GET", "HEAD"],
"denied_paths": [],
"connector": null,
"connector_connection_method": null,
"managed_namespace_id": null,
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
}/api/v1/compute/apis/{api_id}Update API
Update config, the credential reference, or the call policy. Only provided fields are changed. Changing credential_ref changes the stored reference only (never values); what the API's principal can resolve still depends on its Vault connection and grants. Turning strict off requires a valid http(s) base_url (422 compute.errors.baseUrlRequired or compute.errors.invalidBaseUrl). On a connector API, changing base_url, credential_ref or the connector's auth headers is 409 compute.errors.connectorManagedField.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Request Body
| Name | Type | Description |
|---|---|---|
name | string | New name |
description | string | New description |
base_url | string | New base URL |
variables | object | Replace API variables |
default_headers | object | Replace default headers |
credential_ref | CredentialRef | null | The Vault credential calls are sent with, {namespace, credential} by ID. Omit to keep it; null removes it. |
strict | boolean | Whether only the saved requests run |
allowed_methods | string[] | Replace the methods a direct call may use |
denied_paths | string[] | Replace the paths a direct call can never reach |
Response Fields
| Name | Type | Description |
|---|---|---|
API* | object | The updated API (same shape as Get API) |
curl -X PATCH https://platform.ergondata.ai/api/v1/compute/apis/{api_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"variables": {"api_version": "2024-06-20"}}'Response
200 OK{
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"name": "Stripe",
"description": null,
"base_url": "https://api.stripe.com",
"variables": {"api_version": "2024-06-20"},
"default_headers": {"Accept": "application/json"},
"credential_ref": {"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"},
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"strict": true,
"allowed_methods": ["GET", "HEAD"],
"denied_paths": [],
"connector": null,
"connector_connection_method": null,
"managed_namespace_id": null,
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
}/api/v1/compute/apis/{api_id}Delete API
Delete an API and cascade-delete its requests. Also soft-deletes the zone in IAM.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:delete (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/apis/{api_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/apis/{api_id}/callCall API
Send one request that no saved request maps, through a non-strict API: its base URL, default headers, credential (resolved as the API principal and redacted) and company egress. The path, query, headers and body are sent as given and never templated. Refusals happen before egress and create no invocation: 409 compute.errors.apiStrict while the API is strict, 403 compute.errors.methodNotAllowed for a method outside allowed_methods, 403 compute.errors.pathDenied when a denied path covers the call, and 400 compute.errors.baseUrlViolation for a URL that leaves the base URL (a .. segment in any encoding, //, a backslash, or a Host header). Recorded as an invocation with target_kind='api_call'.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:call (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Request Body
| Name | Type | Description |
|---|---|---|
method* | string | HTTP method; must be in the API's allowed_methods |
path* | string | Path under the base URL, starting with /, with no ? or # |
query | object | Query parameters; values are sent as stringsDefault: {} |
headers | object | Headers, merged over the API's default headersDefault: {} |
body | any | Request body; objects and arrays are sent as JSON |
Response Fields
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation audit row ID |
status* | string | succeeded or failed |
response | object | null | The upstream response (status, headers, body), with any secrets redacted |
failure_kind | string | null | egress_denied, credential_denied, credential_reconnect_required, credential_unavailable, credential_unsupported, upstream_error, timeout, or internal — on failure |
failure_message | string | null | Human-readable failure detail, or null |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/call \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"method": "GET", "path": "/v1/customers", "query": {"limit": "3"}}'Response
200 OK{
"invocation_id": "inv_01h2x3y4-5678-4abc-9012-3456789abcdf",
"status": "succeeded",
"response": {
"status": 200,
"headers": {"content-type": "application/json"},
"body": {"object": "list", "data": [], "has_more": false}
},
"failure_kind": null,
"failure_message": null
}/api/v1/compute/companies/{company_id}/api-prefsGet API Preferences
Return the caller's per-user API-tree preferences — the favorite API and custom drag order shown in the sidebar tree. Personal UI state (not an IAM resource): requires a user token and is scoped to the path company.
Bearer <token> + X-Company-Id header required. Requires a user token (personal UI state — no IAM permission).
Path Parameters
| Name | Type | Description |
|---|---|---|
company_id* | string (UUID) | Organization ID |
Response Fields
| Name | Type | Description |
|---|---|---|
favorite_api_id | string (UUID) | null | Pinned favorite API, or null |
api_order | array<UUID> | The caller's API display order (APIs missing here fall back to server order) |
curl https://platform.ergondata.ai/api/v1/compute/companies/{company_id}/api-prefs \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"favorite_api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"api_order": ["c1a2b3c4-d5e6-4f70-8901-23456789abcd"]
}/api/v1/compute/companies/{company_id}/api-prefsUpdate API Preferences
Update the caller's favorite API and/or API ordering. Only provided fields are changed. Personal UI state — requires a user token.
Bearer <token> + X-Company-Id header required. Requires a user token (personal UI state — no IAM permission).
Path Parameters
| Name | Type | Description |
|---|---|---|
company_id* | string (UUID) | Organization ID |
Request Body
| Name | Type | Description |
|---|---|---|
favorite_api_id | string (UUID) | null | Pin a favorite API, or null to clear it |
api_order | array<UUID> | Replace the API display order |
Response Fields
| Name | Type | Description |
|---|---|---|
favorite_api_id | string (UUID) | null | Pinned favorite API, or null |
api_order | array<UUID> | The caller's API display order |
curl -X PUT https://platform.ergondata.ai/api/v1/compute/companies/{company_id}/api-prefs \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"favorite_api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd", "api_order": ["c1a2b3c4-d5e6-4f70-8901-23456789abcd"]}'Response
200 OK{
"favorite_api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"api_order": ["c1a2b3c4-d5e6-4f70-8901-23456789abcd"]
}Connectors
A connector is an API installed from Compute's catalog (GitHub first). The catalog entry fixes the base URL, default headers and call policy, and offers one or more connection methods, each a Vault credential type (GitHub: user, a person's account through an OAuth app, or installation, a GitHub App installed on an organization or account); the installer picks a method and gives a name, the method's fields and its secret. The install creates the API plus a system-managed Vault namespace the API owns, holding the credential and already granted to the API principal. While the API is a connector, its base_url, credential_ref and the connector's auth headers can't be edited (409 connectorManagedField), and deleting the API deletes the namespace first. Detaching makes it an ordinary API and hands the namespace to the installer.
/api/v1/compute/connectors/catalogList Connector Catalog
The connectors that can be installed: provider, base URL, default methods, and each connection method's credential type and preset, the fields and secret the install asks for, and how the connected account is read.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:create (on org/{company_id}), the same as installing
Query Parameters
| Name | Type | Description |
|---|---|---|
limit | integer | Page size, at most 100Default: 50 |
offset | integer | Entries to skipDefault: 0 |
Response Fields
| Name | Type | Description |
|---|---|---|
total* | integer | Number of catalog entries |
items[].slug* | string | Entry id, sent as connector on install |
items[].connection_methods* | ConnectorMethod[] | The ways to install the entry, at least one |
items[].connection_methods[].slug* | string | Method id, sent as connection_method on install |
items[].connection_methods[].credential_type* | string | Vault credential type the install creates, e.g. oauth2_authorization_code or oauth2_jwt_bearer |
items[].connection_methods[].credential_preset* | object | Fixed credential config, e.g. the provider's authorize and token URLs |
items[].connection_methods[].config_templates* | object | Config values built from the fields, e.g. a token_url with an {installation_id} path segment |
items[].connection_methods[].user_fields* | ConnectorField[] | Fields the installer fills: name, label_key, kind (text or list), required, default, pattern (a regular expression a text value must match in full) and config_key (null for a field only a template uses) |
items[].connection_methods[].secret* | object | null | The secret to enter: label_key and input (password, textarea or pem) |
items[].connection_methods[].identity* | object | null | How the connected account is read: {source: "api", method, path, fields}, a call through the API, or {source: "vault"}, read by Vault with the credential |
items[].connection_methods[].next_step* | string | null | authorize when the credential must be connected through Vault's OAuth routes |
items[].default_method* | string | The method used when the install names none |
items[].base_url* | string | The installed API's base URL |
items[].default_allowed_methods* | string[] | Methods unmapped calls may use unless the install overrides them |
curl https://platform.ergondata.ai/api/v1/compute/connectors/catalog \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"items": [
{
"slug": "github",
"provider": "github",
"category": "developer_tools",
"label_key": "connectors.catalog.github.label",
"description_key": "connectors.catalog.github.description",
"icon": "/connectors/github.svg",
"connection_methods": [
{
"slug": "user",
"label_key": "connectors.methods.github.user.label",
"description_key": "connectors.methods.github.user.description",
"credential_type": "oauth2_authorization_code",
"credential_preset": {
"authorize_url": "https://github.com/login/oauth/authorize",
"token_url": "https://github.com/login/oauth/access_token",
"pkce": true
},
"config_templates": {},
"user_fields": [
{"name": "client_id", "label_key": "connectors.fields.clientId", "kind": "text", "required": true, "default": null, "pattern": null, "config_key": "client_id"},
{"name": "scopes", "label_key": "connectors.fields.scopes", "kind": "list", "required": false, "default": ["read:user"], "pattern": null, "config_key": "scopes"}
],
"secret": {"label_key": "connectors.fields.clientSecret", "input": "password"},
"identity": {"source": "api", "method": "GET", "path": "/user", "fields": {"login": "login", "name": "name", "avatar_url": "avatar_url"}},
"next_step": "authorize"
},
{
"slug": "installation",
"label_key": "connectors.methods.github.installation.label",
"description_key": "connectors.methods.github.installation.description",
"credential_type": "oauth2_jwt_bearer",
"credential_preset": {
"iat_skew_s": 60,
"exchange": {
"assertion_placement": "authorization_header",
"body_format": "json",
"response": {"access_token_field": "token", "expiry_field": "expires_at", "expiry_format": "rfc3339"}
},
"account_fields": {"login": "account.login", "avatar_url": "account.avatar_url"}
},
"config_templates": {
"token_url": "https://api.github.com/app/installations/{installation_id}/access_tokens",
"account_url": "https://api.github.com/app/installations/{installation_id}"
},
"user_fields": [
{"name": "client_id", "label_key": "connectors.fields.githubAppClientId", "kind": "text", "required": true, "default": null, "pattern": "[A-Za-z0-9._-]{1,100}", "config_key": "issuer"},
{"name": "installation_id", "label_key": "connectors.fields.githubInstallationId", "kind": "text", "required": true, "default": null, "pattern": "[0-9]{1,20}", "config_key": null}
],
"secret": {"label_key": "connectors.fields.privateKey", "input": "pem"},
"identity": {"source": "vault"},
"next_step": null
}
],
"default_method": "user",
"auth_headers": ["Authorization"],
"base_url": "https://api.github.com",
"default_headers": {"Accept": "application/vnd.github+json", "X-GitHub-Api-Version": "2022-11-28"},
"default_allowed_methods": ["GET", "HEAD"],
"openapi_url": "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json"
}
],
"total": 1
}/api/v1/compute/connectorsInstall Connector
Create an API from a catalog entry plus the Vault namespace it owns, holding one credential built from the connection method's preset, the fields and its templates, and the secret. If IAM or Vault fails, the API and whatever Vault created are deleted (403 vaultNamespaceDenied, 409 connectorNameTaken, 422 connectorCredentialInvalid, 502 creatorGrantUnavailable, apiPrincipalUnavailable or vaultUnavailable). When Vault can't undo its part, the API is kept and the answer is 502 vaultUnavailable; deleting the API retries the cleanup. 409 connectorInstallAborted if the API was deleted or detached during the install, before Vault was called. An unknown connection method (422 connectorMethodUnknown) and unknown, invalid, missing required or mismatched fields (422 connectorFieldPattern for a value that doesn't match the field's pattern) are refused before anything is created.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:create (on org/{company_id}); Vault also requires vault:namespaces:create
Request Body
| Name | Type | Description |
|---|---|---|
connector* | string | Catalog slug, e.g. github |
connection_method | string | null | The entry's connection method, e.g. user or installation for GitHub; null takes its default_method |
name* | string | Name of the API, and of the Vault namespace and credential it owns |
description | string | null | Optional description |
fields | object | Values for the method's user_fields, by nameDefault: {} |
secret | string | null | The method's secret (an OAuth client secret, or a GitHub App's private key). Sealed in Vault; never returned or stored by Compute. |
strict | boolean | Only saved requests run. Connectors default to taking direct calls.Default: false |
allowed_methods | string[] | null | Methods a direct call may use; null takes the entry's default_allowed_methods, and an empty list allows none |
denied_paths | string[] | Paths a direct call can never reach, each starting with /Default: [] |
Response Fields
| Name | Type | Description |
|---|---|---|
api* | Api | The installed API (same shape as Get API), with connector and managed_namespace_id set |
namespace_id* | string | The Vault namespace the API owns |
credential_id* | string | The credential in that namespace |
next_step* | string | null | authorize: connect the credential with Vault's POST /credentials/{credential_id}/oauth/authorize before the API can call the provider. null: it works at once; refresh the connector identity to check the fields and key. |
curl -X POST https://platform.ergondata.ai/api/v1/compute/connectors \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{
"connector": "github",
"connection_method": "user",
"name": "GitHub (Ana)",
"fields": {"client_id": "{client_id}", "scopes": ["read:user", "repo"]},
"secret": "{client_secret}"
}'Response
201 Created{
"api": {
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "GitHub (Ana)",
"base_url": "https://api.github.com",
"credential_ref": {"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"},
"strict": false,
"allowed_methods": ["GET", "HEAD"],
"connector": "github",
"connector_connection_method": "user",
"managed_namespace_id": "11111111-1111-4111-8111-111111111111",
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
},
"namespace_id": "11111111-1111-4111-8111-111111111111",
"credential_id": "22222222-2222-4222-8222-222222222222",
"next_step": "authorize"
}/api/v1/compute/apis/{api_id}/connector/identityRefresh Connector Identity
Read the connected account with the identity of the connection method the API was installed with, and store its login, name and avatar_url as connector_account. For an account read through the API (GitHub user: GET /user) the call runs as a call of the API, with company egress and the credential resolved as the API principal; a failed call still answers 200 with the failed invocation and leaves connector_account as it was. For a GitHub App installation, Vault reads the account with the credential (the app's JWT never leaves Vault) and invocation is null; when no account comes back the answer is 502 connectorAccountUnavailable with params.reason (e.g. http_401, http_404, host_denied). 409 notConnector for an API not installed from a connector, 409 connectorWithoutIdentity when the method has none.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Response Fields
| Name | Type | Description |
|---|---|---|
api* | Api | The API, with connector_account |
invocation* | InvokeResponse | null | The identity call: invocation_id, status, response, failure_kind, failure_message. Null when Vault read the account. |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/connector/identity \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"api": {
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"connector": "github",
"connector_account": {
"login": "ana",
"name": "Ana Souza",
"avatar_url": "https://avatars.githubusercontent.com/u/1",
"refreshed_at": "2026-11-09T14:00:00+00:00"
},
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
},
"invocation": {
"invocation_id": "9f8e7d6c-5b4a-4321-8f0e-1d2c3b4a5968",
"status": "succeeded",
"response": {"status": 200, "headers": {}, "body": {"login": "ana"}},
"failure_kind": null,
"failure_message": null
}
}/api/v1/compute/apis/{api_id}/detachDetach Connector
Make a connector API an ordinary API. Vault hands the namespace to the installer as an ordinary namespace; the API keeps its credential references and Vault access, so its calls keep working. connector, connector_connection_method, managed_namespace_id and connector_account are cleared and every field becomes editable. 409 notConnector; 502 vaultUnavailable if Vault can't release it, with nothing changed.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Response Fields
| Name | Type | Description |
|---|---|---|
Api* | Api | The detached API (same shape as Get API) |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/detach \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "GitHub (Ana)",
"base_url": "https://api.github.com",
"connector": null,
"connector_connection_method": null,
"managed_namespace_id": null,
"connector_account": null,
"created_by": "a1b2c3d4-0000-4000-8000-000000000001"
}Requests
A request is a single prepared call — the leaf of an API. It carries a method, path, headers, query, body, and a params_schema for caller-filled, non-secret inputs. Invoking runs the request on the shared outbound engine. Credential indirection applies: the API's own principal resolves the Vault secret, the caller never holds it, and the response is redacted.
/api/v1/compute/apis/{api_id}/requestsCreate Request
Create a request in an API. kind is rest (default) or graphql; for graphql the method is forced to POST. A relative path is appended to the API base_url. The URL must stay under the base URL: a path that leaves it (another host, a .. segment in any encoding, //, a backslash) is 400 compute.errors.baseUrlViolation, on create and edit. path may template {{vars.*}} and {{params.*}}; placeholders count as one plain segment here and the rendered URL is checked again at invoke.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:requests:create (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Request Body
| Name | Type | Description |
|---|---|---|
name* | string | Display name |
kind | string | rest or graphqlDefault: rest |
method* | string | GET, POST, PUT, PATCH, or DELETE (forced to POST for graphql) |
path* | string | Path appended to base_url when relative; an absolute http(s):// URL must be under base_url. May template {{vars.*}} / {{params.*}} |
headers | object | Per-request headersDefault: {} |
query | object | Query-string templateDefault: {} |
body | any | null | Body template; for graphql: {query, variables} |
params_schema | object | null | JSON Schema for the caller-filled parameters. Becomes the tool's args_schema. |
response_schema | object | null | JSON Schema describing the response |
expose_as_tool | boolean | When true, registers a row in IAM's tools table for this requestDefault: false |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | Request ID |
company_id* | string | Company ID |
api_id* | string | Parent API ID |
name* | string | Display name |
kind* | string | rest or graphql |
method* | string | HTTP method |
path* | string | Path template |
headers* | object | Per-request headers |
query* | object | Query template |
body* | any | null | Body template, or null |
params_schema* | object | null | Params JSON Schema, or null |
response_schema* | object | null | Response JSON Schema, or null |
expose_as_tool* | boolean | Whether registered as a tool |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{
"name": "Get invoice",
"kind": "rest",
"method": "GET",
"path": "/v1/invoices/{{params.invoice_id}}",
"headers": {"Accept": "application/json"},
"params_schema": {
"type": "object",
"required": ["invoice_id"],
"properties": {"invoice_id": {"type": "string"}}
},
"expose_as_tool": true
}'Response
201 Created{
"id": "r1234567-89ab-4cde-f012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "Get invoice",
"kind": "rest",
"method": "GET",
"path": "/v1/invoices/{{params.invoice_id}}",
"headers": {"Accept": "application/json"},
"query": {},
"body": null,
"params_schema": {
"type": "object",
"required": ["invoice_id"],
"properties": {"invoice_id": {"type": "string"}}
},
"response_schema": null,
"expose_as_tool": true
}/api/v1/compute/apis/{api_id}/requestsList Requests
List the requests in an API.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:view (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
Response Fields
| Name | Type | Description |
|---|---|---|
[]* | Request[] | Requests in the API (same shape as Get Request) |
curl https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK[
{
"id": "r1234567-89ab-4cde-f012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "Get invoice",
"kind": "rest",
"method": "GET",
"path": "/v1/invoices/{{params.invoice_id}}",
"headers": {"Accept": "application/json"},
"query": {},
"body": null,
"params_schema": {"type": "object", "required": ["invoice_id"], "properties": {"invoice_id": {"type": "string"}}},
"response_schema": null,
"expose_as_tool": true
}
]/api/v1/compute/apis/{api_id}/requests/{request_id}Get Request
Retrieve a single request by ID.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:view (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
request_id* | string | Request ID |
Response Fields
| Name | Type | Description |
|---|---|---|
Request* | object | The request (id, name, kind, method, path, headers, query, body, params_schema, response_schema, expose_as_tool) |
curl https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests/{request_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"id": "r1234567-89ab-4cde-f012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "Get invoice",
"kind": "rest",
"method": "GET",
"path": "/v1/invoices/{{params.invoice_id}}",
"headers": {"Accept": "application/json"},
"query": {},
"body": null,
"params_schema": {"type": "object", "required": ["invoice_id"], "properties": {"invoice_id": {"type": "string"}}},
"response_schema": null,
"expose_as_tool": true
}/api/v1/compute/apis/{api_id}/requests/{request_id}Update Request
Edit a request. Only provided fields are changed.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:requests:edit (on the request)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
request_id* | string | Request ID |
Request Body
| Name | Type | Description |
|---|---|---|
name | string | New name |
kind | string | rest or graphql |
method | string | New HTTP method |
path | string | New path template |
headers | object | Replace headers |
query | object | Replace query template |
body | any | Replace body template |
params_schema | object | Replace params schema |
response_schema | object | Replace response schema |
expose_as_tool | boolean | Toggle tool registration |
Response Fields
| Name | Type | Description |
|---|---|---|
Request* | object | The updated request |
curl -X PATCH https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests/{request_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"name": "Get invoice by ID"}'Response
200 OK{
"id": "r1234567-89ab-4cde-f012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"api_id": "c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"name": "Get invoice by ID",
"kind": "rest",
"method": "GET",
"path": "/v1/invoices/{{params.invoice_id}}",
"headers": {"Accept": "application/json"},
"query": {},
"body": null,
"params_schema": {"type": "object", "required": ["invoice_id"], "properties": {"invoice_id": {"type": "string"}}},
"response_schema": null,
"expose_as_tool": true
}/api/v1/compute/apis/{api_id}/requests/{request_id}Delete Request
Delete a request.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:requests:delete (on the request)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
request_id* | string | Request ID |
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests/{request_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/apis/{api_id}/requests/{request_id}/invokeInvoke Request
Run the request with caller-supplied, non-secret params (validated against params_schema and rendered into the final call). Credential indirection: when the API has an auth strategy and a credential reference, Compute resolves the Vault secret as the API's own principal and redacts it — the caller never holds it and needs no Vault permission. The rendered URL must stay under the API's base URL, otherwise the invocation fails with base_url_violation before egress; the target is then bounded by the layered egress allow-list.
Bearer <token> + X-Company-Id header required. Permission: compute:apis:requests:invoke (on the request or API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API ID |
request_id* | string | Request ID |
Request Body
| Name | Type | Description |
|---|---|---|
params | object | Non-secret, invoke-time inputs validated against the request's params_schemaDefault: {} |
Response Fields
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation audit row ID |
status* | string | queued, running, succeeded, failed, or cancelled |
response | object | null | The upstream response (status, headers, body), with any secrets redacted |
failure_kind | string | null | egress_denied, base_url_violation, credential_denied, credential_reconnect_required, credential_unavailable, credential_unsupported, upstream_error, timeout, handler_error, or internal — on failure |
failure_message | string | null | Human-readable failure detail, or null |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/requests/{request_id}/invoke \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"params": {"invoice_id": "in_1MqABCdef"}}'Response
200 OK{
"invocation_id": "inv_01h2x3y4-5678-4abc-9012-3456789abcde",
"status": "succeeded",
"response": {
"status": 200,
"headers": {"content-type": "application/json"},
"body": {"id": "in_1MqABCdef", "amount_due": 4200, "currency": "usd", "status": "paid"}
},
"failure_kind": null,
"failure_message": null
}Generic HTTP
An API-less, org-scoped one-off outbound call — the governed home for the legacy automations.http action. Gated by the org-border capability compute:http:request (a consumer-granted capability toggled on the agent/automation that will hold it, never offered from the global IAM drawer). Unlike API requests, there is no credential indirection: when credential_ref is set the calling principal itself must hold vault:credentials:use. Resolution is still server-side and redacted.
/api/v1/compute/http/requestGeneric HTTP Request
Make a one-off outbound HTTP call with a full {method, url, headers, query, body} and an optional Vault credential_ref. Org-scoped, so it needs only service access + the org permission — no connection, no API. Bounded by the platform floor and company egress policy, and additionally by the caller's own per-principal (Layer-2) policy when one exists. Stored API request invokes do not apply Layer 2.
Bearer <token> + X-Company-Id header required. Permission: compute:http:request (on org/{company_id})
Request Body
| Name | Type | Description |
|---|---|---|
method* | string | HTTP method (GET, POST, …) |
url* | string | Absolute target URL |
headers | object | Request headersDefault: {} |
query | object | Query-string parametersDefault: {} |
body | any | null | Request body |
credential_ref | CredentialRef | null | Optional Vault credential {namespace, credential} by ID. When set, the CALLING principal must itself hold vault:credentials:use (no indirection). It is sent the way its Vault type and config describe, as for an API. |
Response Fields
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation audit row ID |
status* | string | queued, running, succeeded, failed, or cancelled |
response | object | null | The upstream response (status, headers, body), with any secrets redacted |
failure_kind | string | null | egress_denied, credential_denied, credential_reconnect_required, credential_unavailable, credential_unsupported, upstream_error, timeout, handler_error, or internal |
failure_message | string | null | Failure detail, or null |
curl -X POST https://platform.ergondata.ai/api/v1/compute/http/request \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{
"method": "GET",
"url": "https://api.example.com/v1/status",
"headers": {"Accept": "application/json"},
"credential_ref": {"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"}
}'Response
200 OK{
"invocation_id": "inv_02a1b2c3-4d5e-4f60-8901-23456789abcd",
"status": "succeeded",
"response": {
"status": 200,
"headers": {"content-type": "application/json"},
"body": {"ok": true, "region": "us-east-1"}
},
"failure_kind": null,
"failure_message": null
}Egress Policies
The configurable layers of the outbound allow-list behind compute:http:request and API requests. A hardcoded platform floor (deny private/loopback/link-local/reserved, including the cloud metadata endpoint 169.254.169.254) is always on, not configurable, and has no endpoint. Above it sits the company allow-list (deny by default), and an optional per-principal subset for a specific agent/automation. A target is allowed only if every applicable layer permits it: one-off compute.http.request calls apply the floor and company allow-list, plus the caller's per-principal policy when one exists; stored API request invokes and direct API calls apply the floor and company allow-list only.
/api/v1/compute/egress/company-policyGet Company Egress Policy
Read the company (Layer-1) egress policy. Default state is disabled / allow-none — out of the box no outbound call succeeds past the platform floor.
Bearer <token> + X-Company-Id header required. Permission: compute:egress:view (on org/{company_id})
Response Fields
| Name | Type | Description |
|---|---|---|
company_id* | string | Company ID |
enabled* | boolean | When false, no target passes Layer 1 (deny-all) |
allow_hosts* | string[] | Hostname / suffix allow-list, or ["*"] for all public hosts (still subject to the floor) |
curl https://platform.ergondata.ai/api/v1/compute/egress/company-policy \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"enabled": true,
"allow_hosts": ["api.stripe.com", "*.example.com"]
}/api/v1/compute/egress/company-policySet Company Egress Policy
Enable/disable company egress and set the hostname allow-list. The allow-list may be specific hosts/suffixes or ["*"] for all public hosts (still subject to the platform floor). This is company-wide config — the superset every principal draws from.
Bearer <token> + X-Company-Id header required. Permission: compute:egress:manage (on org/{company_id})
Request Body
| Name | Type | Description |
|---|---|---|
enabled* | boolean | Enable or disable company egress |
allow_hosts | string[] | Hostname / suffix allow-list, or ["*"] for all public hostsDefault: [] |
Response Fields
| Name | Type | Description |
|---|---|---|
company_id* | string | Company ID |
enabled* | boolean | Whether egress is enabled |
allow_hosts* | string[] | The stored allow-list |
curl -X PUT https://platform.ergondata.ai/api/v1/compute/egress/company-policy \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"enabled": true, "allow_hosts": ["api.stripe.com", "*.example.com"]}'Response
200 OK{
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"enabled": true,
"allow_hosts": ["api.stripe.com", "*.example.com"]
}/api/v1/compute/egress/principal-policies/{principal_id}Get Principal Egress Policy
Read a consumer's per-principal (Layer-2) allow-list. If no policy exists, the principal inherits the company policy as-is.
Bearer <token> + X-Company-Id header required. Permission: compute:egress:view (on org/{company_id})
Path Parameters
| Name | Type | Description |
|---|---|---|
principal_id* | string | The agent / automation principal that holds the capability |
Response Fields
| Name | Type | Description |
|---|---|---|
company_id* | string | Company ID |
principal_id* | string | Consumer principal ID |
principal_type* | string | agent, automation, or service |
allow_hosts* | string[] | Subset of the company allow-list; empty when no policy is stored |
curl https://platform.ergondata.ai/api/v1/compute/egress/principal-policies/{principal_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"principal_type": "agent",
"allow_hosts": ["api.stripe.com"]
}/api/v1/compute/egress/principal-policies/{principal_id}Set Principal Egress Policy
Set a consumer's per-principal allow-list. The list is intersected with the company policy at save time — entries the company list would not permit are dropped, so a per-principal policy can only ever narrow Layer 1, never widen it.
Bearer <token> + X-Company-Id header required. Permission: compute:egress:manage (on org/{company_id})
Path Parameters
| Name | Type | Description |
|---|---|---|
principal_id* | string | Consumer principal ID |
Request Body
| Name | Type | Description |
|---|---|---|
principal_type* | string | agent, automation, or service |
allow_hosts | string[] | Requested subset of the company allow-list (intersected at save)Default: [] |
Response Fields
| Name | Type | Description |
|---|---|---|
company_id* | string | Company ID |
principal_id* | string | Consumer principal ID |
principal_type* | string | agent, automation, or service |
allow_hosts* | string[] | The effective stored allow-list after intersecting with the company policy |
curl -X PUT https://platform.ergondata.ai/api/v1/compute/egress/principal-policies/{principal_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"principal_type": "agent", "allow_hosts": ["api.stripe.com"]}'Response
200 OK{
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"principal_type": "agent",
"allow_hosts": ["api.stripe.com"]
}Invocations
The audit read surface for every call Compute makes — generic HTTP, API request, or function. Each row records status, timing, egress records, and which credential references were resolved (references only, never values). Secrets are redacted at write time, so these read endpoints surface no credential material.
/api/v1/compute/invocationsList Invocations
List invocations for the company, most recent first, with optional filters by status and target kind.
Bearer <token> + X-Company-Id header required. Permission: compute:activity:view (on org/{company_id})
Query Parameters
| Name | Type | Description |
|---|---|---|
status | string | Filter by status: queued, running, succeeded, failed, cancelled |
target_kind | string | Filter by target kind: http, request, api_call, function |
limit | integer | Results to return (≤ 200)Default: 50 |
Response Fields
| Name | Type | Description |
|---|---|---|
[]* | Invocation[] | Matching invocations (same shape as Get Invocation) |
curl "https://platform.ergondata.ai/api/v1/compute/invocations?target_kind=request&status=succeeded&limit=20" \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK[
{
"id": "inv_01h2x3y4-5678-4abc-9012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"target_kind": "request",
"request_id": "r1234567-89ab-4cde-f012-3456789abcde",
"function_id": null,
"api_id": null,
"call_method": null,
"call_path": null,
"trigger_kind": "api",
"status": "succeeded",
"failure_kind": null,
"failure_message": null,
"egress_records": [{"host": "api.stripe.com", "status": 200, "bytes_out": 312, "bytes_in": 1840}],
"used_credential_refs": [{"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"}],
"duration_ms": 412,
"output_digest": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
"queued_at": "2026-04-14T10:30:00Z",
"started_at": "2026-04-14T10:30:00Z",
"finished_at": "2026-04-14T10:30:00.412Z"
}
]/api/v1/compute/invocations/{invocation_id}Get Invocation
Retrieve a single invocation by ID, including status, output reference, egress records, and resolved credential references.
Bearer <token> + X-Company-Id header required. Permission: compute:activity:view (on org/{company_id})
Path Parameters
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation ID |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | Invocation ID |
company_id* | string | Company ID |
target_kind* | string | http, request, api_call, or function |
request_id* | string | null | Request ID when target_kind=request |
function_id* | string | null | Function ID when target_kind=function |
api_id* | string | null | API ID when target_kind=api_call |
call_method* | string | null | Method of a direct API call |
call_path* | string | null | Normalised path of a direct API call |
trigger_kind* | string | api, agent_tool, automation, app_action, or internal |
status* | string | queued, running, succeeded, failed, or cancelled |
failure_kind* | string | null | egress_denied, base_url_violation, credential_denied, credential_reconnect_required, credential_unavailable, credential_unsupported, upstream_error, timeout, handler_error, or internal |
failure_message* | string | null | Failure detail, or null |
egress_records* | object[] | null | Per-call egress records: [{host, status, bytes_out, bytes_in}] |
used_credential_refs* | CredentialRef[] | null | Which Vault references were resolved — references only, never values |
duration_ms* | integer | null | Duration in milliseconds, or null |
output_digest* | string | null | SHA-256 of the output, or null |
queued_at* | string (ISO 8601) | When queued |
started_at* | string (ISO 8601) | null | When started, or null |
finished_at* | string (ISO 8601) | null | When finished, or null |
curl https://platform.ergondata.ai/api/v1/compute/invocations/{invocation_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"id": "inv_01h2x3y4-5678-4abc-9012-3456789abcde",
"company_id": "c0ffee00-cafe-babe-dead-beefcafebabe",
"target_kind": "request",
"request_id": "r1234567-89ab-4cde-f012-3456789abcde",
"function_id": null,
"api_id": null,
"call_method": null,
"call_path": null,
"trigger_kind": "api",
"status": "succeeded",
"failure_kind": null,
"failure_message": null,
"egress_records": [{"host": "api.stripe.com", "status": 200, "bytes_out": 312, "bytes_in": 1840}],
"used_credential_refs": [{"namespace": "11111111-1111-4111-8111-111111111111", "credential": "22222222-2222-4222-8222-222222222222"}],
"duration_ms": 412,
"output_digest": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
"queued_at": "2026-04-14T10:30:00Z",
"started_at": "2026-04-14T10:30:00Z",
"finished_at": "2026-04-14T10:30:00.412Z"
}/api/v1/compute/invocations/{invocation_id}/logsGet Invocation Logs
Retrieve the stored logs for an invocation. Secrets are redacted at write time, so no credential material is surfaced. Streaming of out-of-row logs from object storage lands with later blob support; until then the log_blob_ref is returned with an empty logs array.
Bearer <token> + X-Company-Id header required. Permission: compute:activity:view (on org/{company_id})
Path Parameters
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation ID |
Response Fields
| Name | Type | Description |
|---|---|---|
invocation_id* | string | Invocation ID |
log_blob_ref* | string | null | Out-of-row log reference, or null |
logs* | object[] | Inline log lines (empty until blob streaming ships); secrets redacted |
curl https://platform.ergondata.ai/api/v1/compute/invocations/{invocation_id}/logs \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{
"invocation_id": "inv_01h2x3y4-5678-4abc-9012-3456789abcde",
"log_blob_ref": null,
"logs": []
}Access & Connections
The shared per-zone Access surface — the backend for the Security tab. Every federated zone (api for APIs, and the preview function-folder, function) exposes /{zone}/{id}/access/* with an identical shape: grant management (eligible principals, resource-types, grants), the connection-request approver inbox, and the active inbound connections list. Storage and lifecycle live in IAM; Compute proxies, gated by compute:permissions:<zone>:manage. The examples below use the API zone; substitute the zone prefix for function folders or functions.
/api/v1/compute/apis/{api_id}/access/grantsCreate Access Grant
Grant a principal a permission on the zone (or a leaf scoped beneath it). The resource defaults to the zone and must be scoped within it; the permission must be grantable at this zone (e.g. compute:apis:requests:invoke on an API).
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API (zone) ID |
Request Body
| Name | Type | Description |
|---|---|---|
principal_type* | string | member, api_key, agent, automation, workflow, team, role, or compute_api |
principal_id* | string | Principal to grant to |
permission_id* | string | IAM permission ID to grant |
resource | string | null | Resource path; defaults to the zone. Must be scoped within the zone — append /request/{request_id} to scope a grant to a single request (the governed leaf) instead of the whole API. |
effect | string | allow or denyDefault: allow |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | Grant ID |
permission_id* | string | Granted permission ID |
name* | string | Permission name |
resource* | string | Resource the grant applies to |
effect* | string | allow or deny |
is_system* | boolean | Whether the grant is system-managed |
granted_at* | string (ISO 8601) | When granted |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{
"principal_type": "agent",
"principal_id": "{agent_principal_id}",
"permission_id": "{permission_id}",
"effect": "allow"
}'Response
201 Created{
"id": "g1234567-89ab-4cde-f012-3456789abcde",
"permission_id": "p1234567-89ab-4cde-f012-3456789abcde",
"name": "compute:apis:requests:invoke",
"resource": "org/c0ffee00-cafe-babe-dead-beefcafebabe/api/c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"effect": "allow",
"is_system": false,
"granted_at": "2026-04-14T10:30:00Z"
}/api/v1/compute/apis/{api_id}/access/connection-requestsList Connection Requests
The approver inbox: incoming connection requests targeting this zone, which the zone admin approves or rejects (approve via .../connection-requests/{request_id}/approve, reject via .../reject).
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API (zone) ID |
Query Parameters
| Name | Type | Description |
|---|---|---|
status | string | Filter by request statusDefault: pending |
Response Fields
| Name | Type | Description |
|---|---|---|
[]* | ConnectionRequest[] | Connection requests targeting this zone |
curl "https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/connection-requests?status=pending" \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK[
{
"id": "cr123456-789a-4bcd-ef01-23456789abcd",
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"principal_label": "Billing Assistant",
"direction": "inbound",
"target_service": "compute",
"target_resource": "org/c0ffee00-cafe-babe-dead-beefcafebabe/api/c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"requested_permissions": ["compute:apis:requests:invoke"],
"message": "Needs to invoke the Get invoice request",
"status": "pending",
"created_at": "2026-04-14T10:25:00Z"
}
]/api/v1/compute/apis/{api_id}/access/connection-requests/{request_id}/approveApprove Connection Request
Approve an incoming connection request, optionally granting a subset of the requested permissions. Only permissions grantable at this zone are allowed.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API (zone) ID |
request_id* | string | Connection request ID |
Request Body
| Name | Type | Description |
|---|---|---|
permissions | string[] | null | Permissions to grant; defaults to the requested set |
grant | boolean | Whether to issue the grant on approvalDefault: true |
label | string | null | Optional connection label |
Response Fields
| Name | Type | Description |
|---|---|---|
id* | string | Request ID |
status* | string | approved |
connection_id | string | null | The created connection ID |
decided_by | string | null | Approving principal |
decided_at | string (ISO 8601) | null | When decided |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/connection-requests/{request_id}/approve \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"permissions": ["compute:apis:requests:invoke"], "grant": true}'Response
200 OK{
"id": "cr123456-789a-4bcd-ef01-23456789abcd",
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"target_service": "compute",
"target_resource": "org/c0ffee00-cafe-babe-dead-beefcafebabe/api/c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"status": "approved",
"connection_id": "cx987654-3210-4fed-cba9-87654321fedc",
"decided_by": "u9000000-0000-4000-8000-000000000001",
"decided_at": "2026-04-14T10:31:00Z",
"created_at": "2026-04-14T10:25:00Z"
}/api/v1/compute/apis/{api_id}/access/connectionsList Inbound Connections
List the active connections wired into this zone — each enriched with the connected principal, who established the bridge, who originally requested it, and when. This is the owning-side connections surface; revoke a connection via DELETE .../access/connections/{connection_id}.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage (on the API)
Path Parameters
| Name | Type | Description |
|---|---|---|
api_id* | string | API (zone) ID |
Response Fields
| Name | Type | Description |
|---|---|---|
[]* | InboundConnection[] | Active connections into the zone |
curl https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/connections \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK[
{
"id": "cx987654-3210-4fed-cba9-87654321fedc",
"principal_id": "a9b8c7d6-0000-4000-8000-000000000777",
"principal_type": "agent",
"principal_label": "Billing Assistant",
"target_service": "compute",
"target_resource": "org/c0ffee00-cafe-babe-dead-beefcafebabe/api/c1a2b3c4-d5e6-4f70-8901-23456789abcd",
"label": "Billing Assistant → Stripe",
"created_at": "2026-04-14T10:31:00Z",
"created_by": "u9000000-0000-4000-8000-000000000001",
"requested_by": "a9b8c7d6-0000-4000-8000-000000000777"
}
]Batch Access Grants
These JWT and X-Company-Id routes accept BatchCreateGrantsRequest and return ordered BatchCreateGrantsResponse partial-success envelopes. Operations expand as resources × permission_ids with a hard limit of 200 expanded grants. HTTP 200 may contain failures; `already_exists` is an idempotent success, so retrying the whole request or failed index/client_ref entries is safe. A side-effect error means the primary grant succeeded and only the follow-up needs reconciliation; it does not indicate rollback.
/api/v1/compute/apis/access/grants/batchBatch Create API Grants
Create grants across API roots with independent preflight and partial success. Agent ToolDef slug: `compute.api_access.create_grants_batch`.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on every concrete API root.
Request Body
| Name | Type | Description |
|---|---|---|
operations* | BatchGrantOperation[] | One or more grouped operations; maximum 200 expanded grants |
Response Fields
| Name | Type | Description |
|---|---|---|
results* | BatchGrantResult[] | Ordered results with index, client_ref, status, principal, permission_id, canonical resource, effect, grant, error_status/error_detail, and side_effect_error_status/side_effect_error_detail |
summary* | object | created, already_exists, and failed counts |
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/access/grants/batch \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"operations":[{"client_ref":"api-access","principal_type":"member","principal_id":"{principal_id}","resources":["org/{company_id}/api/{api_id}"],"permission_ids":["{permission_id}"],"effect":"allow"}]}'Response
200 OK{
"results": [{
"index": 0, "client_ref": "api-access", "status": "created",
"principal_type": "member", "principal_id": "{principal_id}",
"permission_id": "{permission_id}", "resource": "org/{company_id}/api/{api_id}",
"effect": "allow", "grant": {}, "error_status": null, "error_detail": null,
"side_effect_error_status": null, "side_effect_error_detail": null
}],
"summary": { "created": 1, "already_exists": 0, "failed": 0 }
}/api/v1/compute/function-folders/access/grants/batchBatch Create Function Folder Grants
Create grants across function-folder roots with the same ≤200 expansion, partial-success, retry, and side-effect semantics. Agent ToolDef slug: `compute.function_folder_access.create_grants_batch`.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on every concrete function-folder root.
Request Body
| Name | Type | Description |
|---|---|---|
operations* | BatchGrantOperation[] | BatchCreateGrantsRequest operations: client_ref, principal_type/id, resources, permission_ids, and effect |
Response Fields
| Name | Type | Description |
|---|---|---|
results* | BatchGrantResult[] | Ordered partial-success results with primary and side-effect errors |
summary* | object | created, already_exists, and failed counts |
curl -X POST https://platform.ergondata.ai/api/v1/compute/function-folders/access/grants/batch \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"operations":[{"principal_type":"workflow","principal_id":"{principal_id}","resources":["org/{company_id}/function-folder/{folder_id}"],"permission_ids":["{permission_id}"]}]}'Response
200 OK{
"results": [{ "index": 0, "client_ref": null, "status": "created", "principal_type": "workflow", "principal_id": "{principal_id}", "permission_id": "{permission_id}", "resource": "{function_folder_resource}", "effect": "allow", "grant": {}, "error_status": null, "error_detail": null, "side_effect_error_status": null, "side_effect_error_detail": null }],
"summary": { "created": 1, "already_exists": 0, "failed": 0 }
}/api/v1/compute/functions/access/grants/batchBatch Create Function Grants
Create grants across function roots with the same ≤200 expansion, partial-success, retry, and side-effect semantics. Agent ToolDef slug: `compute.function_access.create_grants_batch`.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on every concrete function root.
Request Body
| Name | Type | Description |
|---|---|---|
operations* | BatchGrantOperation[] | BatchCreateGrantsRequest operations: client_ref, principal_type/id, resources, permission_ids, and effect |
Response Fields
| Name | Type | Description |
|---|---|---|
results* | BatchGrantResult[] | Ordered partial-success results with primary and side-effect errors |
summary* | object | created, already_exists, and failed counts |
curl -X POST https://platform.ergondata.ai/api/v1/compute/functions/access/grants/batch \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}" \
-H "Content-Type: application/json" \
-d '{"operations":[{"principal_type":"automation","principal_id":"{principal_id}","resources":["org/{company_id}/function-folder/{folder_id}/function/{function_id}"],"permission_ids":["{permission_id}"]}]}'Response
200 OK{
"results": [{ "index": 0, "client_ref": null, "status": "failed", "principal_type": "automation", "principal_id": "{principal_id}", "permission_id": "{permission_id}", "resource": "{function_resource}", "effect": "allow", "grant": null, "error_status": 403, "error_detail": "Permission denied", "side_effect_error_status": null, "side_effect_error_detail": null }],
"summary": { "created": 0, "already_exists": 0, "failed": 1 }
}Access Route Matrix
The remaining per-zone access operations for APIs, function folders, and functions. Every operation is an OpenAPI-derived agent tool and retains the concrete zone manage permission.
/api/v1/compute/apis/{api_id}/access/eligibleList Eligible Principals — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/eligible \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/apis/{api_id}/access/resource-typesList Resource Types — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/resource-types \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/apis/{api_id}/access/permissionsList Permissions — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/permissions \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/apis/{api_id}/access/grantsList Grants — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/apis/{api_id}/access/grants/{grant_id}Delete Grant — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/grants/{grant_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/apis/{api_id}/access/connection-requests/{request_id}/rejectReject Connection Request — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/connection-requests/{request_id}/reject \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/apis/{api_id}/access/connections/{connection_id}Revoke Connection — api
Manage the api federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:apis:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/apis/{api_id}/access/connections/{connection_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/function-folders/{folder_id}/access/eligibleList Eligible Principals — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/eligible \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/resource-typesList Resource Types — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/resource-types \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/permissionsList Permissions — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/permissions \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/grantsList Grants — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/grantsCreate Grant — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
201 Created{}/api/v1/compute/function-folders/{folder_id}/access/grants/{grant_id}Delete Grant — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/grants/{grant_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/function-folders/{folder_id}/access/connection-requestsList Connection Requests — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/connection-requests \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/connection-requests/{request_id}/approveApprove Connection Request — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/connection-requests/{request_id}/approve \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/connection-requests/{request_id}/rejectReject Connection Request — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/connection-requests/{request_id}/reject \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/connectionsList Connections — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/connections \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/function-folders/{folder_id}/access/connections/{connection_id}Revoke Connection — function-folder
Manage the function-folder federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:function-folders:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/function-folders/{folder_id}/access/connections/{connection_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/functions/{function_id}/access/eligibleList Eligible Principals — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/eligible \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/resource-typesList Resource Types — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/resource-types \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/permissionsList Permissions — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/permissions \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/grantsList Grants — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/grantsCreate Grant — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/grants \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
201 Created{}/api/v1/compute/functions/{function_id}/access/grants/{grant_id}Delete Grant — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/grants/{grant_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
204 No Content/api/v1/compute/functions/{function_id}/access/connection-requestsList Connection Requests — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/connection-requests \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/connection-requests/{request_id}/approveApprove Connection Request — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/connection-requests/{request_id}/approve \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/connection-requests/{request_id}/rejectReject Connection Request — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X POST https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/connection-requests/{request_id}/reject \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/connectionsList Connections — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X GET https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/connections \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"Response
200 OK{}/api/v1/compute/functions/{function_id}/access/connections/{connection_id}Revoke Connection — function
Manage the function federated zone through Compute's IAM-backed access surface.
Bearer <token> + X-Company-Id header required. Permission: compute:permissions:functions:manage on the concrete zone.
curl -X DELETE https://platform.ergondata.ai/api/v1/compute/functions/{function_id}/access/connections/{connection_id} \
-H "Authorization: Bearer {token}" \
-H "X-Company-Id: {company_id}"