REST API for Oracle Banking Collections

Add New Case Account Association

post

/obcr-strategy-services/api/v1/dmcaseaccountassos

This endpoint is used to add a new Case Account Association.

Request

Supported Media Types

application/json
application/xml

Header Parameters

appId(required): string

The application ID of host service.
branchCode(required): string

The branch code of requesting branch.
contentType: string

The content type of request or response body.
userId(required): string

The user ID of requesting user.

Request Body that contains data required for creating a new Case Account Association.

Root Schema : DmCaseAccountAssociationDTO

Type: object

DmCaseAccountAssociation DTO

Show Source

accountId: string

Account ID of the Case Account Association
caseId: string

Case ID of the Case Account Association
endDt: string

End Date of the Case Account Association
startDt: string

Start Date of the Case Account Association

{
    "description":"DmCaseAccountAssociation DTO",
    "type":"object",
    "properties":{
        "caseId":{
            "description":"Case ID of the Case Account Association",
            "type":"string"
        },
        "accountId":{
            "description":"Account ID of the Case Account Association",
            "type":"string"
        },
        "startDt":{
            "description":"Start Date of the Case Account Association",
            "type":"string"
        },
        "endDt":{
            "description":"End Date of the Case Account Association",
            "type":"string"
        }
    }
}

Response

Supported Media Types

application/json
application/xml

201 Response

Returns the Id of the newly created Case Account Association.

Headers

Location: string

URL of newly created Case Account Association

Root Schema : inlineResponse201

Type: object

ID of the newly created order.

Show Source

id: string

{
    "description":"ID of the newly created order.",
    "type":"object",
    "properties":{
        "id":{
            "type":"string"
        }
    }
}

400 Response

Malformed syntax.

401 Response

Request does not have sufficient credentials.

403 Response

Request is not authorized.

405 Response

Invalid input

500 Response

Internal error