How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Vaquill AI

Vaquill AI Chronology API

The dated events across a matter's documents, as one timeline, with duplicate and date-conflict flags.

Documentation Provider Profile APIs.io OpenAPI GitHub

Vaquill AI Chronology API is one of 26 APIs that Vaquill AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 18 JSON Schema definitions.

Tagged areas include Chronology. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a changelog, and 18 JSON Schemas.

This API exposes 6 operations across 4 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.vaquill.ai/workspace, /workspace.

6 operations 4 paths 12 schemas 1 DELETE2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.vaquill.ai/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Vaquill AI Chronology API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (vq_ws_*) (WorkspaceAuth). By default, every request must be authenticated.

  • WorkspaceAuth — Workspace credential issued from the automation console at /automation. Send it as Authorization: Bearer vqws.... This is NOT a Data API key: a vqkey credentia…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Chronology 6

The dated events across a matter's documents, as one timeline, with duplicate and date-conflict flags.

GET
/v1/matters/{matterId}/chronology/events
List chronology events
chronologyEvents.list 16 params → 200422401403404429500503
POST
/v1/matters/{matterId}/chronology/events
Create a chronology event
chronologyEvents.create 1 param body → 201422401403404429500503
PATCH
/v1/matters/{matterId}/chronology/events/{eventId}
Update a chronology event
chronologyEvents.update 2 params body → 200422401403404429500503
DELETE
/v1/matters/{matterId}/chronology/events/{eventId}
Delete a chronology event
chronologyEvents.delete 2 params → 204422401403404429500503
GET
/v1/matters/{matterId}/chronology/extraction-status
Get chronology extraction status
chronology.extractionStatus 1 param → 200422401403404429500503
POST
/v1/matters/{matterId}/chronology/exports
Export the chronology as CSV, PDF or DOCX
chronology.export 1 param body → 200422401403404429500503

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ChronologyEvent (21 properties), ChronologyEventCreateRequest (12 properties), ChronologyFilters (11 properties), ChronologyEventUpdateRequest (10 properties). Each schema is shown below with its type and property counts.

ChronologyEventCreateRequest
object
A hand-entered event. Created events are recorded as NOT ai-extracted and carry no confidence, which is what keeps them distinguishable from the pipeline's out…
12 properties 2 required
ChronologyExportRequest
object
A POST, because the filters live in the body. The export honours exactly the filters the list accepts, and it refuses rather than truncating: over the ceiling…
2 properties 1 required
ChronologyExtractionStatus
object
How far the automatic extraction has got across the whole matter.
6 properties 6 required
Pagination
object
Where the caller is, and whether there is more. total is the count of rows matching the filter, not the count returned, so a caller can size a job before runni…
4 properties 4 required
ValidationProblem
object
A problem document for a schema rejection. errors lists the fields that were refused. The value you submitted is deliberately not echoed, so a validation failu…
7 properties 6 required
ChronologyFilters
object
Which events to include. ONE model, two call sites: the list takes it as a query model and the export takes it as a field on its body. That is deliberate, and…
11 properties
Problem
object
An RFC 9457 problem document. Branch on type, which is stable; title and detail are written for people and may be reworded. Some problems carry extra members (…
6 properties 5 required
ChronologyEvent
object
One dated event on the matter's timeline.
21 properties 12 required
Page_ChronologyEvent_
object
2 properties 2 required
DocumentExtractionState
object
Where one document's chronology extraction got to.
4 properties 3 required
ChronologyEventUpdateRequest
object
Fields to change. Omitted fields are left alone. An explicit null clears description or eventDateEnd. Every other field here is backed by a NOT NULL column, so…
10 properties
ChronologyExport
object
A rendered timeline, returned as bytes rather than as a signed URL.
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vaquill-ai-chronology-api-openapi.yml Raw ↑

Other APIs Vaquill AI publishes across the network.

Vaquill AI Board Watches API
AE Profile APIs.io
Vaquill AI Clients API
AE Profile APIs.io
Vaquill AI Comparisons API
AE Profile APIs.io
Vaquill AI Compliance API
AE Profile APIs.io
Vaquill AI Credits API
AE Profile APIs.io
Vaquill AI Documents API
AE Profile APIs.io
Vaquill AI Drafting API
AE Profile APIs.io
Vaquill AI Facts API
AE Profile APIs.io
Vaquill AI Folders API
AE Profile APIs.io
Vaquill AI India Credits API
AE Profile APIs.io
Vaquill AI India Pricing API
AE Profile APIs.io
Vaquill AI Indian Acts and Legislation API
AE Profile APIs.io
#Chronology
← Back to V APIs
API Details
ID
vaquill-ai:vaquill-ai-chronology-api
Base URL
https://api.vaquill.ai/api/v1
Docs
https://www.vaquill.ai/legal-api
Provider
Vaquill AI
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=vaquill-ai-chronology-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vaquill-ai-chronology-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Vaquill AI Chronology API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.