Skip to main content
POST
/
files
/
encrypted
/
index
Index encrypted files
curl --request POST \
  --url https://proxy.cci.prem.io/files/encrypted/index \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "files": [
    {
      "file_id": "<string>",
      "encrypted_file_dek": "<string>",
      "encrypted_rag_dek": "<string>",
      "file_nonce": "<string>",
      "rag_dek_nonce": "<string>",
      "s3_r2_path": "<string>",
      "cipher_text": "<string>"
    }
  ]
}
'
{
  "status": 200,
  "data": {
    "results": [
      {
        "file_id": "file_0198042e-6dde-7b9c-bc91-452a7e0c833b",
        "rag_status": "running",
        "success": true
      },
      {
        "file_id": "file_0198042e-6dde-7b9c-bc91-452a7e0c833c",
        "rag_status": "running",
        "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 indexing encrypted files for RAG

​
files
object[]
required

Array of encrypted files to index

Minimum array length: 1

Response

Files indexed successfully

Response containing the file indexing 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"