> ## Documentation Index > Fetch the complete documentation index at: https://bavlio.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get Starter Templates > Return starter email templates that read as the CALLER's business. Generated deterministically from the org's default sender profile so a customer sees copy selling their business to their ICP, never Bavlio's. When the org has no usable sender profile, returns generic industry-neutral copy that names no company. Strictly org-scoped: the sender profile is fetched via the org's default accessor, so one org can never see another's copy. ## OpenAPI ````yaml https://api.bavlio.com/openapi.json get /api/v1/templates/starter openapi: 3.1.0 info: title: Bavlio API description: >- Outreach automation API — lead enrichment, email campaigns, LinkedIn automation, and AI agent. Full docs at https://docs.bavlio.com. version: 1.0.0 x-guidance: product: Bavlio Data API protocols: - x402 description: >- Pay-per-call B2B data endpoints for AI agents. USDC on Base mainnet via x402 v2. See /openapi.json for pricing. Landing page + marketing details: https://bavlio.com/developers network: eip155:8453 docs_url: https://docs.bavlio.com x-payment-merchant-address: '0xcca4725e0e931982830bff523b141e1a7a58d3e7' servers: [] security: [] tags: - name: API Keys description: >- Create, list, and revoke API keys for programmatic access. JWT authentication required. - name: credits description: Credit balance, cost estimates, and transaction history. - name: campaigns description: Create, manage, launch, and monitor email campaigns. - name: campaign-personalization description: AI-powered email subject and body personalization for campaigns. - name: email-finder description: Find and verify email addresses for prospects. - name: sender-profiles description: Manage sender identity profiles for outreach. - name: sender-profile-chat description: Interactive chat for building sender profiles. - name: templates description: Email template CRUD. - name: suppression description: Do-not-contact suppression list management. - name: datasets description: Lead dataset listing, download, and updates. - name: user-extractions description: Uploaded lead file management and processing. - name: enrichment-chat description: Interactive chat for data enrichment sessions. - name: enrichment-processing description: Batch lead enrichment processing. - name: File Upload (CSV/Excel) description: Upload and preview CSV/Excel lead files. - name: connected-accounts description: LinkedIn account connections via Unipile. - name: linkedin-content description: LinkedIn post creation, scheduling, and management. - name: linkedin-playground description: Direct LinkedIn actions (profile lookup, messaging, engagement). - name: bavimail-proxy description: BaviMail domain, alias, and email management. - name: agent description: Bavi AI agent chat with SSE streaming. - name: notifications description: Notification preferences and delivery. - name: referral description: Referral code management and stats. - name: feedback description: User feedback submission. - name: authentication description: JWT token verification and user info. - name: users description: User quota and usage information. - name: Health description: Health checks and system status. - name: Personalization description: Core lead personalization engine. - name: Session Management description: Enrichment session lifecycle. - name: Session Processing description: Session data processing. - name: webhooks description: Inbound webhook handlers (Stripe, BaviMail, Unipile). paths: /api/v1/templates/starter: get: tags: - templates summary: Get Starter Templates description: >- Return starter email templates that read as the CALLER's business. Generated deterministically from the org's default sender profile so a customer sees copy selling their business to their ICP, never Bavlio's. When the org has no usable sender profile, returns generic industry-neutral copy that names no company. Strictly org-scoped: the sender profile is fetched via the org's default accessor, so one org can never see another's copy. operationId: get_starter_templates_api_v1_templates_starter_get responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/StarterTemplatesResponse' '401': description: Unauthorized - Invalid or missing JWT token '404': description: Template not found security: - HTTPBearer: [] components: schemas: StarterTemplatesResponse: properties: templates: items: $ref: '#/components/schemas/StarterTemplate' type: array title: Templates description: Generated starter templates generated_from_profile: type: boolean title: Generated From Profile description: >- True when built from the org's sender profile; False = generic fallback type: object required: - templates - generated_from_profile title: StarterTemplatesResponse description: Starter templates generated from the org's default sender profile. StarterTemplate: properties: id: type: string title: Id description: 'Stable slug: intro | value | follow_up' name: type: string title: Name description: Display name subject: type: string title: Subject description: Subject line with {{merge}} tokens body: type: string title: Body description: Body with {{merge}} tokens type: object required: - id - name - subject - body title: StarterTemplate description: A single generated starter template (subject + body with merge tokens). securitySchemes: HTTPBearer: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.