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
Veterans Affairs

Veterans Affairs Messaging API

The Messaging API from Veterans Affairs — 20 operation(s) for messaging.

Documentation Provider Profile APIs.io OpenAPI GitHub

Veterans Affairs Messaging API is one of 25 APIs that Veterans Affairs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 24 operations across 20 paths. It is described by OpenAPI 3.0.0, at version v0.

Requests are made against 2 base URLs: https://sandbox-api.va.gov/services/appeals/appealable-issues/{version}, https://api.va.gov/services/appeals/appealable-issues/{version}.

24 operations 20 paths 0 schemas 1 DELETE11 GET2 PATCH8 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v0
Base URL
https://api.va.gov/services/benefits-intake/v2
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0
Contact
developer.va.gov
Resource Areas
1

Authentication & Security 3

Veterans Affairs Messaging API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer_token). It supports OAuth 2.0 (productionOauth) using the authorizationCode and clientCredentials flows, exposing 6 scopes. It supports OAuth 2.0 (sandboxOauth) using the authorizationCode and clientCredentials flows, exposing 6 scopes.

  • productionOauth — The authentication model for the Appealable Issues API uses OAuth 2.0/OpenID Connect. The following authorization models are supported: [Authorization code flo…
  • sandboxOauth — The authentication model for the Appealable Issues API uses OAuth 2.0/OpenID Connect. The following authorization models are supported: [Authorization code flo…

Paths & Operations 24

Across 20 paths, the API surfaces 24 operations — 1 DELETE, 11 GET, 2 PATCH, 8 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Messaging 24
GET
/v1/messaging/folders
/v1/messaging/folders
get_folders → 200401403
GET
/v1/messaging/folders/{id}
/v1/messaging/folders/{id}
get_folder → 200401403
PUT
/v1/messaging/folders/{id}
/v1/messaging/folders/{id}
post_rename_folder body → 201401403
GET
/v1/messaging/folders/{id}/threads
/v1/messaging/folders/{id}/threads
get_folder_threads 6 params → 200401403
POST
/v1/messaging/folders/{id}/search
/v1/messaging/folders/{id}/search
search_folder 3 params body → 200401403
POST
/v1/messaging/message_drafts
/v1/messaging/messagedrafts
post_create_message_draft 1 param body → 201401403
PUT
/v1/messaging/message_drafts/{id}
/v1/messaging/messagedrafts/{id}
post_create_message_draft 2 params body → 204401403
POST
/v1/messaging/message_drafts/{reply_id}/replydraft
/v1/messaging/messagedrafts/{replyid}/replydraft
post_create_message_draft_reply 2 params body → 201401403
POST
/v1/messaging/message_drafts/{reply_id}/replydraft/{draft_id}
/v1/messaging/messagedrafts/{replyid}/replydraft/{draftid}
post_create_message_draft_reply 3 params body → 204401403
POST
/v1/messaging/messages
/v1/messaging/messages
post_create_message 2 params body → 200400401403422
GET
/v1/messaging/messages/categories
/v1/messaging/messages/categories
get_categories 1 param → 200401403
GET
/v1/messaging/messages/oh_sync_status
/v1/messaging/messages/ohsyncstatus
get_oh_sync_status 1 param → 200401403502
DELETE
/v1/messaging/messages/{id}
/v1/messaging/messages/{id}
delete_message 2 params → 204400401403
GET
/v1/messaging/messages/{id}
/v1/messaging/messages/{id}
get_message 1 param → 200401403
PATCH
/v1/messaging/messages/{id}
/v1/messaging/messages/{id}/move
post_move_message 3 params → 204401403
GET
/v1/messaging/messages/{id}/attachments/{attachment_id}
/v1/messaging/messages/{id}/attachments/{attachmentid}
get_attachment 2 params → 200401403
POST
/v1/messaging/messages/{id}/reply
/v1/messaging/messages/{id}/reply
post_create_message_reply 3 params body → 200400401403422
GET
/v1/messaging/messages/{id}/thread
/v1/messaging/messages/{id}/thread
get_messages_for_thread 2 params → 200401403
GET
/v1/messaging/recipients
/v1/messaging/recipients
get_triage_teams 1 param → 200401403
GET
/v1/messaging/allrecipients
/v1/messaging/allrecipients
get_all_triage_teams → 200401403
PATCH
/v1/messaging/threads/{id}/move
/v1/messaging/threads/{id}/move
post_move_thread 3 params → 204401403
POST
/v1/messaging/preferences/recipients
/v1/messaging/preferences/recipients
update_triage_team_preferences body → 200401403
GET
/v1/messaging/preferences/signature
/v1/messaging/preferences/signature
get_signature 1 param → 200401403
POST
/v1/messaging/preferences/signature
/v1/messaging/preferences/signature
update_signature 1 param body → 200401403

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

va-messaging-api-openapi.yml Raw ↑

Other APIs Veterans Affairs publishes across the network.

Patient Health API (FHIR)
AE Profile APIs.io
Health Care Costs and Coverage API (FHIR)
AE Profile APIs.io
Appeals Status API
AE Profile APIs.io
Decision Reviews API
AE Profile APIs.io
VA Facilities API
AE Profile APIs.io
VA Forms API
AE Profile APIs.io
Veteran Verification API
AE Profile APIs.io
Direct Deposit Management API
AE Profile APIs.io
VA Letter Generator API
AE Profile APIs.io
Benefits Reference Data API
AE Profile APIs.io
Veterans Affairs Appealable Issues API
AE Profile APIs.io
Veterans Affairs Appeals Status API
AE Profile APIs.io
#Messaging
← Back to V APIs
API Details
ID
va:va-messaging-api
Base URL
https://api.va.gov/services/benefits-intake/v2
Docs
https://developer.va.gov/explore/api/benefits-intake
Provider
Veterans Affairs
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=va-messaging-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/va-messaging-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 Veterans Affairs Messaging 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.