SoftLayer Development Network

Home of all the documentation you need for leveraging the SoftLayer API.

Our API provides direct control over every aspect of every SoftLayer service, as well as your SoftLayer customer account. And when we say every, we mean every .

So learn more now about using the API to manage your SoftLayer environment, integrate the SoftLayer API with other APIs, and more. And connect with other developers to share tips, ideas, and best practices.

Language Guides

While the SoftLayer API can be used with any programming language that has supports the SOAP, XML-RPC, or REST protocols, we have created these API clients to help you get started.

Object Storage

With the release of SoftLayer Object Storage, we wanted to integrate brand-unique, value-added features on top of the already comprehensive tools that have been set in place to provide a first-in-class product for our customers.

Latest Blog Posts

September 5, 2014
In part seven of this series we explored using fog-softlayer for managing your SoftLayer Global IP addresses. In this installment, we'll look at using tags to bring order to the compute and network assets that we provisioned on SoftLayer. These examples all assume you have ~/.fog which contains the following: :softlayer_username: example-username :softlayer_api_key: 1a1a1a1a1a1a1a1a1a11a1a1a1a1a1a1a1a1a1 ... read more
August 25, 2014
What is Jumpgate? Jumpgate, an OpenStack community project, is a library that acts as a translation layer to convert an incoming OpenStack call to a different cloud provider's API call. Teams from IBM and SoftLayer collaborated to support more of Jumpgate's functionality, increasing coverage of the standard OpenStack API for SoftLayer’s API. Supporting Neutron (network) is one of our focus items in the latest release. New OpenStack Functionality Added to Jumpgate ... read more
August 21, 2014
The SoftLayer platform lets you add dynamic data and scripts when you place your order. The scripts are executed after the machine is booted. To place a script on a virtual server, the script must be available through a URL. Note: For HTTP URLs, the script is injected in the server and manually executed. For HTTPS URLs, the script is injected and automatically executed. In this article, we use https://x.x.x.x/ as the URL where the scripts are available and as the script. If you place the URL on the browser, the result should be: #!/bin/bash ... read more

Latest Forum Discussions

Gentlemen, Has anyone been successful in automating IPV6 PTR? I am unsure whether it is...
Here is my sample code: # Authentication information has been removed vg_service = SoftLayer...
I want to order a hardware via command line sl hardware . . . . . But I read somewhere to use...