API HTTP Response Codes


Verizon Personal Cloud Storage APIs support only JASON responses.

NOTE: The exception is GET /oauth2/authorize API, where the success response is HTTP status 302, which redirects the user to the Verizon Cloud login page and HTTP status 200 is a failure response for this API.

Success Responses

200 The API request was successful.
201 The API request was successful and a new resource has been created.
202 Accepted: the request has been accepted for processing, but the processing is not complete yet.

Failure Responses

All error messages are returned in this format:

{ "error": "string", "error_description": "string" }
204 No Content
205 This error can occur when GET /fullview API is called after the user has made too many changes to the content in the Cloud account. The user must do a full resync.
304 Not modified: the resource has not been modified since the last request.
400 Bad input parameter sent to Orchestration Layer.
401 Invalid access token: either the user’s access has been revoked or the token has expired.
403 Forbidden by the server: user is accessing a forbidden resource on the server.
404 The requested resource (file or folder) is not found.
405 Request method not expected.
406 Not acceptable: an unsupported media type has been specified in the accept header.
409 Conflict: the API request is attempting a resource that already exists or write access has been denied.
410 The resource at the specified path does not exist or has been deleted.
411 Length required: an entity was included in the request but a content-length header was not.
412 Precondition failed.
413 User quota exceeded.
415 Unsupported media type.
429 App is making too many API requests and is being rate limited.
500 Server error: the client should retry the request.
503 The server is busy. If the retry-after header is set to a value, retry request after value seconds.
504 Gateway timeout.

Copyright © 2015-2016, Verizon and/or its Licensors. All rights reserved.