Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.turnkey.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What are activities?

Activities (also called submissions) are requests to create, modify, or use resources within Turnkey. Submission endpoints are always prefixed with /public/v1/submit.
  • Policy Enforcement: Activities are subject to consensus or condition enforcement via the policy engine.
  • Optimistic Execution: Activities are executed optimistically synchronous—if possible, the request completes synchronously; otherwise, it falls back to asynchronous processing.
  • Activity Status:
    • COMPLETED: The activity was successful and the result field is populated.
    • FAILED: The activity failed and the failure field contains the reason.
    • CONSENSUS_NEEDED: More signatures are required to process the request.
    • PENDING: The request is processing asynchronously.
  • Approval expiration: Activities do not expire. However, approvals expire 24 hours after the first vote if consensus is not reached, and must be re-submitted while the activity remains in ACTIVITY_STATUS_CONSENSUS_NEEDED.
  • Status Updates: You can get updates by re-submitting the request (idempotent) or polling get_activity with the activity ID.
  • Idempotency: The API is idempotent—identical requests (same POST body) return the same activity. To generate a new activity, change the timestampMs value in your request.