# Get a Message by ID

## Get a message by id

> This method returns the message that matches the entered ID.

```json
{"openapi":"3.0.2","info":{"title":"Vault API","version":"80fbdca"},"tags":[],"security":[{"Ledger_API_Key":[],"Ledger_API_User":[]},{"Ledger_API_Key":[],"Ledger_API_User":[],"Ledger_Store_Auth_Token":[]},{"Ledger_API_User":[]},{"Ledger_API_User":[],"Ledger_Store_Auth_Token":[]}],"components":{"securitySchemes":{"Ledger_API_Key":{"description":"If you've set up your API Key when initializing your LAM, you'll need to include it as a header along with the api user header. For more details, [see step 5 of the get started documentation](https://help.vault.ledger.com/Content/api/api_getstarted.html).","in":"header","name":"X-Ledger-API-Key","type":"apiKey"},"Ledger_API_User":{"description":"(**required**) Username of a registered API User","in":"header","name":"X-Ledger-API-User","type":"apiKey"}},"schemas":{"Message":{"additionalProperties":false,"properties":{"account_id":{"type":"integer"},"address":{"default":null,"description":"The address used to signed the message","nullable":true,"type":"string"},"created_by":{"type":"integer"},"created_on":{"format":"date-time","type":"string"},"data":{"description":"The content of the message","type":"string"},"id":{"type":"integer"},"last_request":{"default":null,"nullable":true,"type":"integer"},"message_type":{"description":"The type of the message","enum":["EIP-191","EIP-712"]},"notes":{"description":"Notes attached to this message","items":{"$ref":"#/components/schemas/TransactionOrMessageNote"},"type":"array"},"signature":{"default":null,"description":"The DER signature of the message","nullable":true,"type":"string"},"status":{"enum":["ABORTED","APPROVED","PENDING_APPROVAL","PENDING_CREATE_IN_HSM","SIGNED"],"type":"string"},"type":{"default":"MESSAGE_SIGNATURE"}},"required":["account_id","created_by","created_on","data","id","message_type","notes","status"],"type":"object"},"TransactionOrMessageNote":{"properties":{"content":{"type":"string"},"title":{"type":"string"}},"required":["content","title"],"type":"object"},"Error":{"properties":{"message":{"type":"string"},"name":{"type":"string"},"status_code":{"type":"integer"}},"required":["message","name","status_code"],"type":"object"}}},"paths":{"/messages/{message_id}":{"get":{"summary":"Get a message by id","tags":["Messages"],"description":"This method returns the message that matches the entered ID.","parameters":[{"name":"message_id","in":"path","description":"The message's ID.","required":true,"schema":{"type":"integer"}}],"responses":{"200":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/Message"}}},"description":"Message object"},"404":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}},"description":"Message not found"}}}}}}
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.enterprise.ledger.com/api-documentation/reference/api-reference/messages/get-a-message-by-id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.