It's finally up and running. The "completed" version 1.0 of 99Stack API is the stable foundation that over time will be extended with new features, all following the same logic structure. Get started by reading the updated and extended documentation, available here: https://api.99stack.com/docs/ Highlights All requests and responses now using the JSON format All timestamps in ISO-8601 UTC+00:00 format Unified variable names, (ex: server_id is always used for server objects) Validation of HTTP method and proper HTTP response codes Change log 2019 Changed view template to ReDoc Reduced response times by optimizing functions Increased security by validating input as early as possible Increased security by carefully reconsidering what info should be in responses to avoid data harvest Included a downloadable OpenAPIv3 JSON template that can be used for testing in your favorite REST API client Renamed functions and variables with non unified names (see docs for more details) Issues and questions Feel free to ask your questions in reply to this topic, and discuss eventual issues and we'll do our best to help you out within reasonable time.

I'm getting this error when trying to deploy a second generation server: { "message": "Deployment failed, unable to proxy request to region. Please try a different region or wait. Reference: #xxx...", "response_type": "error", "response_code": 502 } if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Any ideas why?

Sebastian_Mannerheim Orson_Deforest and to everyone else this may concern. The issue has now been resolved. There are two different types of error messages available when sending a request to /v1/server/create . One for 5xx errors and one for 4xx errors. These are based on what kind of response the API receives from the region control system which is referred to as " external API ". The problem was that these errors where mixed up so that 4xx showed a 5xx error. Example of 4xx error: { "message": "Deployment failed, region does not accept configuration. Please try a different plan and image. Reference: #00000000", "response_type": "error", "response_code": 422 } if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Example of 5xx error: { "message": "Deployment failed, unable to proxy request to region. Please try a different region or wait. Reference: #00000000", "response_type": "error", "response_code": 502 } if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } More specifically: a 422 error means that one of either: plan ID, image ID or region ID was incorrect or unavailable at the moment. Therefore, always check the current availability to see which ID's can be used before sending a request to /create or nay resource. https://api.99stack.com/docs/#tag/Public

Automate your work with 99Stack API

The_Moose

It's finally up and running. The "completed" version 1.0 of 99Stack API is the stable foundation that over time will be extended with new features, all following the same logic structure. Get started by reading the updated and extended documentation, available here: https://api.99stack.com/docs/

Highlights

All requests and responses now using the JSON format
All timestamps in ISO-8601 UTC+00:00 format
Unified variable names, (ex: server_id is always used for server objects)
Validation of HTTP method and proper HTTP response codes

Change log 2019

Changed view template to ReDoc
Reduced response times by optimizing functions
Increased security by validating input as early as possible
Increased security by carefully reconsidering what info should be in responses to avoid data harvest
Included a downloadable OpenAPIv3 JSON template that can be used for testing in your favorite REST API client
Renamed functions and variables with non unified names (see docs for more details)

Issues and questions

Feel free to ask your questions in reply to this topic, and discuss eventual issues and we'll do our best to help you out within reasonable time.

Kauko_Laaksonen

Outstanding move to keep the old functions and simply include a deprecated flag. It took just a few minutes to read and understand how to update. After the change I had to change some variables but then everything worked excellent.

Deprecated-Function	true

Sebastian_Mannerheim

I'm getting this error when trying to deploy a second generation server:

{
    "message": "Deployment failed, unable to proxy request to region. Please try a different region or wait. Reference: #xxx...",
    "response_type": "error",
    "response_code": 502
}

Any ideas why?

Orson_Deforest

Sebastian_Mannerheim Me too, I've tried to wait but it seems to happen always. However, for some reason when I double checked the plan and image ID's in my request it worked.

The_Moose

Sebastian_Mannerheim Orson_Deforest and to everyone else this may concern.

The issue has now been resolved.

There are two different types of error messages available when sending a request to /v1/server/create. One for 5xx errors and one for 4xx errors. These are based on what kind of response the API receives from the region control system which is referred to as "external API". The problem was that these errors where mixed up so that 4xx showed a 5xx error.

Example of 4xx error:

{
    "message": "Deployment failed, region does not accept configuration. Please try a different plan and image. Reference: #00000000",
    "response_type": "error",
    "response_code": 422
}

Example of 5xx error:

{
    "message": "Deployment failed, unable to proxy request to region. Please try a different region or wait. Reference: #00000000",
    "response_type": "error",
    "response_code": 502
}

More specifically: a 422 error means that one of either: plan ID, image ID or region ID was incorrect or unavailable at the moment. Therefore, always check the current availability to see which ID's can be used before sending a request to /create or nay resource. https://api.99stack.com/docs/#tag/Public

Kauko_Laaksonen

The_Moose Maybe the 4xx error should include some information on which of those three ID's are incorrect? It works great when a variable is missing or misspelled, but on incorrect input it's always that same error message with HTTP code 422.

The_Moose

Kauko_Laaksonen It would be great and we have been looking for ways to implement this. Although, the problem is that we where not exactly sure how to obtain that information accurately. This is because a 422 error is what we get from the remote location once a deployment error occurs. One approach could of course be to check with /v1/region/list, /v1/image/list and /v1/plan/list, something we've implemented in our new control panel.

But for the API it seems more efficient to throw a 422 error and let you double check which variable that was incorrect.