Introduction

The Case Management API provides a RESTful public interface to interact with support cases. By using this API, you can create cases, get case statuses, add comments to a case, add and remove users from a case watchlist, download and add attachments, and more.

Endpoint URL

The Case Management API uses the following global endpoint URL. When you call the API, add the path for each method to form the complete API endpoint for your requests.

https://support-center.cloud.ibm.com

Example API request

curl -X {request_method} "https://support-center.cloud.ibm.com/{method_endpoint}"

Replace {request_method} and {method_endpoint} in this example with the values for your particular API call.

Authentication and authorization

Authentication and authorization to the Case Management REST API are enforced by using an IAM access token. The token is used to determine the access roles that the identity has access to when using the user management account management service. For information about how to obtain an IAM token for an authenticated user or service ID, see the IAM Identity Service API documentation.

Use of the IAM Policy Management REST API is done by adding a valid IAM token to the HTTP Authorization request header. Example: -H 'Authorization: Bearer $TOKEN'

To retrieve your access token:

curl -X POST \
'https://iam.cloud.ibm.com/identity/token' \
-H 'Authorization: TOKEN' \
-H 'Content-Type: application/x-www-form-urlencoded'
-d 'grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=MY_APIKEY'

Case Scope

All cases are in the scope of the account specified in the IAM token. Make sure that you have the IAM token that has account information. If you generate the IAM token through some API, you might forget adding the account information.

Error Handling

The Case Management APIs return standard HTTP status codes to indicate the success or failure of a request. The format of the response is represented in JSON.

If an operation can't be fulfilled, an appropriate 400 or 500 series HTTP response is returned from the server. The operations defined in the Reference section describe example errors that can be returned from a failed request. All responses from the IAM Policy Management API are in the JSON format.

Here are potential error codes that the API can return.

HTTP Error Code Description Recovery
200 Success The request was successful.
201 Created The resource was successfully created.
204 No Content The request was successful. No response body is provided.
400 Bad Request The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all required parameters in your request.
401 Unauthorized You are not authorized to make this request. The token is either invalid, missing or expired. Get a new valid token and try again.
403 Forbidden The token is valid, but the subject of the token is not authorized to perform the operation. If this error persists, contact the account owner to check your permissions.
404 Not Found The requested resource could not be found.
409 Conflict The entity is already in the requested state.
415 Unsupported Media Type Request body sent was formatted using an unsupported media type.
429 Too Many Requests Too many requests have been made within a given time window. Wait before calling the API again.
500 Service Unavailable IAM Policy Management Point is currently unavailable. Your request could not be processed. Wait a few minutes and try again.
{
    "trace": "cd4f7573121a4cf99f0079f8482b3d6b",
    "errors": [
        {
            "code": "invalid_token",
            "message": "The provided IAM token is invalid."
        }
    ],
    "status_code": 401
}

Methods

Get cases in account

Get cases in the account which is specified by the content of the IAM token.

GET /case-management/v1/cases
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Query Parameters

  • Number of cases should be skipped

    Default: 0

  • Number of cases should be returned

    Default: 10

  • String that a case might contain

  • Sort field and direction. If omitted, default to descending of updated date. Prefix "~" signifies sort in descending.

    Allowable values: [number,short_description,severity,updated_at,created_at,~number,~short_description,~severity,~updated_at,~created_at]

  • Case status filter

    Allowable values: [new,in_progress,waiting_on_client,resolution_provided,resolved,closed]

    Constraints: collection format: csv

  • Seleted fields of interest instead of the entire case information

    Allowable values: [number,short_description,description,created_at,created_by,updated_at,updated_by,contact,contact_type,status,severity,support_tier,resolution,close_notes,invoice_number,eu,watchlist,attachments,resources,comments,offering]

    Constraints: number of items ≥ 1, contains only unique items, collection format: csv

  • curl -X GET \
    'https://support-center.cloud.ibm.com/case-management/v1/cases?offset=0&limit=10&status=new,in_progress,waiting_on_client,resolution_provided' \
    -H 'Authorization: TOKEN' \
    
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

