`order` (Order the items in a directory)

The order transaction orders the items in a directory. Note that directories and tables can not be interspersed with one another.

Query string

The query string in the HTTP header must contain the following parameters:

api

Specify the name of the API transaction.

apiversion

Specify the version of the API that should handle the requested transaction.

For the most up-to-date version, use apiversion=3.

uid

Specify a valid 1010data user name.

pswd

Specify a valid password for the 1010data user name provided to the uid parameter.

Note: The pswd value should be the encrypted password returned from the login transaction.

sid

The session ID for the current API session.

This value is returned by the login transaction and must be provided to every transaction (except login).

kill (optional)

Valid values for kill are as follows:

yes: Terminate the existing session and start a new one.
no: Do not terminate the existing session.
If no session exists, a new one will be created. If a session does exist, an error is returned.

Note: If kill=no and a session is active, the system returns an error.
possess: Log in and possess the existing session.
auth: Authenticate with the system but do not kill, possess, or start any session.

The default is yes.

XML input to server

The specifications must contain the following elements:

<name>: The full name of a directory. Directory names are specified as a full path to the location of the directory, e.g., directory1.directory2.directory[N].thisdirectory.

<dirs>: Contains <name> elements, each containing the full name of a directory. For the order transaction, the order in which the <name> elements are provided represents the order in which the directories will appear in the parent directory.
<tabs>: Contains <name> elements, each containing the full name of a table. For the order transaction, the order in which the <name> elements are provided represents the order in which the tables will appear in the directory.

XML response from server

A successful order contains the following elements:

<rc>: The return code generated by the transaction. For a list of return codes, see Return codes.
<msg>: The message returned by the system. Specific messages correspond to specific return codes.

Query string example

https://www2.1010data.com/gw.k?api=order&apiversion=3&uid=$UID&pswd=$PSWD&sid=$SID

XML input example

<in>
  <name>certification.upload_training.mark</name>
  <dirs>
     <name>certification.upload_training.mark.production</name>
     <name>certification.upload_training.mark.staging</name>
  </dirs>
  <tabs>
     <name>certification.upload_training.mark.rental_test</name>
     <name>certification.upload_training.mark.my_quick_app</name>
     <name>certification.upload_training.mark.csbacounty</name>
  </tabs>
</in>

XML response example

<out>
  <rc>0</rc>
  <msg>Order Successful</msg>
</out>