System APIs
Creates a new version of output design
HTTP method | POST |
URI | https://api.rambase.net/system/output-designs/{outputDesignId}/versions |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {outputDesignId} |
Output design identifier
Integer, minimum 100000 |
Successful HTTP status code | 201 |
API resource identifier | 2389, version 13 |
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.
DesignType
Required/mandatory field
This is the various types the output design can be
Applicable domain values can be found here
>{String}</DesignType>Description
Description of this output design version
This field is optional.
>{String}</Description>HashCode
This is the generated hashcode of the report file. This uniquely identifies the output design.
This field is optional.
>{String}</HashCode>OutputType
This defines the type of the output will be.
Examples: pdf, docx, xls, ...
More can be added if they are made available through the output designer.
Applicable domain values can be found here
This field is optional.
>{String}</OutputType>ExternalFilePath
ExternalFilePath is for TYPE eq FILE.
It is will be an optional field and will contain a path to an external file.
Ex: C:\NiceLabel\Return label 1\
This field is optional.
>{String}</ExternalFilePath>LegacyDesigns
This field is optional.
>LayoutId
The identifier of the legacy layout
This field is optional.
>{Integer}</LayoutId>LogoId
The identifier of the logo used in the legacy layout
This field is optional.
>{Integer}</LogoId>DateFormatId
The identifier of the date formats used in the legacy layout
This field is optional.
>{Integer}</DateFormatId>BarcodeId
The identifier of the barcodes used in the legacy layout
This field is optional.
>{Integer}</BarcodeId>DataSource
This field is optional.
>DataSourceId
Data source identifier
This field is optional.
>{Integer}</DataSourceId>DesignType
Required/mandatory field
This is the various types the output design can be
Applicable domain values can be found here
": "{String}",Description
Description of this output design version
This field is optional.
": "{String}",HashCode
This is the generated hashcode of the report file. This uniquely identifies the output design.
This field is optional.
": "{String}",OutputType
This defines the type of the output will be.
Examples: pdf, docx, xls, ...
More can be added if they are made available through the output designer.
Applicable domain values can be found here
This field is optional.
": "{String}",ExternalFilePath
ExternalFilePath is for TYPE eq FILE.
It is will be an optional field and will contain a path to an external file.
Ex: C:\NiceLabel\Return label 1\
This field is optional.
": "{String}",LegacyDesigns
This field is optional.
": {LayoutId
The identifier of the legacy layout
This field is optional.
": "{Integer}",LogoId
The identifier of the logo used in the legacy layout
This field is optional.
": "{Integer}",DateFormatId
The identifier of the date formats used in the legacy layout
This field is optional.
": "{Integer}",BarcodeId
The identifier of the barcodes used in the legacy layout
This field is optional.
": "{Integer}"DataSource
This field is optional.
": {DataSourceId
Data source identifier
This field is optional.
": "{Integer}"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.
$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 |
$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. |
$showDomainDescriptions Boolean, optional | Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false. |
$lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
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.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
OutputDesignVersionId
Identifier of the version
>{Integer}</OutputDesignVersionId>Status
Version status
>{Integer}</Status>DesignType
This is the various types the output design can be
Possible domain values can be found here
>{String}</DesignType>Description
Description of this output design version
>{String}</Description>HashCode
This is the generated hashcode of the report file. This uniquely identifies the output design.
>{String}</HashCode>OutputType
This defines the type of the output will be.
Examples: pdf, docx, xls, ...
More can be added if they are made available through the output designer.
Possible domain values can be found here
>{String}</OutputType>ExternalFilePath
ExternalFilePath is for TYPE eq FILE.
It is will be an optional field and will contain a path to an external file.
Ex: C:\NiceLabel\Return label 1\
CreatedAt
Date and time of creation
>{Datetime}</CreatedAt>CreatedBy
The user id of the person how created the version of the output design
>EmployeeId
Employee identifier
>{Integer}</EmployeeId>LastName
Last name of employee
>{String}</LastName>EmployeeLink
Employee reference
>{String}</EmployeeLink>LayoutId
The identifier of the legacy layout
>{Integer}</LayoutId>LogoId
The identifier of the logo used in the legacy layout
>{Integer}</LogoId>DateFormatId
The identifier of the date formats used in the legacy layout
>{Integer}</DateFormatId>BarcodeId
The identifier of the barcodes used in the legacy layout
>{Integer}</BarcodeId>DataSourceId
Data source identifier
>{Integer}</DataSourceId>DataSourceLink
Data source reference
>{String}</DataSourceLink>OutputDesignVersionId
Identifier of the version
": "{Integer}",Status
Version status
": "{Integer}",DesignType
This is the various types the output design can be
Possible domain values can be found here
": "{String}",Description
Description of this output design version
": "{String}",HashCode
This is the generated hashcode of the report file. This uniquely identifies the output design.
": "{String}",OutputType
This defines the type of the output will be.
Examples: pdf, docx, xls, ...
More can be added if they are made available through the output designer.
Possible domain values can be found here
": "{String}",ExternalFilePath
ExternalFilePath is for TYPE eq FILE.
It is will be an optional field and will contain a path to an external file.
Ex: C:\NiceLabel\Return label 1\
CreatedAt
Date and time of creation
": "{Datetime}",CreatedBy
The user id of the person how created the version of the output design
": {EmployeeId
Employee identifier
": "{Integer}",LastName
Last name of employee
": "{String}",EmployeeLink
Employee reference
": "{String}"LayoutId
The identifier of the legacy layout
": "{Integer}",LogoId
The identifier of the logo used in the legacy layout
": "{Integer}",DateFormatId
The identifier of the date formats used in the legacy layout
": "{Integer}",BarcodeId
The identifier of the barcodes used in the legacy layout
": "{Integer}"DataSourceId
Data source identifier
": "{Integer}",DataSourceLink
Data source reference
": "{String}"
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 102382 HTTP 404 | Data source not found |
Error 102608 HTTP 404 | Legacy design of type {0} is not found :: {1} |