Example responses
  • {
      "total_count": 69,
      "first": {
        "href": "http://support-center.cloud.ibm.com/cases?limit=0"
      },
      "next": {
        "href": "http://support-center.cloud.ibm.com/cases?limit=10&offset=10"
      },
      "last": {
        "href": "http://support-center.cloud.ibm.com/cases?limit=10&offset=60"
      },
      "cases": [
        {
          "number": "CS1234567",
          "short_description": "Test",
          "description": "test",
          "created_at": "2019-07-21 05:20:12",
          "created_by": {
            "name": "Example Name",
            "user_id": "email@example.com",
            "realm": "IBMid",
            "type": "customer"
          },
          "updated_at": "2019-07-30 21:39:40",
          "updated_by": {
            "name": "Example Name",
            "user_id": "Example Name",
            "realm": "IBMid",
            "type": "customer"
          },
          "contact": {
            "name": "Example Name",
            "user_id": "email@example.com",
            "realm": "IBMid",
            "type": "customer"
          },
          "contact_type": "Cloud Support Center",
          "status": "In Progress",
          "severity": 4,
          "support_tier": "Premium",
          "resolution": "",
          "close_notes": "",
          "invoice_number": "",
          "eu": {
            "support": false,
            "data_center": ""
          },
          "watchlist": [
            {
              "name": "Example Name",
              "user_id": "email@example.com",
              "realm": "IBMid",
              "type": "customer"
            }
          ],
          "attachments": [
            {
              "id": "28ccc7e0db12fb123456dd4b5e96191f",
              "filename": "example.png",
              "size_in_bytes": 1000,
              "created_at": "2019-06-24 15:19:36"
            }
          ],
          "url": "https://support-center.cloud.ibm.com/case-management/v1/cases/CS1234567/attachments/28acc7e0db12fb801785dd4b5e96191f",
          "resources": null,
          "comments": [
            {
              "value": "Test comment",
              "added_at": "2019-06-21 18:08:01",
              "added_by": {
                "name": "Example Name",
                "user_id": "email@example.com",
                "realm": "IBMid",
                "type": "customer"
              }
            }
          ]
        }
      ]
    }

Create a case

Create a case in the account.

POST /case-management/v1/cases
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

The case to create

Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

Example responses
  • {
      "number": "string",
      "short_description": "string",
      "description": "string",
      "created_at": "string",
      "created_by": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "updated_at": "string",
      "updated_by": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "contact_type": "Cloud Support Center",
      "contact": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "status": "string",
      "severity": 0,
      "support_tier": "Free",
      "resolution": "string",
      "close_notes": "string",
      "eu": {
        "support": true,
        "data_center": "string"
      },
      "watchlist": [
        {
          "name": "John Doe",
          "realm": "IBMid",
          "user_id": "johndoe@ibm.com"
        }
      ],
      "attachments": [
        {
          "id": "string",
          "filename": "string",
          "size_in_bytes": 0,
          "created_at": "string",
          "url": "string"
        }
      ],
      "offering": {
        "id": "string",
        "value": "string"
      },
      "resources": [
        {
          "crn": "string",
          "name": "string",
          "type": "string",
          "url": "string",
          "note": "string"
        }
      ],
      "comments": [
        {
          "value": "string",
          "added_at": "string",
          "added_by": {
            "name": "John Doe",
            "realm": "IBMid",
            "user_id": "johndoe@ibm.com"
          }
        }
      ]
    }

Get a case in account

Get a case in the account that is specified by the case number.

GET /case-management/v1/cases/{case_number}
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

