Skip to content
Reference

API overview

The synsmarts API is the supported automation interface for customer operations. Use this overview for the API contract and authentication model, then open the interactive reference for request fields, response schemas, and language-specific examples.

The portal and public API expose customer capabilities through different adapters:

  • The portal uses a browser session and CSRF protection.
  • The public API uses an App-bound API key or a supported delegated bearer token.
  • The CLI is a peer client of the public API for operations that have a CLI mapping.

Parity means a customer capability can be available through the portal, API, and CLI through the same Team/App resource address, with each client using its own authentication method. It doesn’t mean every published API operation is already presented in every client. The generated availability shown for each operation below is authoritative for the portal and CLI. The generated OpenAPI document is authoritative for direct API access. If an operation isn’t listed below, it isn’t currently published for customer API use.

https://api.synsmarts.io

All paths are relative to this URL. The current contract uses versioned /api/v1/ paths. Validate requests and responses against the published schema; breaking contract changes use a new API version.

Send an App-bound API key in the X-API-Key header. A bearer token issued by synsmarts can also authenticate supported integrations. Every customer operation addresses its Team at /api/v1/t/{team}/...; App operations continue through /a/{app}/.... The path selects the resource. The session, API key, or delegated grant authorizes access to that addressed resource.

Don’t put credentials in a URL, query string, source repository, or support attachment.

Terminal window
curl --request GET \
--url "https://api.synsmarts.io/api/v1/t/$TEAM/a/$APP/diagnostics" \
--header "Accept: application/json" \
--header "X-API-Key: $SYNSMARTS_API_KEY"

Store the key in a secret manager or protected environment variable. Create a separate key for each integration so it can be rotated or revoked independently.

Errors use application/problem+json with stable fields including status, detail, and error_code. Respect Retry-After when it is present on a 429 or 503 response. Otherwise, use the HTTP status and operation behavior to decide whether a retry is safe.

Most published operations are App-scoped. Scope: app means the operation is addressed by its /a/{app}/ path segment, and the credential authorizes access to that App. An App-bound key authorizes only its own App. Scope: team means the operation is addressed by its /t/{team}/ path segment, and the credential authorizes access to that Team. Request-tracing operations are the exception, and their team_slug and tenant_id are validated against the caller. synchronous operations complete in the response. A durable operation accepts work for continued processing and returns the identifier named in its completion metadata; save that identifier for the related status or result operation.

Deploy application releases, inspect deployment status and history, and roll back releases.

POST /api/v1/t/{team}/a/{app}/deploys/create

Operation ID: deployment.deploy

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: deployments.write · Completion: durable; save deploy_id from the response

Portal: Shown as Deploy
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/deploys/{deploy_id}

Operation ID: deployment.getStatus

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: operations.read · Completion: synchronous

Portal: Shown as Deployment status
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/deploys/{deploy_id}/rollback

Operation ID: deployment.rollback

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: deployments.write · Completion: durable; save deploy_id from the response

Portal: Shown as Roll back deployment
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/deploys

Operation ID: diagnostics.getDeployHistory

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: deployments.read · Completion: synchronous

Portal: Shown as Deployment history
CLI: Not currently presented

View request fields, response schemas, and code samples →

Run investigations and inspect reports, telemetry, traces, configuration, queries, and code.

POST /api/v1/t/{team}/a/{app}/diagnostics/explain

Operation ID: diagnostics.explainQuery

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Analysis-only; leaves App configuration unchanged.

Scope: app · Permission: database_queries.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/config/{service}

Operation ID: diagnostics.getConfig

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/{investigation_id}/report

Operation ID: diagnostics.getReport

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: findings.read · Completion: synchronous

Portal: Shown as Diagnostic report
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/traces/{trace_id}

Operation ID: diagnostics.getTraceDetail

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: traces.read · Completion: synchronous

Portal: Shown as Trace detail
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics

Operation ID: diagnostics.listInvestigations

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: findings.read · Completion: synchronous

