Create a Settlement for an Item Dispute
post
/bcws/webresources/v1.0/disputes/settlement/item/{id}
Create a settlement for the specified item.
Request
Path Parameters
-
id(required): string
The ID of the item in dispute.
Supported Media Types
- application/xml
- application/json
Information about the settlement. The minimum required parameter is amount.
Root Schema : schema
Type:
Show Source
object
-
actionAffectsRef: object
ResourceRef
-
amount(required): number
The amount of the adjustment.
-
amountIsCredit: boolean
Default Value:
true
Whether the adjustment is a credit (true) or a debit (false). -
effective: string
(date-time)
The date and time the adjustment takes effect.
-
extension: object
extension
The extended attributes.
-
includeTax: boolean
Default Value:
true
Whether to include the tax in the adjustment (true) or not (false). -
notes: object
Notes
-
resourceId: integer
(int32)
The ID of the resource to adjust.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Notes
Type:
Show Source
object
-
accountId(required): string
The ID of the account associated with the note.
-
amount: number
The amount associated with the note. It can be a payment amount, adjustment amount, or so on.
-
billId: string
The ID of the bill associated with the note.
-
billUnitId: string
The ID of the bill unit associated with the note.
-
closedDate: string
(date-time)
The date and time the note was resolved.
-
comments: array
comments
The list of comments associated with the note.
-
count: integer
(int32)
The number of comments associated with the note.
-
domainId: integer
(int32)
The domain ID associated with the note.
-
effectiveDate: string
(date-time)
The date and time the comment was posted.
-
eventId: string
The ID of the event associated with the note.
-
extension: object
extension
The extended attributes.
-
header: string
The header associated with the note.
-
id: string
The ID.
-
itemId: string
The ID of the item associated with the note.
-
reasonId: integer
(int32)
The reason ID associated with the note. Possible values are stored in /config/reason_code_scope objects. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the reasons.locale file.
-
serviceId: string
The service ID associated with the note.
-
status: number
The note's status: not set (100), resolved (101), or unresolved (102). The default value is 102.
-
subType: integer
(int32)
The note's subtype. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
-
type: integer
(int32)
The note's type. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
Nested Schema : comments
Type:
array
The list of comments associated with the note.
Show Source
-
Array of:
object Comments
The list of comments associated with the note.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Comments
Type:
object
The list of comments associated with the note.
Show Source
-
comment(required): string
The comment.
-
csrAccountId: string
The CSR's account ID.
-
csrFirstName: string
The CSR's first name.
-
csrLastName: string
The CSR's last name.
-
csrLoginId: string
The login ID associated with the CSR.
-
entryDate: string
(date-time)
The date and time the comment was entered by the CSR.
-
externalUser: string
The external user.
-
trackingId: string
The tracking ID.
Information about the settlement. The minimum required parameter is amount.
Root Schema : schema
Type:
Show Source
object
-
actionAffectsRef: object
ResourceRef
-
amount(required): number
The amount of the adjustment.
-
amountIsCredit: boolean
Default Value:
true
Whether the adjustment is a credit (true) or a debit (false). -
effective: string
(date-time)
The date and time the adjustment takes effect.
-
extension: object
extension
The extended attributes.
-
includeTax: boolean
Default Value:
true
Whether to include the tax in the adjustment (true) or not (false). -
notes: object
Notes
-
resourceId: integer
(int32)
The ID of the resource to adjust.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Notes
Type:
Show Source
object
-
accountId(required): string
The ID of the account associated with the note.
-
amount: number
The amount associated with the note. It can be a payment amount, adjustment amount, or so on.
-
billId: string
The ID of the bill associated with the note.
-
billUnitId: string
The ID of the bill unit associated with the note.
-
closedDate: string
(date-time)
The date and time the note was resolved.
-
comments: array
comments
The list of comments associated with the note.
-
count: integer
(int32)
The number of comments associated with the note.
-
domainId: integer
(int32)
The domain ID associated with the note.
-
effectiveDate: string
(date-time)
The date and time the comment was posted.
-
eventId: string
The ID of the event associated with the note.
-
extension: object
extension
The extended attributes.
-
header: string
The header associated with the note.
-
id: string
The ID.
-
itemId: string
The ID of the item associated with the note.
-
reasonId: integer
(int32)
The reason ID associated with the note. Possible values are stored in /config/reason_code_scope objects. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the reasons.locale file.
-
serviceId: string
The service ID associated with the note.
-
status: number
The note's status: not set (100), resolved (101), or unresolved (102). The default value is 102.
-
subType: integer
(int32)
The note's subtype. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
-
type: integer
(int32)
The note's type. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
Nested Schema : comments
Type:
array
The list of comments associated with the note.
Show Source
-
Array of:
object Comments
The list of comments associated with the note.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Comments
Type:
object
The list of comments associated with the note.
Show Source
-
comment(required): string
The comment.
-
csrAccountId: string
The CSR's account ID.
-
csrFirstName: string
The CSR's first name.
-
csrLastName: string
The CSR's last name.
-
csrLoginId: string
The login ID associated with the CSR.
-
entryDate: string
(date-time)
The date and time the comment was entered by the CSR.
-
externalUser: string
The external user.
-
trackingId: string
The tracking ID.
Response
Supported Media Types
- application/xml
- application/json
201 Response
The settlement was created successfully.
Root Schema : resource
Type:
Show Source
object
-
extension: object
extension
The extended attributes.
-
reference(required): object
ResourceRef
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
400 Response
The request isn't valid.
500 Response
An internal server error occurred.
Examples
This example shows how to create a settlement for an item dispute by submitting a POST request on the REST resource using cURL. For more information about cURL, see "Use cURL".
cURL Command
curl -X POST 'http://hostname:port/bcws/webresources/version/disputes/settlement/item/0.0.0.1+-item-cycle_forward+268139' -H 'content-type: application/json' -d @settleItemDispute.json
where:
- hostname is the URL for the Billing Care REST server.
- port is the port for the Billing Care REST server.
- version is the version of the API you're using, such as v1.0.
- settleItemDispute.json is the JSON file that specifies the settlement details.
Example of Request Body
This shows an example of the contents of the settleItemDispute.json file sent as the request body.
{
"amount": 5,
"notes": {
"extension": null,
"id": "0.0.0.1+-note+274771",
"accountId": "0.0.0.1+-account+266347",
"amount": -5,
"billUnitId": "0.0.0.1+-billinfo+269419",
"billId": null,
"closedDate": 1612341749000,
"count": 1,
"effectiveDate": 1612341749000,
"eventId": "0.0.0.0++0",
"header": "",
"itemId": "0.0.0.1+-item-dispute+275027",
"subType": 215,
"type": 200,
"domainId": 34,
"reasonId": 1,
"serviceId": "0.0.0.0++0",
"status": 101,
"comments": [
{
"csrLoginId": "HeadCSR",
"csrFirstName": "Alia",
"csrLastName": "Abadi",
"csrAccountId": "1234",
"externalUser": "CSR Portal",
"comment": "Resolving item dispute.",
"trackingId": "",
"entryDate": 1612341749000
}
]
}
}
Example of Response Body
This shows an example of the response body, which includes the settlement ID and URI.
{
"extension": null,
"reference": {
"id": "0.0.0.1+-item-settlement+273226",
"uri": "http://hostname:port/bcws/webresources/v1.0/disputes/settlement/0.0.0.1+-item-settlement+273226"
}
}