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
OpenZeppelin

OpenZeppelin Signers API

Signers are responsible for signing the transactions related to the relayers.

Documentation Provider Profile APIs.io OpenAPI GitHub

OpenZeppelin Signers API is one of 9 APIs that OpenZeppelin publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a GitHub repository, a changelog, and rate-limit docs.

This API exposes 5 operations across 2 paths, and defines 24 schemas. It is described by OpenAPI 3.1.0, at version 1.5.0.

Requests are made against the base URL https://defender-api.openzeppelin.com/v2.

5 operations 2 paths 24 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.5.0
Base URL
https://defender-api.openzeppelin.com/v2
Authentication
HTTP Bearer
Contact
OpenZeppelin
License
AGPL-3.0 license
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

OpenZeppelin Signers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer_auth).

Paths & Operations 5

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

Signers 5

Signers are responsible for signing the transactions related to the relayers.

GET
/api/v1/signers
Signer routes implementation
listSigners 2 params → 200400401500
POST
/api/v1/signers
Creates a new signer.
createSigner body → 201400401409500
GET
/api/v1/signers/{signer_id}
Retrieves details of a specific signer by ID.
getSigner 1 param → 200400401404500
DELETE
/api/v1/signers/{signer_id}
Deletes a signer by ID.
deleteSigner 1 param → 200400401404500
PATCH
/api/v1/signers/{signer_id}
Updates an existing signer.
updateSigner 1 param body → 200400401404500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are GoogleCloudKmsSignerServiceAccountRequestConfig (10 properties), VaultTransitSignerRequestConfig (7 properties), GoogleCloudKmsSignerServiceAccountResponseConfig (7 properties), VaultSignerRequestConfig (6 properties). Each schema is shown below with its type and property counts.

GoogleCloudKmsSignerServiceAccountResponseConfig
object
7 properties 7 required
ApiResponse_Vec_SignerResponse
object
5 properties 1 required
GoogleCloudKmsSignerServiceAccountRequestConfig
object
Google Cloud KMS service account configuration for API requests
10 properties 10 required
LocalSignerRequestConfig
object
Local signer configuration for API requests
1 property 1 required
VaultTransitSignerRequestConfig
object
Vault Transit signer configuration for API requests
7 properties 5 required
GoogleCloudKmsSignerRequestConfig
object
Google Cloud KMS signer configuration for API requests
2 properties 2 required
SignerType
string
Signer type enum used for validation and API responses
LogEntry
object
2 properties 2 required
AwsKmsSignerRequestConfig
object
AWS KMS signer configuration for API requests
2 properties 2 required
VaultSignerRequestConfig
object
Vault signer configuration for API requests
6 properties 4 required
SignerConfigResponse
Signer configuration response Does not include sensitive information like private keys
GoogleCloudKmsSignerKeyRequestConfig
object
Google Cloud KMS key configuration for API requests
4 properties 4 required
SignerCreateRequest
object
Request model for creating a new signer
3 properties 2 required
GoogleCloudKmsSignerKeyResponseConfig
object
4 properties 4 required
ApiResponse_String
object
5 properties 1 required
SignerConfigRequest
Signer configuration enum for API requests (without type discriminator)
SignerUpdateRequest
object
Request model for updating an existing signer At the moment, we don't allow updating signers
ApiResponse_SignerResponse
object
5 properties 1 required
TurnkeySignerRequestConfig
object
Turnkey signer configuration for API requests
5 properties 5 required
PluginMetadata
object
2 properties
SignerTypeRequest
string
Signer type enum for API requests
LogLevel
string
CdpSignerRequestConfig
object
CDP signer configuration for API requests
4 properties 4 required
PaginationMeta
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openzeppelin-signers-api-openapi.yml Raw ↑

Other APIs OpenZeppelin publishes across the network.

OpenZeppelin Monitor API
AE Profile APIs.io
OpenZeppelin Contracts API Reference
AE Profile APIs.io
OpenZeppelin Health API
AE Profile APIs.io
OpenZeppelin Metrics API
AE Profile APIs.io
OpenZeppelin Networks API
AE Profile APIs.io
OpenZeppelin Notifications API
AE Profile APIs.io
OpenZeppelin Plugins API
AE Profile APIs.io
OpenZeppelin Relayers API
AE Profile APIs.io
#Signers
← Back to O APIs
API Details
ID
openzeppelin:openzeppelin-signers-api
Base URL
https://defender-api.openzeppelin.com/v2
Docs
https://docs.openzeppelin.com/defender/sdk
Provider
OpenZeppelin
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=openzeppelin-signers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/openzeppelin-signers-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 OpenZeppelin Signers 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.