Portal: Shown as Diagnostic investigations
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/logs

Operation ID: diagnostics.queryLogs

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: logs.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/metrics

Operation ID: diagnostics.queryMetrics

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: metrics.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/traces

Operation ID: diagnostics.queryTraces

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: traces.read · Completion: synchronous

Portal: Shown as Trace summaries
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}/apply

Operation ID: diagnostics.recommendations.apply

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: recommendations.write · Completion: durable; save operation_id from the response

Portal: Shown as Apply recommendation
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}/dismiss

Operation ID: diagnostics.recommendations.dismiss

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: recommendations.write · Completion: synchronous

Portal: Shown as Dismiss recommendation
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}

Operation ID: diagnostics.recommendations.get

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: findings.read · Completion: synchronous

Portal: Shown as Recommendation detail
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/recommendations

Operation ID: diagnostics.recommendations.list

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: findings.read · Completion: synchronous

Portal: Shown as Recommendations
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}/mark-applied

Operation ID: diagnostics.recommendations.markApplied

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: recommendations.write · Completion: synchronous

Portal: Shown as Mark recommendation applied
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}/mark-not-applied

Operation ID: diagnostics.recommendations.markNotApplied

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: recommendations.write · Completion: synchronous

Portal: Shown as Mark recommendation not applied
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/recommendations/{rec_id}/reopen

Operation ID: diagnostics.recommendations.reopen

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: recommendations.write · Completion: synchronous

Portal: Shown as Reopen recommendation
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/diagnostics/code/search

Operation ID: diagnostics.searchCode

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: code.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/diagnostics/trigger

Operation ID: diagnostics.triggerInvestigation

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Analysis-only; leaves App configuration unchanged.

Scope: app · Permission: diagnostics.run · Completion: durable; save investigation_id from the response

Portal: Shown as Run diagnostics
CLI: Not currently presented

View request fields, response schemas, and code samples →

Inspect and operate App services and reconcile customer configuration.

POST /api/v1/t/{team}/a/{app}/services/cache/clear

Operation ID: control.clearCache

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Clear cache
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/site-configuration

Operation ID: control.configureServices

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: config.write · Completion: durable; save deployment_id from the response

Portal: Shown as Configure services
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/cron/disable

Operation ID: control.disableCron

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Disable cron
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/opcache/flush

Operation ID: control.flushOpcache

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Flush OPcache
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/services/status/{action_id}

Operation ID: control.getActionStatus

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: operations.read · Completion: synchronous

Portal: Shown as Action status
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/site-configuration

Operation ID: control.getSiteConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Shown as Site configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/mysql/kill-query

Operation ID: control.killQuery

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: database_queries.terminate · Completion: durable; save action_id from the response

Portal: Shown as Kill database query
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/config/preview

Operation ID: control.previewConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Analysis-only; leaves App configuration unchanged.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Shown as Preview configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/config/reconcile

Operation ID: control.reconcileConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: config.write · Completion: durable; save deployment_id from the response

Portal: Not currently presented
CLI: Presented as deploy config-reconcile

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/php/restart

Operation ID: control.restartPhp

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Restart PHP
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/redis/restart

Operation ID: control.restartRedis

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Restart Redis
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/config/rollback

Operation ID: control.rollbackConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: config.write · Completion: durable; save operation_id from the response

Portal: Shown as Roll back configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/scale

Operation ID: control.scale

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: scale.write · Completion: durable; save action_id from the response

Portal: Shown as Scale resources
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/services/maintenance/toggle

Operation ID: control.toggleMaintenanceMode

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires confirmed: true and an Idempotency-Key.

Scope: app · Permission: services.operate · Completion: durable; save action_id from the response

Portal: Shown as Toggle maintenance mode
CLI: Not currently presented

View request fields, response schemas, and code samples →

POST /api/v1/t/{team}/a/{app}/config/validate

Operation ID: control.validateConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Analysis-only; leaves App configuration unchanged.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Shown as Validate configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/services/mysql/connections

