API

Production APIs

POST production/work-order-operations/reopen-reasons

Create a new Reopen Reason

HTTP method POST
URI https://api.rambase.net/production/work-order-operations/reopen-reasons
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 4267, version 1

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
<ReopenReason>
2
     <Description
Description

Required/mandatory field

Description of the name/value/code/key

>{String}</Description>
3
</ReopenReason>
1
{
2
     "reopenReason": {
3
          "description
Description

Required/mandatory field

Description of the name/value/code/key

": "{String}"
4
     }
5
}

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.

Format:
1
<ReopenReason>
2
     <ReopenReasonId
ReopenReasonId

Identifer of Reopen Reason

>{Integer}</ReopenReasonId>
3
     <Status
Status

Status of Reopen Reason

>{String}</Status>
4
     <Value
Value

Value of Reopen Reason

>{String}</Value>
5
     <Priority
Priority

Priority of Reopen Reason

>{Integer}</Priority>
6
     <Description
Description

Description of the name/value/code/key

>{String}</Description>
7
     <TranslatedDescription
TranslatedDescription

Description of the name/value/code/key

>{String}</TranslatedDescription>
8
</ReopenReason>
1
{
2
     "reopenReason": {
3
          "reopenReasonId
ReopenReasonId

Identifer of Reopen Reason

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

Status of Reopen Reason

": "{String}",
5
          "value
Value

Value of Reopen Reason

": "{String}",
6
          "priority
Priority

Priority of Reopen Reason

": "{Integer}",
7
          "description
Description

Description of the name/value/code/key

": "{String}",
8
          "translatedDescription
TranslatedDescription

Description of the name/value/code/key

": "{String}"
9
     }
10
}

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 100027 HTTP 400 Missing mandatory parameter {0}
Error 105991 HTTP 400 Event is not of the same type as event set on the automated flow
Error 100012 HTTP 400 {0} must exist in {1}