Quality management APIs
Creates a new deviation cost of quality issue.
| HTTP method | POST |
| URI | https://api.rambase.net/quality/issues/{qualityIssueId}/costs |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {qualityIssueId} |
Quality issue identifier
Integer, minimum 100000 |
| Successful HTTP status code | 201 |
| API resource identifier | 4594, version 5 |
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.
Cost
Required/mandatory field
Estimated cost of a quality issue.
Minimum value: 0
>{Decimal}</Cost>CostCategoryId
Required/mandatory field
Identifier of the domain value
Minimum value: 100000
>{Integer}</CostCategoryId>Cost
Required/mandatory field
Estimated cost of a quality issue.
Minimum value: 0
": "{Decimal}",CostCategoryId
Required/mandatory field
Identifier of the domain value
Minimum value: 100000
": "{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. |
| $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.
IssueCostId
Quality issue cost identifier
>{Integer}</IssueCostId>CreatedAt
Date and time of creation
>{Datetime}</CreatedAt>Cost
Estimated cost of a quality issue.
>{Decimal}</Cost>Currency
Three character code following the ISO 4217 standard
>{String}</Currency>CostCategoryId
Identifier of the domain value
>{Integer}</CostCategoryId>Name
Description of a domain value
>{String}</Name>IssueCostId
Quality issue cost identifier
": "{Integer}",CreatedAt
Date and time of creation
": "{Datetime}",Cost
Estimated cost of a quality issue.
": "{Decimal}",Currency
Three character code following the ISO 4217 standard
": "{String}",CostCategoryId
Identifier of the domain value
": "{Integer}",Name
Description of a domain value
": "{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 101606 HTTP 404 | Module not found |
| Error 102018 HTTP 403 | You need permission {0}. Duties with this permission: {1} |
| Error 101420 HTTP 404 | Setting definition not found |
| Error 106156 HTTP 400 | Department cannot be empty. |
| Error 106155 HTTP 400 | OccuredAt cannot be empty. |
| Error 105858 HTTP 400 | Responsible cannot be empty. |