What has been done with the files attached to this world

GET

/api/v1/chat/attachments

const url = 'http://localhost:11044/api/v1/chat/attachments';
const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url http://localhost:11044/api/v1/chat/attachments \
  --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

Newest first. An import runs in the background and can take over a minute, during which nothing else says it is happening — so this reports the finished ones too, which is what answers “did it work” after the fact.

Authorizations

apiKeyAuth
basicAuth

Responses

200

Ingestion records, newest first

application/json

Array<object>

What has happened to one file attached to this world: the handler that took it, whether its import is running, done or failed, and what it reported. Listed newest first by GET /chat/attachments

object

filename

required

The file’s name as it was attached

string

finishedAt

ISO-8601 instant the import finished or failed; null while importing

string

handler

required

Name of the handler that took the file

string

stale

required

True for an IMPORTING record started more than 15 minutes ago: most likely a process killed mid-import, not an import still running

boolean

startedAt

required

ISO-8601 instant the import started

string

state

required

IMPORTING (a handler is running now), IMPORTED, or FAILED

string

Allowed values: IMPORTING IMPORTED FAILED

summary

required

The handler’s own account of what it imported, or for FAILED the reason it gave; up to 2,000 characters, empty while importing

string

Example

[
  {
    "state": "IMPORTING"
  }
]