System APIs

GET system/error-messages/{errorMessageId}

Retrieves all information about the specified error-message

HTTP method	GET
URI	https://api.rambase.net/system/error-messages/{errorMessageId}
Supported formats	Xml, Html, Json (ex. $format=json)
- URI parameter {errorMessageId}	Error message identifier Integer, minimum 10000
Successful HTTP status code	200
API resource identifier	150, version 9

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:

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.
$expand String, optional	Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable 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:

                                        <ErrorMessage>
                                    

<ErrorMessageId

ErrorMessageId

Error message identifier

>{Integer}</ErrorMessageId>

<Status

Status

Object status of the errormessage

>{String}</Status>

<Namespace

Namespace

Namespace of the error message. Used for categorization only.

>{String}</Namespace>

<HttpStatusCode

HttpStatusCode

The HTTP Status Code that will be used when sending out the error-message (ex. 500, 404)

>{Integer}</HttpStatusCode>

<Message

Message

The english error-message

>{String}</Message>

<TechnicalDescription

TechnicalDescription

A techinical description describing causes of the error and solutions to the problem

>{String}</TechnicalDescription>

                                             <Repository>
                                    

<IsChanged

IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

>{Boolean}</IsChanged>

<ChangedBy

ChangedBy

EmployeeId of the employee making the change

>{Integer}</ChangedBy>

                                             </Repository>
                                    

<Translations

Translations

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

<Translation

Translation

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

<Language

Language

The language of the translated error-message

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

>{String}</Language>

<TranslatedMessage

TranslatedMessage

The translated error-message

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

>{String}</TranslatedMessage>

                                                  </Translation>
                                    

                                             </Translations>
                                    

                                        </ErrorMessage>
                                    

{

                                             "errorMessage": {
                                    

"errorMessageId

ErrorMessageId

Error message identifier

": "{Integer}",

"status

Status

Object status of the errormessage

": "{String}",

"namespace

Namespace

Namespace of the error message. Used for categorization only.

": "{String}",

"httpStatusCode

HttpStatusCode

The HTTP Status Code that will be used when sending out the error-message (ex. 500, 404)

": "{Integer}",

"message

Message

The english error-message

": "{String}",

"technicalDescription

TechnicalDescription

A techinical description describing causes of the error and solutions to the problem

": "{String}",

                                                  "repository": {
                                    

"isChanged

IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

": "{Boolean}",

"changedBy

ChangedBy

EmployeeId of the employee making the change

": "{Integer}"

},

"translations

Translations

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

": [

{

"language

Language

The language of the translated error-message

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

": "{String}",

"translatedMessage

TranslatedMessage

The translated error-message

This field is greyed out because it is an expandable field. You have to add $expand=Translations in your request URI to get this field

": "{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 100619 HTTP 404

Error message not found