System APIs
Add email content to provided output object definition.
| HTTP method | POST |
| URI | https://api.rambase.net/system/output-object-definitions/{outputObjectDefinitionId}/email-settings/contents |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {outputObjectDefinitionId} |
Output object definition identifier
Integer, minimum 100000 |
| Successful HTTP status code | 201 |
| API resource identifier | 2922, version 6 |
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.
Language
Required/mandatory field
Language of the content. Three character code following the ISO 639-2 standard.
Applicable domain values can be found here
>{String}</Language>Subject
Subject of the content
This field is optional.
>{String}</Subject>Body
Body of the content
This field is optional.
>{String}</Body>Filename
Filename for the content
Input must match the following regular expression pattern: ^([\{\}\(\)\. A-ZØÆÅa-zøæå0-9_-]+)$
This field is optional.
>{String}</Filename>Language
Required/mandatory field
Language of the content. Three character code following the ISO 639-2 standard.
Applicable domain values can be found here
": "{String}",Subject
Subject of the content
This field is optional.
": "{String}",Body
Body of the content
This field is optional.
": "{String}",Filename
Filename for the content
Input must match the following regular expression pattern: ^([\{\}\(\)\. A-ZØÆÅa-zøæå0-9_-]+)$
This field is optional.
": "{String}"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. |
| $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.
Language
Language of the content. Three character code following the ISO 639-2 standard.
>{String}</Language>Subject
Subject of the content
>{String}</Subject>Body
Body of the content
>{String}</Body>Filename
Filename for the content
>{String}</Filename>Language
Language of the content. Three character code following the ISO 639-2 standard.
": "{String}",Subject
Subject of the content
": "{String}",Body
Body of the content
": "{String}",Filename
Filename for the content
": "{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 101114 HTTP 404 | Output object setting not found |
| Error 103568 HTTP 400 | An email already exists with this language |