Jump to Content
Mutual TLS Edge Truststore (Limited availability)
GuideAPIRelease notesTerraformControl Center
Mutual TLS Edge Truststore (Limited availability)
API
GuideAPIRelease notesTerraformControl Center

API

  • mTLS Edge Truststore API v2
  • API summary
  • Get started
  • API concepts
  • Rate and resource limiting
  • API Hypermedia
  • Object versioning
  • Enumeration values
  • API workflow
  • Errors
    • 400
    • 401
    • 403
    • 404
    • 405
    • 406
    • 409
    • 415
    • 422
    • 429
    • 500
    • 503

CA sets

  • CA set
    • Create a CA setpost
    • List CA setsget
    • Get a CA setget
    • Delete a CA setdel
    • List CA set activationsget
    • List CA set activitiesget
    • Get CA set associationsget
    • Clone a CA setpost
    • Get CA set delete statusget

CA set versioning

  • CA set version
    • Create a versionpost
    • List versionsget
    • Get a versionget
    • Update a versionput
    • Activate a versionpost
    • Get version activationsget
    • Get an activationget
    • List certificatesget
    • Clone a versionpost
    • Deactivate a versionpost

Certificates

  • Certificate validation
    • Validate certificatespost

Object versioning

When you exchange data with v2 APIs, you don’t need to specify Accept and Content-Type headers explicitly. By default, the API uses application/json for both requests and responses. .

If you do include these headers, they must be set to application/json. Using any other value results in:

  • 406 if the Accept header is invalid.
  • 415) if the Content-Type header is invalid.
Akamai TechDocs
Akamai.com
Linode.com
Contact us
Akamai support Linode support Share feedback
Try Akamai
Log in
Log out
Try Akamai

Akamai.com

Linode.com

Contact us Akamai support Linode support Share feedback

Log in
Log out