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
LawVu

LawVu Emails API

The Emails API from LawVu — 5 operation(s) for emails.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Emails. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api-sandbox.lawvu.com/account-apis, https://api.lawvu.com/account-apis.

7 operations 5 paths 13 schemas 1 DELETE2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.lawvu.com
Resource Areas
1

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Emails 7
GET
/v1/emails/threads
Get an email thread
get-v1-emails-threads 2 params → 200
POST
/v1/emails/threads
Save email thread
post-v1-emails-threads body → 200
GET
/v1/emails/threads/page
Get email threads
get-v1-emails-threads-page 3 params → 200
POST
/v1/emails/drafts
Create email draft
post-v1-emails-drafts body → 200
DELETE
/v1/emails/drafts/{draftId}
Delete email draft
delete-v1-emails-drafts-draftid 1 param → 200
PUT
/v1/emails/drafts/{draftId}
Update email draft
put-v1-emails-drafts-draftid 1 param body → 200
POST
/v1/emails/threads/byExternalReferenceId
Check for any users tracking an email by External Reference ID
post-v1-emails-threads-byexternalreferenceid body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are EmailThread (15 properties), SaveEmailThread (6 properties), CreateMessageDraft (6 properties), MessageDraft (3 properties). Each schema is shown below with its type and property counts.

CrossUserEmailTrackingByExternalReferenceIdRequest
object
1 property
CrossUserEmailTracking
object
2 properties
UserEmailTrackingRecord
object
2 properties
CreateMessageDraft
object
6 properties
UserEmailTracking
object
3 properties
PagedEmailThread
object
2 properties
MessageDraftRecipient
object
1 property 1 required
SaveEmailThread
object
6 properties 2 required
EmailThreadArray
array
StringArray
array
EmailThread
object
15 properties
CrossUserEmailTrackingResponse
object
1 property
MessageDraft
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lawvu-emails-api-openapi.yml Raw ↑

Other APIs LawVu publishes across the network.

LawVu Auth API
AE Profile APIs.io
LawVu ContractFiles API
AE Profile APIs.io
LawVu ContractKeyDate API
AE Profile APIs.io
LawVu Contracts API
AE Profile APIs.io
LawVu ContractStatusMessage API
AE Profile APIs.io
LawVu ContractTemplates API
AE Profile APIs.io
LawVu ContractUser API
AE Profile APIs.io
LawVu Features API
AE Profile APIs.io
LawVu Fields API
AE Profile APIs.io
LawVu Files API
AE Profile APIs.io
LawVu Folders API
AE Profile APIs.io
LawVu Invoices API
AE Profile APIs.io
#Emails
← Back to L APIs
API Details
ID
lawvu:lawvu-emails-api
Base URL
https://api.lawvu.com
Docs
https://api-docs.lawvu.com/new-api/lawvuapi.openapi
Provider
LawVu
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=lawvu-emails-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lawvu-emails-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 LawVu Emails 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.