Query Parameters

  • Selected fields of interest instead of the entire case information

    Constraints: collection format: csv

  • curl -X GET \
    '/case-management/cases/{case_number}?fields=number,updated_at,resources' \
    -H 'Authorization: TOKEN' \
    
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "number": "CS0264883",
      "short_description": "Test case created by linked account",
      "description": "Test",
      "created_at": "2019-05-24 16:30:20",
      "created_by": {
        "name": "John Doe",
        "user_id": "JohnDoe@example.com",
        "realm": "IBMid",
        "type": "customer"
      },
      "updated_at": "2019-08-21 17:09:35",
      "updated_by": {
        "name": "John Doe",
        "user_id": "JohnDoe@example.com",
        "realm": "IBMid",
        "type": "customer"
      },
      "contact": {
        "name": "John Doe",
        "user_id": "JohnDoe@example.com",
        "realm": "IBMid",
        "type": "customer"
      },
      "contact_type": "Cloud Support Center",
      "status": "In Progress",
      "severity": 4,
      "support_tier": "Premium",
      "resolution": "",
      "close_notes": "",
      "invoice_number": "",
      "eu": {
        "support": false,
        "data_center": ""
      },
      "watchlist": [
        {
          "name": "Jane Doe",
          "user_id": "JaneDoe@example.com",
          "realm": "IBMid",
          "type": "customer"
        },
        {
          "name": "Jorge Doe",
          "user_id": "JorgeDoe@example.com",
          "realm": "IBMid",
          "type": "customer"
        }
      ],
      "attachments": [
        {
          "id": "f2222514dbbbf7c01785dd4b5e111973",
          "filename": "add--solid.svg",
          "size_in_bytes": 135,
          "created_at": "2019-05-29 16:42:07",
          "url": "localhost:8080/case-management/v1/cases/CS0264883/attachments/f7262514db7df7c01785dd4b5e961973"
        }
      ],
      "resources": [
        {
          "crn": "211770",
          "name": "ir-origin01.sliad.dataxu.net",
          "type": "ims",
          "url": "https://cloud.ibm.com/gen1/infrastructure/bare-metal/211770/details",
          "note": null
        },
        {
          "crn": "274300",
          "name": "rts-am269.sliad.dataxu.net",
          "type": "SoftLayer_Hardware",
          "url": null,
          "note": null
        },
        {
          "crn": "242458",
          "name": "lb108.wdc01.dataxu.com",
          "type": "ims",
          "url": "https://cloud.ibm.com/gen1/infrastructure/bare-metal/242458/details",
          "note": null
        },
        {
          "crn": "244120",
          "name": "rts-am058.sliad.dataxu.net",
          "type": "ims",
          "url": "https://cloud.ibm.com/gen1/infrastructure/bare-metal/244120/details",
          "note": null
        },
        {
          "crn": "211883",
          "name": "analytics06.sldc.dataxu.net",
          "type": "ims",
          "url": "https://cloud.ibm.com/gen1/infrastructure/bare-metal/211883/details",
          "note": null
        }
      ],
      "comments": [
        {
          "value": "Test another comment",
          "added_at": "2019-05-24 16:58:58",
          "added_by": {
            "name": "June Doe",
            "user_id": "JuneDoe@example.com",
            "realm": "IBMid",
            "type": "customer"
          }
        },
        {
          "value": "Test unresolved",
          "added_at": "2019-05-24 16:33:52",
          "added_by": {
            "name": "John Doe",
            "user_id": "JohnDoe@example.com",
            "realm": "IBMid",
            "type": "customer"
          }
        },
        {
          "value": "Close notes: ",
          "added_at": "2019-05-24 16:33:52",
          "added_by": {
            "name": "John Doe",
            "user_id": "JohnDoe@example.com",
            "realm": "IBMid",
            "type": "customer"
          }
        },
        {
          "value": "Close notes: Solution provided by an IBM support engineer",
          "added_at": "2019-05-24 16:32:09",
          "added_by": {
            "name": "John Doe",
            "user_id": "JohnDoe@example.com",
            "realm": "IBMid",
            "type": "customer"
          }
        },
        {
          "value": "Test comment",
          "added_at": "2019-05-24 16:31:32",
          "added_by": {
            "name": "John does",
            "user_id": "JohnDoe@example.com",
            "realm": "IBMid",
            "type": "customer"
          }
        }
      ],
      "offering": {
        "name": "Compute: Bare Metal",
        "type": {
          "group": "category",
          "key": "iaas:classic"
        }
      }
    }

