¿Cuánto vale developers.letscloud.io?

LetsCloud API

## Introduction With our API, you can easily perform actions or retrieve information from your instances and containers through HTTP requests to the endpoints described in this documentation. ## Get Started First, you need to generate the token for authentication in the API. You can do this in the **profile** tab of your account, we'll show you how:  ## Requests The API accepts that any tool make queries, for that it is necessary that the requests are made in HTTPS so that they are encrypted. It responds to different methods, let's see them: | **Method** | **Usage** | |------------|----------| | *GET* | For simple retrieval of information about your account and instances, you should use the GET method.The information you request will be returned to you as a JSON object. Any request using the GET method is read-only and will not affect any of the objects you are querying. | | *POST* | To create a new object, your request should specify the POST method. The POST request includes all of the attributes necessary to create a new object. | | *PUT* | To update the information about a resource in your account, the PUT method is available. It sets the state of the target using the provided values, regardless of their current values. | | *DELETE* | To destroy a resource and remove it from your account and environment, the DELETE method should be used. This will remove the specified object if it is found. If it is not found, the operation will return a response indicating that the object was not found. | ## HTTP Statuses REST APIs use the Status-Line part of an HTTP response message to inform clients of their request’s overarching result. RFC 2616 defines the Status-Line syntax. LetsCould API will return a maximum of 5 responses divided into two groups: - Successful Requisitions: - All successful requests return **HTTP Status 200**. - Unsuccessful Requisitions: - Unsuccessful requests can return **HTTP Status 400**, **401**, **500** or **503**. The table below shows in detail the definitions of each request: |Status HTTP| Description | | :---: | :---: | | *200 OK* | Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action. | | 400 Bad Request | The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). | | *401 Unauthorized* | specifically for use when authentication is required and has failed or has not yet been provided. | | *500 Internal Server Error* | A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. | | *503 Service Unavailable* | The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. | ## Responses The return of requests is in **JSON**, always with two properties, `success`, `message`. **Success example:** ```json { "success": true, "data": { } } ``` or ```json { "success": true, "message": 'string' } ``` **Error example:** ```json { "success": false, "message": 'string' } ``` ## Rate Limit Rate limits determine how frequently you can call a particular endpoint. The number of requests that can be made through the API is currently limited to 5,000 per hour in total of 120,000 per day per API token. This rate can vary per resource but the current value is returned in the HTTP headers of your request. For the most recent rate limiting of your requests please view the information in the headers of your response. ## Endpoints The stable HTTP endpoint for the latest version is: **{{url-core-api}}** ## Version **Default version: v1** To select the version of the endpoint just send the example below in the header. If you don't send a version, the default version is used. `application/vnd.letscloud.v1+json`