API

System APIs

GET system/application-versions/{applicationVersionId}

Application details for provided identifier

HTTP method GET
URI https://api.rambase.net/system/application-versions/{applicationVersionId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {applicationVersionId} Application version identifier
String, regular expression: ^[0-9]+[(\.)]?[0-9]*[(\.)]?[0-9]*$
Successful HTTP status code 200
API resource identifier 226, version 16

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
1

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<ApplicationVersion>
2
     <ApplicationVersionId
ApplicationVersionId

Application version identifier

>{String}</ApplicationVersionId>
3
     <Status
Status

Status of application

>{Integer}</Status>
4
     <Name
Name

Name of application

>{String}</Name>
5
     <ApplicationMatch
ApplicationMatch

Matching Keyword

>{String}</ApplicationMatch>
6
     <ContentType
ContentType

Content Type

>{String}</ContentType>
7
     <MasterUrl
MasterUrl

Url of application

>{String}</MasterUrl>
8
     <Description
Description

Descriptive name of the application

>{String}</Description>
9
     <CustomFieldOrder
CustomFieldOrder

It is possible for a customer to rearrange the fields within a component. If they choose to do so for one or more of the components in this application, the fieldorder will contain a json structure that will keep information about the field order they have selected.

>
10
          <FieldOrder
FieldOrder

A json structure describing the field order

>{String}</FieldOrder>
11
          <FieldOrderChecksum
FieldOrderChecksum

An md5 hash of the fieldorder

>{String}</FieldOrderChecksum>
12
     </CustomFieldOrder>
13
</ApplicationVersion>
1
{
2
     "applicationVersion": {
3
          "applicationVersionId
ApplicationVersionId

Application version identifier

": "{String}",
4
          "status
Status

Status of application

": "{Integer}",
5
          "name
Name

Name of application

": "{String}",
6
          "applicationMatch
ApplicationMatch

Matching Keyword

": "{String}",
7
          "contentType
ContentType

Content Type

": "{String}",
8
          "masterUrl
MasterUrl

Url of application

": "{String}",
9
          "description
Description

Descriptive name of the application

": "{String}",
10
          "customFieldOrder
CustomFieldOrder

It is possible for a customer to rearrange the fields within a component. If they choose to do so for one or more of the components in this application, the fieldorder will contain a json structure that will keep information about the field order they have selected.

": {
11
               "fieldOrder
FieldOrder

A json structure describing the field order

": "{String}",
12
               "fieldOrderChecksum
FieldOrderChecksum

An md5 hash of the fieldorder

": "{String}"
13
          }
14
     }
15
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 107080 HTTP 403 You have only admittance to your own objects