Jump to Content
NetStorage Usage API
RecipesAPIRelease notesControl Center
NetStorage Usage API
API
RecipesAPIRelease notesControl Center

API

  • NetStorage Usage API
    • NetStorage Configuration API
  • Key concepts and terms
  • Get started
  • OpenAPI schema
  • Parse XML responses
  • Format an API call
    • Example authentication headers
    • Each call needs signature header authentication
  • Errors
    • 400
    • 403
    • 404
    • 412
    • 429
    • 500

Usage

  • delete actionput
    • Usage details for "delete"
  • dir actionget
    • Usage details for "dir"
  • download actionget
    • Usage details for "download"
  • du actionget
  • list actionget
  • mkdir actionput
    • Usage details for "mkdir"
  • mtime actionpost
  • quick-delete actionpost
    • Usage details for "quick-delete"
  • rename actionput
    • Usage details for "rename"
  • rmdir actionput
    • Usage details for "rmdir"
  • stat actionget
    • Usage details for "stat"
  • symlink actionpost
    • Usage details for "symlink"
  • upload actionput
    • Usage details for "upload"

400

A 400 response usually indicates a validation failure or missing required parameters, but can trigger for many reasons. This sample 400 error represents an attempt to apply invalid parameters:

A malformed request such as an illegal combination of parameters in the X-Akamai-ACS-Action request header may cause a 400 response. There may be more information in the response body, represented as unstructured text.

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