POST
/
workspace
/
{ws_id}
/
case_management
/
table
/
attachments
curl --request POST \
  --url https://app.blinkops.com/api/v1/workspace/{ws_id}/case_management/table/attachments \
  --header 'BLINK-API-KEY: <api-key>' \
  --header 'Content-Type: */*' \
  --data '{
  "attachment": "a97cfe4c-8ce3-4f67-ad17-a17f6087663a",
  "description": "Network log file for analysis",
  "name": "Network Log File",
  "type": "Network Log"
}'
{
  "attachment": "a97cfe4c-8ce3-4f67-ad17-a17f6087663a",
  "description": "Network log file for analysis",
  "name": "Network Log File",
  "type": "Network Log"
}

Authorizations

​
BLINK-API-KEY
string
header
required

Use your API key to access BlinkOps API. To generate an API key, please log in to your BlinkOps account and navigate to the API Keys section in the user settings page. Add the generated key to your request headers as BLINK-API-KEY.

Path Parameters

​
ws_id
string
required

Workspace ID

Body

*/*
Attachment Data
​
attachment
string
Example:

"a97cfe4c-8ce3-4f67-ad17-a17f6087663a"

​
description
string
Example:

"Network log file for analysis"

​
name
string
Example:

"Network Log File"

​
type
enum<string>
Available options:
Network Log,
Malware Sample,
PCAP File,
Report,
Screenshot,
Document
Example:

"Network Log"

Response

200
*/*
OK
​
attachment
string
Example:

"a97cfe4c-8ce3-4f67-ad17-a17f6087663a"

​
description
string
Example:

"Network log file for analysis"

​
name
string
Example:

"Network Log File"

​
type
enum<string>
Available options:
Network Log,
Malware Sample,
PCAP File,
Report,
Screenshot,
Document
Example:

"Network Log"

Was this page helpful?