Update case status

Mark the case as resolved or unresolved, or accept the provided resolution.

PUT /case-management/v1/cases/{case_number}/status
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

the update payload

  • curl -X PUT \
    '/case-management/cases/{case_number}/status' \
    -H 'Authorization: TOKEN' \
    -d '{
    "action": "resolve",
    "comment": "The issue is resolved. Thank you!"
    'resolution_code: 1'
    }'
  • curl -X PUT \
    '/cases/{case_number}/status' \
    -H 'Authorization: TOKEN' \
    -d '{
    "action": "unresolve",
    "comment": "The issue is not resolved!"
    }'
  • curl -X PUT \
    '/cases/{case_number}/status' \
    -H 'Authorization: TOKEN' \
    -d '{
    "action": "accept",
    "comment": "I accept the provided resolution."
    }'
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

  • Conflict - The requested resource is being modified in a different request

Example responses
  • {
      "number": "string",
      "short_description": "string",
      "description": "string",
      "created_at": "string",
      "created_by": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "updated_at": "string",
      "updated_by": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "contact_type": "Cloud Support Center",
      "contact": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      },
      "status": "string",
      "severity": 0,
      "support_tier": "Free",
      "resolution": "string",
      "close_notes": "string",
      "eu": {
        "support": true,
        "data_center": "string"
      },
      "watchlist": [
        {
          "name": "John Doe",
          "realm": "IBMid",
          "user_id": "johndoe@ibm.com"
        }
      ],
      "attachments": [
        {
          "id": "string",
          "filename": "string",
          "size_in_bytes": 0,
          "created_at": "string",
          "url": "string"
        }
      ],
      "offering": {
        "id": "string",
        "value": "string"
      },
      "resources": [
        {
          "crn": "string",
          "name": "string",
          "type": "string",
          "url": "string",
          "note": "string"
        }
      ],
      "comments": [
        {
          "value": "string",
          "added_at": "string",
          "added_by": {
            "name": "John Doe",
            "realm": "IBMid",
            "user_id": "johndoe@ibm.com"
          }
        }
      ]
    }

Add comment to case

Add a comment to a case.

PUT /case-management/v1/cases/{case_number}/comments
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • curl -X PUT \
    '/case-management/cases/{case_number}/comments' \
    -H 'Authorization: TOKEN' \
    -d '{
    "comment": "Test comment api"
    }'
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "value": "string",
      "added_at": "string",
      "added_by": {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      }
    }

Add users to watchlist of case

Add users to the watchlist of case. By adding a user to the watchlist of the case, you are granting them read and write permissions, so the user can view the case, receive updates, and make updates to the case. Note that the user must be in the account to be added to the watchlist.

PUT /case-management/v1/cases/{case_number}/watchlist
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • curl -X PUT \
    '/case-management/cases/{case_number}/watchlist' \
    -H 'Authorization: TOKEN' \
    -d '[
    {
    realm: "IBMid"
    user_id: "test@ibm.com"
    }
    ]'
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "added": [
        {
          "name": "John Doe",
          "realm": "IBMid",
          "user_id": "johndoe@ibm.com"
        }
      ],
      "failed": [
        {
          "name": "John Doe",
          "realm": "IBMid",
          "user_id": "johndoe@ibm.com"
        }
      ]
    }

Remove users from watchlist of case

Remove users from the watchlist of a case.

DELETE /case-management/v1/cases/{case_number}/watchlist
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • curl -X DELETE \
    '/case-management/cases/{case_number}/watchlist' \
    -H 'Authorization: TOKEN' \
    -d '[
    {
    realm: "IBMid"
    user_id: "test@ibm.com"
    }
    ]'
Response

