HTTP/2 302
server: nginx
date: Fri, 10 Oct 2025 10:14:36 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20151028130915
location: https://web.archive.org/web/20151028130915/https://nephoscale.com/nephoscale-technologies/rest-api/
server-timing: captures_list;dur=0.927966, exclusion.robots;dur=0.034560, exclusion.robots.policy;dur=0.017598, esindex;dur=0.015590, cdx.remote;dur=28.613586, LoadShardBlock;dur=194.992859, PetaboxLoader3.datanode;dur=76.357689
x-app-server: wwwb-app210
x-ts: 302
x-tr: 284
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie: wb-p-SERVER=wwwb-app210; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Fri, 10 Oct 2025 10:14:37 GMT
content-type: text/html; charset=UTF-8
x-archive-orig-server: Apache/2.2.22 (Ubuntu)
x-archive-orig-x-powered-by: PHP/5.4.43-1+deb.sury.org~precise+1
x-archive-orig-x-pingback: https://nephoscale.com/xmlrpc.php
x-archive-orig-link:
; rel=shortlink
x-archive-orig-cache-control: max-age=172800
x-archive-orig-expires: Fri, 30 Oct 2015 12:20:38 GMT
x-archive-orig-vary: Accept-Encoding
x-archive-orig-date: Wed, 28 Oct 2015 13:07:27 GMT
x-archive-orig-x-varnish: 1194980819 1194980609
x-archive-orig-age: 2808
x-archive-orig-via: 1.1 varnish
x-archive-orig-connection: close
x-archive-orig-x-cache-action: HIT
x-archive-guessed-content-type: text/html
x-archive-guessed-charset: utf-8
memento-datetime: Wed, 28 Oct 2015 13:09:15 GMT
link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Mon, 10 Nov 2014 10:11:03 GMT", ; rel="prev memento"; datetime="Fri, 28 Aug 2015 21:35:04 GMT", ; rel="memento"; datetime="Wed, 28 Oct 2015 13:09:15 GMT", ; rel="next memento"; datetime="Mon, 14 Dec 2015 11:58:18 GMT", ; rel="last memento"; datetime="Wed, 19 Dec 2018 19:29:56 GMT"
content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src: alexa20151029-09/52_49_20151028130910_crawl303.arc.gz
server-timing: captures_list;dur=0.733137, exclusion.robots;dur=0.029221, exclusion.robots.policy;dur=0.013568, esindex;dur=0.012916, cdx.remote;dur=77.052578, LoadShardBlock;dur=391.742785, PetaboxLoader3.datanode;dur=160.843842, PetaboxLoader3.resolve;dur=220.579844, load_resource;dur=227.919500
x-app-server: wwwb-app210
x-ts: 200
x-tr: 819
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=8
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
content-encoding: gzip
NephoScale REST APIs
The NephoScale RESTful APIs are used for programmatically manipulating cloud infrastructure over HTTP, and are the most granular level of control over the platform. NephoScale has two distinct (but interdependent) APIs. NephOS is the API that covers the majority of the NephoScale platform. ObjectStor is the API used to manage cloud storage containers and objects, and it is based on OpenStack Object Storage.
The NephOS API is a REST API that is used for provisioning and managing Cloudlet and BareMetal servers, and other NephoScale cloud resources.
The ObjectStor API is an OpenStack compatible REST API and is used for provisioning and managing the ObjectStor object-based cloud storage system.
Users who want to create their own job management client can use the NephOS API and ObjectStor APIs to call into the NephOS platform, and the APIs can also be used to automate provisioning and manipulation of infrastructure directly from user applications.
NephoScale Admin CLI:
The NephoScale Admin CLI provides an additional convenient way to access the NephOS API.
Requires that an agent be installed on every server
Agent can be added to a server using either CloudScript or the REST API
After a server is created with an agent it can be accessed using the CLI
Run commands in a shell after applying appropriate configuration using the REST API
Use shell commands to easily run recipes
Leverage tokens to allow commands to be run on servers in a stateful manner
Use available VNC Console to connect to a server, and use the CLI as an easy way to retrieve information from various resources on the NephOS platform
Questions? Feedback? powered by Olark live chat software