Skip to content
Sine Cloud
PowersOpenAPI

Create or replay a persisted run

POST/api/powers/v1/runs

This host waits for execution to settle. A new record returns 201 even when its status reports a provider error or UNKNOWN. Repeating an identical Idempotency-Key returns the saved record with 200. An expectedEndpointRevision mismatch returns 409 before execution; describe again before deciding whether to submit. Authenticate with an organization API key. Native permission names describe runtime capabilities; x-sinecloud-scopes lists the customer key scopes required by Cloud. For a managed request, retain expectedEndpointRevision from endpoint discovery. An explicit binding requires a connection. Save and reuse the original Idempotency-Key and complete request envelope to recover; do not switch between managed and native envelopes. Without a key, a retry can start a new invocation. Read saved runs after uncertain responses; UNKNOWN and reconciliation states do not establish that execution failed.

Organization API key authentication

Authorization: Bearer $SINECLOUD_API_KEY

Required scopes: toolRun

Parameters

idempotency-key · header · Optional
Strongly recommended for execution. Reuse the original key and full request body for recovery. Cloud binds it to the current actor and project scope.
X-Sinecloud-Project-Id · header · Optional
Select a currently accessible project. A project-restricted key cannot select another project. Omit to use the key restriction or organization scope as permitted.

Request body

Required

application/json

Responses

200
Existing run replayed without another execution
201
Run record created; inspect its status
400
Invalid request
401
Bearer authentication required
402
Insufficient credits to reserve this capability call
403
Request is not authorized
404
Resource not found
405
Method not allowed; inspect Allow
409
Catalog cursor, Endpoint revision, idempotency, or run state conflict
412
Connection credentials are not configured
413
JSON request exceeds 64 KiB
415
Use uncompressed UTF-8 application/json
422
Execution admission rejected
429
Request rate or quota exceeded. Respect Retry-After when supplied.
500
Internal error; details are not disclosed
501
Required execution capability is not supported
502
Runtime response unavailable. Reuse the original Idempotency-Key and request envelope to recover the admitted invocation.
503
Runtime unavailable

Loading API reference…

Powers · Setup & authentication

Base URLhttps://sinecloud.dev/api/powers/v1

Open Console · Create an API key · Browse all APIs

Download API index

Before your first request

Select your organization, prepare resources in Console, and issue an organization API key with the required product scopes. Current permissions, resource access, budget and available funds are checked on every call.

Choose an available endpoint, then inspect its current revision and input schema. The catalog covers endpoint discovery, organization connections, tool runs and durable run recovery. Managed runs include endpointId, expectedEndpointRevision and input; native runs also select an organization-owned connection and may select an explicit binding. Preserve the native result and status envelope.

Use the Cloud scopes listed in x-sinecloud-scopes on each operation. Native permission names describe runtime capabilities. Connection changes require connectionWrite and an organization-wide key without a project restriction; add BYOK credentials in Console. Reuse the original Idempotency-Key, revision and complete input when recovering an uncertain run. HTTP success alone does not mean execution succeeded.

Organization key authentication and base URL

The production API origin is https://sinecloud.dev; the documentation origin does not serve product requests. The path prefix is /api/powers/v1. Use the complete path documented for the operation, replacing resource IDs, models and endpoint revisions with your actual selections.

Authorization: Bearer $SINECLOUD_API_KEY

Set SINECLOUD_API_KEY to your own environment variable value; never use platform service credentials. Each operation lists required scopes in x-sinecloud-scopes.

This reference is read-only. Run requests in Console or your own client. Browsing documentation never creates a key, starts execution or incurs an execution charge. Keep request IDs and execution receipts; a lost connection does not cancel work. Follow the operation’s recovery instructions before submitting again.

Sine CloudDocs
Console

Type to search…

↑↓ navigate↵ selectEsc Close