Skip to main content
POST
/
files
/
encrypted
/
delete-index
Delete index of encrypted files
curl --request POST \
  --url https://proxy.cci.prem.io/files/encrypted/delete-index \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "cipher_text": "<string>",
  "encrypted_rag_dek": "<string>",
  "rag_dek_nonce": "<string>",
  "fileIds": [
    "<string>"
  ]
}
'
{
  "status": 200,
  "data": {
    "results": [
      {
        "file_id": "file_0198042e-6dde-7b9c-bc91-452a7e0c833b",
        "success": true
      },
      {
        "file_id": "file_0198042e-6dde-7b9c-bc91-452a7e0c833c",
        "success": true
      }
    ],
    "enclave_response": []
  },
  "error": null,
  "log": null,
  "validator": null,
  "support_id": null,
  "message": "Resource created successfully",
  "env": "development"
}

Authorizations

​
Authorization
string
header
required

Send your access token as header Authorization: Bearer {accessToken}

​
Authorization
string
header
required

Your API key that starts with sk_live or sk_test. You can create yours at go.prem.io/api-keys.

Body

application/json

Request body for deleting index of encrypted files from RAG

​
cipher_text
string
required

Cipher text for encryption context

Example:

"cipher_text_data"

​
encrypted_rag_dek
string
required

Encrypted RAG data encryption key

Example:

"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"

​
rag_dek_nonce
string
required

Nonce used for RAG DEK encryption

Example:

"0123456789abcdef0123456789abcdef"

​
fileIds
string[]
required

Array of file IDs to delete from index

Minimum array length: 1

File ID

Response

File indexes deleted successfully

Response containing the file index deletion status

​
status
enum<integer>
required

Status code of the response

Available options:
200,
201,
202
​
data
object
required

Response data containing the requested object

​
message
string | null
required

Message of the response, human readable

Example:

"Resource created successfully"

​
env
enum<string>
required

API environment

Available options:
development,
production
​
error
string | null

Error message of the response, human readable

Example:

"Invalid email address"

​
log

Useful informaiton, not always present, to debug the response

Examples:
{ "request_id": "req_1234567890" }

"Some pertinent log message"

​
validator

Validator response object, each key is the field name and value is the error message

Example:
{
  "email": "Invalid email address",
  "password": "Password is required"
}
​
support_id
string<uuid> | null

Support ID linked to the response, used to identify it when talking with our team

Example:

"support_uuidv7-something-else"