> ## Documentation Index > Fetch the complete documentation index at: https://developer.lemlist.com/llms.txt > Use this file to discover all available pages before exploring further. > Returns one library message template with its body. # Get Message Template export const SnippetObjectReference = ({objectName, objectPath = null}) => { const lowerCaseObjectName = objectName.toLowerCase(); if (lowerCaseObjectName === 'lead' || lowerCaseObjectName === 'leads') { return This endpoint uses the {objectName} object. Make sure to also check the {lowerCaseObjectName === 'lead' ? 'Contact' : 'Lead'} object to understand the distinction between the two. ; } return This endpoint uses the {objectName} object. ; }; The body is HTML as stored, with `{{variables}}` left raw: keep them as they are when reusing the template in a step. A deleted template, another workspace's template and a campaign step body all answer `404 EMAIL_TEMPLATE_NOT_FOUND`: only the team library is readable here. ## OpenAPI ````yaml get /message-templates/{templateId} openapi: 3.0.0 info: title: lemlist API version: 1.0.0 description: >- Welcome to the lemlist Developer Documentation. lemlist is very customizable and open. You'll find on this page all the API and integration you can do with lemlist. # Rate Limit lemlist's API rate limits requests in order to prevent abuse and overload of our services. Rate limits are applied on all routes and per API key performing the request. The rate limits are **20** requests per **2** seconds. The response provides any information you may need about it: | Header | Description | | --- | --- | | Retry-After | The number of seconds in which you can retry | | X-RateLimit-Limit | The maximum requests in that time | | X-RateLimit-Remaining | The number of remaining requests you can make | | X-RateLimit-Reset | The date when the rate limit will reset | _Example of values for the rate limit headers_ ``` json { "Retry-After": 2, "X-RateLimit-Limit": 20, "X-RateLimit-Remaining": 7, "X-RateLimit-Reset" : "Tue Feb 16 2021 09:02:42 GMT+0100 (Central European Standard Time)" } ``` # Definitions ## Team A team is the entity of lemlist that can handle users and billing. ## Credits Credits are the coins a team uses to enrich emails, LinkedIn URLs, etc. via the enrich route. Each enrichment feature needs a certain amount of credits to run. ## User You use a user account to connect to lemlist and send messages via the connected emails or LinkedIn account. ## Campaign A campaign is the entity to automate outreach. A campaign has multiple sequences composed of steps. ## Lead A lead is a person that you try to contact via a campaign. ## Activity An activity is the history of all the steps. ## Unsubscribe An unsubscribe occurs when a person decides they don't want to receive emails from you anymore. # Authentication All API routes use the dedicated subdomain `api.lemlist.com`. lemlist uses API keys to allow access to the API. You can get your lemlist API key at our [integration page](https://app.lemlist.com/settings/integrations). You need to add the `Authorization` header using the `Basic` authentication type. `login:password` **where the login is always empty and the password is the API key**. ⚠️ **Don't forget to add the semicolon (**`:`**) before your API key in curl command.** > To authorize, use this code: ``` shell curl https://api.lemlist.com/api/team \ --user ":YourApiKey" ``` **Make sure to replace** **`YourApiKey`** **with your API key.** # Give feedback If you want to report a bug, ask for data, or share with us a use case, please fill this [form](https://lemlist.typeform.com/to/mfVlkyGf). It will help us centralize your needs! servers: - url: https://api.lemlist.com/api security: - basicAuth: [] paths: /message-templates/{templateId}: parameters: - name: templateId in: path required: true description: >- The unique identifier of the message template, from GET /message-templates example: etp_A1B2C3D4E5F6G7H8I schema: type: string get: tags: - Message templates summary: Get Message Template description: Returns one library message template with its body. parameters: [] responses: '200': description: The message template content: application/json: schema: $ref: '#/components/schemas/MessageTemplate' example: _id: etp_A1B2C3D4E5F6G7H8I name: Follow-up after demo subject: Next steps message:

Hi {{firstName}},

Thanks for your time yesterday.

cc: [] tags: - follow-up createdBy: usr_A1B2C3D4E5F6G7H8I createdAt: '2026-09-01T10:00:00.000Z' '400': description: >- `VALIDATION_ERROR` - a filter cap or a bad `page` / `limit` or a malformed `templateId` (`WRONG_PARAM_ID`) (JSON body), or no API key was supplied (plain text). content: application/json: example: error: Validation error code: VALIDATION_ERROR text/plain: example: no api key provided '401': description: >- Unauthorized - invalid or missing API key (plain text), or an API key with no linked user (JSON body carrying `ROUTE_UNAUTHORIZED`). content: text/plain: example: The authentication you supplied is incorrect application/json: example: error: Route unauthorized code: ROUTE_UNAUTHORIZED '404': description: >- `EMAIL_TEMPLATE_NOT_FOUND` - the template does not exist in this workspace's library. A deleted template, another workspace's template and a campaign step body all answer this. content: application/json: example: error: Message template not found code: EMAIL_TEMPLATE_NOT_FOUND '405': description: Method not allowed - this endpoint only accepts GET '429': description: Rate limit exceeded - 20 requests per 2 seconds per API key components: schemas: MessageTemplate: type: object description: >- A library message template: a whole reusable message a user saved from the Templates page or an editor, usable as a step on any channel. Bodies are HTML as stored, with `{{variables}}` left raw. properties: _id: type: string description: Template identifier (`etp_`) name: type: string description: Name shown on the Templates page subject: type: string description: Subject line; `""` when none was set message: type: string description: HTML body, variables left as `{{variable}}` cc: type: array items: type: string description: CC addresses; `[]` when none was set tags: type: array items: type: string description: Tags, trimmed and lowercased; `[]` when none was set createdBy: type: string description: Creator user id (`usr_`), see GET /team/members createdAt: type: string format: date-time description: Creation date example: _id: etp_A1B2C3D4E5F6G7H8I name: Follow-up after demo subject: Next steps message:

Hi {{firstName}},

Thanks for your time yesterday.

cc: [] tags: - follow-up createdBy: usr_A1B2C3D4E5F6G7H8I createdAt: '2026-09-01T10:00:00.000Z' securitySchemes: basicAuth: type: http scheme: basic ````