Operation ID: control.viewConnections

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: database_queries.read · Completion: synchronous

Portal: Shown as Database connections
CLI: Not currently presented

View request fields, response schemas, and code samples →

Read team-scoped usage and invoices.

GET /api/v1/t/{team}/billing/invoices/{invoice_id}

Operation ID: billing.getInvoice

Scoped to the addressed Team; the {team} path segment selects the resource and the credential authorizes access. Read-only.

Scope: team · Permission: billing.read · Completion: synchronous

Portal: Shown as Invoice detail
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/billing/usage

Operation ID: billing.getUsage

Scoped to the addressed Team; the {team} path segment selects the resource and the credential authorizes access. Read-only.

Scope: team · Permission: billing.read · Completion: synchronous

Portal: Shown as Billing usage
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/billing/invoices

Operation ID: billing.listInvoices

Scoped to the addressed Team; the {team} path segment selects the resource and the credential authorizes access. Read-only.

Scope: team · Permission: billing.read · Completion: synchronous

Portal: Shown as Invoices
CLI: Not currently presented

View request fields, response schemas, and code samples →

Inspect environments and purchased resource allocations.

GET /api/v1/t/{team}/a/{app}/resources

Operation ID: environment.getResources

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Shown as Resources
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/environments

Operation ID: environment.list

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: operations.read · Completion: synchronous

Portal: Shown as Environments
CLI: Not currently presented

View request fields, response schemas, and code samples →

Read live runtime status and service information for an App.

GET /api/v1/t/{team}/a/{app}/live/mysql/variables

Operation ID: live.getMysqlVariables

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: status.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/live/nginx/status

Operation ID: live.getNginxStatus

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: status.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/live/php-fpm/status

Operation ID: live.getPhpFpmStatus

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: status.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/live/php/info

Operation ID: live.getPhpInfo

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: status.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

GET /api/v1/t/{team}/a/{app}/live/redis/info

Operation ID: live.getRedisInfo

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: status.read · Completion: synchronous

Portal: Not currently presented
CLI: Not currently presented

View request fields, response schemas, and code samples →

Read customer-visible audit events for an App.

GET /api/v1/t/{team}/a/{app}/audit-events

Operation ID: audit.getEvents

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: audit.read · Completion: synchronous

Portal: Shown as Audit events
CLI: Not currently presented

View request fields, response schemas, and code samples →

List available backups for an App.

GET /api/v1/t/{team}/a/{app}/backups

Operation ID: backups.list

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: backups.read · Completion: synchronous

Portal: Shown as Backups
CLI: Not currently presented

View request fields, response schemas, and code samples →

Inspect App domain, DNS, and TLS status.

GET /api/v1/t/{team}/a/{app}/dns

Operation ID: dnsTls.getDomains

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: dns_tls.read · Completion: synchronous

Portal: Shown as DNS and TLS status
CLI: Not currently presented

View request fields, response schemas, and code samples →

Read and update resource-addressed request tracing.

GET /api/v1/t/{team}/a/{app}/tracing

Operation ID: tracing.getConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Read-only.

Scope: app · Permission: config.read · Completion: synchronous

Portal: Shown as Request tracing configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

PUT /api/v1/t/{team}/a/{app}/tracing

Operation ID: tracing.updateConfiguration

Scoped to the addressed App; the {team} and {app} path segments select the resource and the credential authorizes access. MCP tools supply their app_id through the canonical App path segment. Mutating operation; requires an Idempotency-Key.

Scope: app · Permission: config.write · Completion: synchronous

Portal: Shown as Update request tracing configuration
CLI: Not currently presented

View request fields, response schemas, and code samples →

The operation list and interactive reference are generated from the same canonical capability catalog. Publishing a customer operation updates both without maintaining a separate handwritten endpoint inventory.


Contract catalog version: 1
Contract digest: 81b57d3552f0187804872c835e18da8c4cbd8d300b519b4347d58bca09fbb0ea