Version 1.0

deprecated

Basic Information

  • URL

    Base URL

    All API URLs referenced in this documentation start with the following base part:


    https://api.clevermonitor.com/v1.0

  • application/json application/xml

    Content Type

    The default content type is application/json.
    To change the type of content, use the Accept HTTP header.
    You can use types: application/json or application/xml


    curl -H 'Accept: application/json' 'https://api.clevermonitor.com/v1.0'

    or


    curl -H 'Accept: application/xml' 'https://api.clevermonitor.com/v1.0'

  • ISO 8601

    Date and Time format

    Using format: ISO 8601

    Example:


    2016-01-29T00:00:00+01:00

  • gzip

    Content Encoding

    Using Encoding: gzip

    The type of encoding used on the data.


    Content-Encoding: gzip

  • 2XX 3XX 4XX

    HTTP Status Codes

    2XX

    200 OK - Standard response for successful HTTP requests.

    201 Created - The request has been fulfilled and resulted in a new resource being created.

    202 Accepted - The request has been accepted for processing, but the processing has not been completed.

    204 No Content - The server successfully processed the request, but is not returning any content.

    3XX

    304 No Modified - Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match

    4XX

    400 Bad Request - The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

    401 Unauthorized - Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

    403 Forbidden - The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

    404 Not Found - The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

    405 Method Not Allowed - A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

    410 Gone - Indicates that the resource requested is no longer available and will not be available again. 

    415 Unsupported Media Type - The request entity has a media type which the server or resource does not support. 

    422 Unprocessable Entity - The request was well-formed but was unable to be followed due to semantic errors.

    429 Too-Many Requests - The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.


Copyright © CleverMonitor, 2017