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

SparkPost DKIM Keys API

The DKIM Keys API from SparkPost — 3 operation(s) for dkim keys.

SparkPost DKIM Keys API is one of 12 APIs that SparkPost publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include DKIM Keys. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

6 operations 3 paths 2 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sparkpost.com/api/v1
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

SparkPost DKIM Keys API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 6

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

DKIM Keys 6
GET
/sending-domains/{domain}/dkim-keys
List DKIM Keys
listDkimKeys 1 param → 200404
POST
/sending-domains/{domain}/dkim-keys
Create a DKIM Key
createDkimKey 1 param body → 200400404422
GET
/sending-domains/{domain}/dkim-keys/{key_id}
Retrieve a DKIM Key
getDkimKey 2 params → 200404
PUT
/sending-domains/{domain}/dkim-keys/{key_id}
Update a DKIM Key
updateDkimKey 2 params body → 200400404
DELETE
/sending-domains/{domain}/dkim-keys/{key_id}
Delete a DKIM Key
deleteDkimKey 2 params → 204400404
POST
/sending-domains/{domain}/dkim-keys/{key_id}/verify
Verify a DKIM Key
verifyDkimKey 2 params → 200400404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are DkimKeyRequest (7 properties), DkimKeyUpdateRequest (5 properties). Each schema is shown below with its type and property counts.

DkimKeyUpdateRequest
object
5 properties
DkimKeyRequest
object
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sparkpost-dkim-keys-api-openapi.yml Raw ↑

Other APIs SparkPost publishes across the network.

SparkPost Events API
SparkPost Inbound Domains API
SparkPost Metrics API
SparkPost Recipient Lists API
SparkPost Relay Webhooks API
SparkPost Sending Domains API
SparkPost Subaccounts API
SparkPost Suppression List API
SparkPost Templates API
SparkPost Transmissions API
SparkPost Webhooks API
Where this information came from

This is an independent, third-party profile of SparkPost DKIM Keys 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.