User IDs in the watchlist

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • [
      {
        "name": "John Doe",
        "realm": "IBMid",
        "user_id": "johndoe@ibm.com"
      }
    ]

Add a resource to case

Add a resource to case by specifying the Cloud Resource Name (CRN), or id and type if attaching a class iaaS resource.

PUT /case-management/v1/cases/{case_number}/resources
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • curl -X PUT \
    '/case-management/cases/{case_number}/resources' \
    -H 'Authorization: TOKEN' \
    -d '{
    "crn": "296878"
    "note": "This resource does not work"
    }'
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "crn": "string",
      "name": "string",
      "type": "string",
      "url": "string",
      "note": "string"
    }

Add attachment(s) to case

You can add attachments to a case to provide more information for the support team about the issue that you're experiencing.

PUT /case-management/v1/cases/{case_number}/attachments
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

  • Allowable values: [multipart/form-data,application/octet-stream]

Path Parameters

  • Unique identifier of a case

Form Parameters

  • file of supported types, 8MB in size limit

  • curl -X PUT \
    '/case-management/cases/{case_number}/attachments' \
    -H 'Authorization: TOKEN' \
    -F file=@/Users/test/icon.svg
    
Response

Details of an attachment

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "id": "string",
      "filename": "string",
      "size_in_bytes": 0,
      "created_at": "string",
      "url": "string"
    }

Download an attachment

Download an attachment from a case.

GET /case-management/v1/cases/{case_number}/attachments/{file_id}
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • Unique identifier of a file

  • curl -X PUT \
    '/case-management/cases/{case_number}/watchlist' \
    -H 'Authorization: TOKEN' \
    -d '[
    "test@ibm.com"
    ]'
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • Success

Remove attachment from case

Remove an attachment from a case.

DELETE /case-management/v1/cases/{case_number}/attachments/{file_id}
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Path Parameters

  • Unique identifier of a case

  • Unique identifier of a file

  • curl -X DELETE \
    '/case-management/cases/{case_number}/attachments/{file_id}' \
    -H 'Authorization: TOKEN' \
    
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

  • Not Found - The requested resource does not exist.

Example responses
  • {
      "attachments": [
        {
          "id": "string",
          "filename": "string",
          "size_in_bytes": 0,
          "created_at": "string",
          "url": "string"
        }
      ]
    }

Shows how to mark case as EU supported

Shows how an account can mark a case as EU supported.

GET /case-management/utilities/v1/eu-support
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

No Sample Response

This method does not specify any sample responses.

Get offerings

Get offerings used in technical cases.

GET /case-management/utilities/v1/offerings/technical
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

No Sample Response

This method does not specify any sample responses.

Get resolution code values

Get the resolution code values used in "Update Status API"

GET /case-management/utilities/v1/constants/resolution-codes
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

  • curl -X GET \
    '/case-management/constants/resolutionCodes' \
    -H 'Authorization: TOKEN' \
    
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

No Sample Response

This method does not specify any sample responses.

Get status values

Get the status values used in case filtering

GET /case-management/utilities/v1/constants/statuses
Request

Custom Headers

  • The OAuth token obtained from the IBM Cloud Identity and Access Management (IAM) through a grant of type 'passcode', or 'apikey', or 'authorization_code'. For access to certain IBM Cloud resources, the OAuth token obtained using a IAM 'authorization_code' needs to be account-scoped, i.e. include the BSS/IMS account id, when obtaining the token through the call to the 'console-platform-express-session' module (as described in the module documentation)

  • curl -X GET \
    '/case-management/constants/statuses' \
    -H 'Authorization: TOKEN' \
    
Response

Status Code

  • Success

  • Unauthorized - unable to determine a valid authorization header. The Authorization header was not populated, the value is not a well-formed JWT token, or it is expired, etc.

  • Forbidden - insufficient permission. The client has been authenticated successfully, but the permissions set for the operation forbid this operation to the specified user.

No Sample Response

This method does not specify any sample responses.