{"files":{"SKILL.md":"---\nname: amazon-workmail-message-flow\ndescription: \"Amazon WorkMail Message Flow API skill. Use when working with Amazon WorkMail Message Flow for messages. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Amazon WorkMail Message Flow\nAPI version: 2019-05-01\n\n## Auth\nAWS SigV4\n\n## Base URL\nNot specified.\n\n## Setup\n1. Configure auth: AWS SigV4\n2. GET /messages/{messageId} -- verify access\n3. POST /messages/{messageId} -- create first messages\n\n## Endpoints\n\n2 endpoints across 1 groups. See references/api-spec.lap for full details.\n\n### messages\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /messages/{messageId} | Retrieves the raw content of an in-transit email message, in MIME format. |\n| POST | /messages/{messageId} | Updates the raw content of an in-transit email message, in MIME format. This example describes how to update in-transit email message. For more information and examples for using this API, see  Updating message content with AWS Lambda.  Updates to an in-transit message only appear when you call PutRawMessageContent from an AWS Lambda function configured with a synchronous  Run Lambda rule. If you call PutRawMessageContent on a delivered or sent message, the message remains unchanged, even though GetRawMessageContent returns an updated message. |\n\n## Common Questions\n\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Get message details?\" -> GET /messages/{messageId}\n- \"How to authenticate?\" -> See Auth section\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Create/update endpoints typically return the created/updated object\n\n## CLI\n\n```bash\n# Update this spec to the latest version\nnpx @lap-platform/lapsh get amazon-workmail-message-flow -o references/api-spec.lap\n\n# Search for related APIs\nnpx @lap-platform/lapsh search amazon-workmail-message-flow\n```\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Amazon WorkMail Message Flow\n@version 2019-05-01\n@auth AWS SigV4\n@endpoints 2\n@toc messages(2)\n\n@endpoint GET /messages/{messageId}\n@desc Retrieves the raw content of an in-transit email message, in MIME format.\n@required {messageId: str}\n@returns(200) {messageContent: bytes}\n\n@endpoint POST /messages/{messageId}\n@desc Updates the raw content of an in-transit email message, in MIME format. This example describes how to update in-transit email message. For more information and examples for using this API, see  Updating message content with AWS Lambda.  Updates to an in-transit message only appear when you call PutRawMessageContent from an AWS Lambda function configured with a synchronous  Run Lambda rule. If you call PutRawMessageContent on a delivered or sent message, the message remains unchanged, even though GetRawMessageContent returns an updated message.\n@required {messageId: str, content: RawMessageContent}\n\n@end\n"}}