List domain keys, and optionally filter by signing domain or selector. The page & limit data is only required when paging through the data.
A 200 response
required | Array of objects |
object |
A 401 response
{- "items": [
- {
- "signing_domain": "authority.domain.tld",
- "selector": "s1",
- "dns_record": {
- "is_active": true,
- "cached": [
- "cached dns value"
], - "name": "s1._domainkey.authority.domain.tld",
- "record_type": "TXT",
- "valid": "VALID",
- "value": "expected dns value"
}
}, - {
- "signing_domain": "authority.domain.tld",
- "selector": "s2",
- "dns_record": {
- "cached": [
- "cached dns value"
], - "name": "s2._domainkey.authority.domain.tld",
- "record_type": "TXT",
- "valid": "UNKNOWN",
- "value": "expected dns value"
}
}
], - "paging": {
}
}
Create a domain key. Note that once private keys are created or imported they are never exported. Alternatively, you can import an existing PEM file containing a RSA private key in PKCS #1, ASn.1 DER format. Note, the pem can be passed as a file attachment or as a form-string parameter.
{- "signing_domain": "example.com",
- "selector": "s1",
- "dns_record": {
- "cached": [ ],
- "name": "s1._domainkey.example.com",
- "record_type": "TXT",
- "valid": "unknown",
- "value": "k=rsa; p=<public_key>"
}
}
Selector is the unique identifier of your key. It has to be different from other keys selector.
{- "message": "Domain DKIM authority changed"
}