> For the complete documentation index, see [llms.txt](https://docs.tagshelf.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tagshelf.dev/event-api/fileevents/file-extracted-data-create.md).

# File Extracted Data Create

### Usage

This file event triggers when a file has completed obtains the information from the file based on some parameters, once all the parameters are complete, it will extract the information to pass it to text.

Once in our system, this file will be classified, indexed and the configured data points of its labels will be extracted.

### JSON Payload

```json
{
  "event_id": "(UUID format) - Unique identifier for the event.",
  "event_type": "Describes the type of event that occurred.",
  "event_time": "(floating-point numeric timestamp) - Unix timestamp representing the time when the event occurred, including tenths of a second.",
  "event": {
    "event_name": "Name of the specific event.",
    "event_type": "Type of the event, often matching or related to the outer event_type.",
    "company_id": "(UUID format) - Unique identifier for the company involved in the event.",
    "company_name": "Name of the company involved in the event.",
    "file_log_id": "(UUID format) - Unique identifier for the log entry related to the file event.",
    "content": "Text - Extracted textual content or data from the file.",
    "provider": "Name of the service provider that performed the data extraction.",
    "creation_date": "(ISO 8601 date format) - Date and time when the extracted data was initially created.",
    "update_date": "(ISO 8601 date format) - Date and time when the extracted data or event log was last updated."
  }
}
```

```bash
{
  "event_id": "mnop4567-qr89-0123-st45-uvwxy6789012",
  "event_type": "file_event_type",
  "event_time": "1651325678.10",
  "event": {
    "event_name": "file_extracted_data_create_event",
    "event_type": "file_event_type",
    "company_id": "678m7891-n23o-67h8-f012-548614182000",
    "company_name": "TechAdventures",
    "file_log_id": "456n9012-o34p-78i9-j123-659314183000",
    "content": "Extracted text content or data from the document...",
    "provider": "DataExtractionService",
    "creation_date": "2023-05-03T10:15:00Z",
    "update_date": "2023-05-04T12:20:00Z"
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tagshelf.dev/event-api/fileevents/file-extracted-data-create.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.