How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Turnkey

Turnkey Signing API

Transaction and raw payload signing activities.

Documentation Provider Profile APIs.io OpenAPI GitHub

Turnkey Signing API is one of 5 APIs that Turnkey publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.turnkey.com.

5 operations 5 paths 6 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.turnkey.com/public/v1
Authentication
API Key, API Key
Contact
Turnkey Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

Turnkey Signing API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Stamp (apiStamp). An API key is passed in the header as X-Stamp-Webauthn (webauthnStamp). By default, every request must be authenticated.

  • apiStamp — Base64URL-encoded JSON stamp {publicKey, signature, scheme} where signature is a DER-encoded, hex-encoded signature over the exact JSON POST body produced by t…
  • webauthnStamp — Plain-JSON WebAuthn assertion stamp for passkey-authenticated requests.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 POST. Each is listed below with its method, path, parameters, and response codes.

Signing 5

Transaction and raw payload signing activities.

POST
/public/v1/submit/sign_transaction
Sign a transaction
signTransaction body → 200
POST
/public/v1/submit/sign_raw_payload
Sign a raw payload
signRawPayload body → 200
POST
/public/v1/submit/sign_raw_payloads
Sign multiple raw payloads
signRawPayloads body → 200
POST
/public/v1/query/get_activity
Get an activity
getActivity body → 200
POST
/public/v1/query/list_activities
List activities
listActivities body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SubmitActivityEnvelope (4 properties), GetActivityRequest (2 properties), OrganizationScopedQuery (1 property), ActivityResponse (1 property). Each schema is shown below with its type and property counts.

SubmitActivityEnvelope
object
Common envelope for all submit (mutation) activities. The type selects the activity and parameters carries the activity-specific body.
4 properties 4 required
ActivityResponse
object
Standard activity envelope returned by submit and query endpoints.
1 property
SignRawPayloadRequest
OrganizationScopedQuery
object
1 property 1 required
GetActivityRequest
object
2 properties 2 required
SignTransactionRequest

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

turnkey-signing-api-openapi.yml Raw ↑

Other APIs Turnkey publishes across the network.

Turnkey Organizations API
AE Profile APIs.io
Turnkey Private Keys API
AE Profile APIs.io
Turnkey Users & Policies API
AE Profile APIs.io
Turnkey Wallets API
AE Profile APIs.io
#Signing
← Back to T APIs
API Details
ID
turnkey:turnkey-signing-api
Base URL
https://api.turnkey.com/public/v1
Docs
https://docs.turnkey.com/concepts/organizations
Provider
Turnkey
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=turnkey-signing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/turnkey-signing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Turnkey Signing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.