> ## Documentation Index > Fetch the complete documentation index at: https://docs.letterdrop.com/llms.txt > Use this file to discover all available pages before exploring further. # Get an account's CRM outreach > Your team's outreach to the account from your CRM: the outreach summary and attribution verdict, the timeline from signal to meeting and opportunity, outreach per contact, and the CRM activities themselves. ## OpenAPI ````yaml /openapi.json get /accounts/{account_id}/outreach openapi: 3.1.0 info: title: Letterdrop Competitor Monitoring API version: 2.0.0 license: name: Proprietary url: https://letterdrop.com/terms description: >- Read your workspace's Competitor Monitoring data: the accounts where people engaged your competitors, the contacts and signals behind each, their CRM context, your outreach, and the dashboard metrics. The API speaks the same language as the New Competitor Deal webhook (payload version v2): a field has the same name and the same values in both, so whatever you build on one reads the other. **Versioning.** The major version is in the path (/api/v2). Within v2 changes are additive only (new optional fields, filters, endpoints), so ignore fields you do not recognise. The v1 competitor-monitoring endpoints keep working unchanged. **Rate limits.** Per workspace: 10 requests/second and 600/minute, plus 20 uncached computations/minute (analytics count as 4). Cached reads (meta.cache = hit), including every later page of a list you already started, use no computation budget. Every response carries RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset; a 429 carries Retry-After. **Freshness.** Results are cached for a few minutes (analytics and filter options a little longer); meta.data_as_of says when the data was computed. Signals are collected daily, so polling faster than every few minutes returns the same data. servers: - url: https://api.letterdrop.com/api/v2 security: [] tags: - name: Accounts description: Companies with competitor signals, and what we know about each. - name: Contacts description: The people behind the signals. - name: Analytics description: The dashboard metrics, one endpoint each. - name: Filters description: Every key of every object, and how to select and filter on it. externalDocs: description: Developer reference url: https://api.letterdrop.com/api/v2/docs paths: /accounts/{account_id}/outreach: get: tags: - Accounts summary: Get an account's CRM outreach description: >- Your team's outreach to the account from your CRM: the outreach summary and attribution verdict, the timeline from signal to meeting and opportunity, outreach per contact, and the CRM activities themselves. operationId: getAccountOutreach parameters: - name: account_id in: path required: true description: The account_id of an account, URL-encoded (domain%3Aacme.com). schema: type: string - name: include in: query required: false description: contact_info adds contact emails to contact_activity and activities. schema: type: string - name: activity_limit in: query required: false description: CRM activities to return, newest first, 1-200. Default 50. schema: type: integer minimum: 1 maximum: 200 - name: fields in: query required: false description: Comma-separated top-level fields of data to return; omit for all. schema: type: string maxLength: 4000 responses: '200': description: OK content: application/json: schema: type: object required: - data - meta properties: data: $ref: '#/components/schemas/Outreach' meta: $ref: '#/components/schemas/Meta' example: data: account_id: domain:acme.com outreach_started: true outreach_any_replied: true outreach_in_market: true outreach_in_market_reason: >- Reply sentiment and meeting activity point to an active evaluation. outreach_summary: >- First touch four days after the signal; a meeting was booked a week later. outreach_lead_source: outbound outreach_attribution: direct_reply outreach_attribution_reason: >- The meeting was booked after Jane replied to the Oct 24 outreach. outreach_counts: outbound_emails: 2 inbound_emails: 1 calls: 0 dms: 0 meetings: 1 tasks: 0 page_visits: 0 marketing_opens: 3 form_submissions: 0 outreach_timeline: signal_date: '2026-10-20' first_outreach_after_signal_date: '2026-10-24' last_outreach_date: '2026-10-24' meeting_booked_date: '2026-10-30' opportunity_created_date: '' contact_activity: - contact_name: Jane Doe contact_job_title: VP Marketing crm_source: hubspot outreach_contacted: true outreach_replied: true outreach_contacted_by_name: Alex Owner outreach_contacted_by_email: alex@example.com outreach_last_outbound_at: '2026-10-24T12:15:00.000Z' outreach_last_reply_at: '2026-10-26T09:40:00.000Z' outreach_reply_classification: positive activities: - activity_type: meeting activity_at: '2026-10-30T16:30:00.000Z' crm_source: hubspot direction: '' subject: Discovery call snippet: 30 min discovery with marketing ops. owner_name: Alex Owner contact_name: Jane Doe outreach_attribution: direct_reply outreach_attribution_reason: Booked after Jane replied to the Oct 24 outreach. activity_total: 3 meta: api_version: '2' data_as_of: '2026-11-02T09:36:28.016Z' cache: hit '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/Unprocessable' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/ServerError' security: - WorkspaceKey: [] - BearerAuth: - mcp.read components: schemas: Outreach: type: object description: Your team's outreach to an account, from your CRM. x-field-groups: - Account - Outreach properties: account_id: type: string description: The account. x-group: Account outreach_started: type: boolean description: Anyone at the account has been contacted. x-group: Outreach outreach_any_replied: type: boolean description: Anyone at the account replied. x-group: Outreach outreach_in_market: type: boolean description: The CRM activity reads as an active evaluation. x-group: Outreach outreach_in_market_reason: type: string description: Why. x-group: Outreach outreach_summary: type: string description: A short summary of the outreach. x-group: Outreach outreach_lead_source: type: string description: Lead source category (outbound, inbound, …). x-group: Outreach outreach_attribution: type: string x-values: - direct_reply - driven - assisted - detected - competitive_deal - pending_analysis - none description: >- Our verdict on whether the signal led to the meeting or deal. Empty when we make no claim. x-group: Outreach outreach_attribution_reason: type: string description: Why. x-group: Outreach outreach_counts: type: object additionalProperties: true description: >- Activity counts: outbound_emails, inbound_emails, calls, dms, meetings, tasks, page_visits, marketing_opens, form_submissions. x-group: Outreach outreach_timeline: allOf: - $ref: '#/components/schemas/OutreachTimeline' description: The dates the table's mini timeline plots. x-group: Outreach contact_activity: type: array items: $ref: '#/components/schemas/ContactActivity' description: Outreach per CRM contact at the account. x-group: Outreach activities: type: array items: $ref: '#/components/schemas/Activity' description: CRM activities, newest first (up to activity_limit). x-group: Outreach activity_total: type: integer description: All CRM activities on the account. x-group: Outreach Meta: type: object required: - api_version - data_as_of - cache properties: api_version: type: string const: '2' data_as_of: type: string format: date-time description: >- When the data in this response was computed. Responses are cached for a few minutes; this tells you how fresh they are. cache: type: string enum: - hit - miss - shared - 'off' description: >- hit = served from cache; miss = computed for this request; shared = joined a computation already running for the same query. OutreachTimeline: type: object description: Signal to meeting to opportunity. x-field-groups: - Signal - CRM - Outreach properties: signal_date: type: string x-format: YYYY-MM-DD, or empty description: The account's first signal. x-group: Signal first_outreach_after_signal_date: type: string x-format: YYYY-MM-DD, or empty description: First outreach after it. x-group: Outreach last_outreach_date: type: string x-format: YYYY-MM-DD, or empty description: Latest outreach. x-group: Outreach meeting_booked_date: type: string x-format: YYYY-MM-DD, or empty description: First meeting booked after the signal. x-group: Outreach opportunity_created_date: type: string x-format: YYYY-MM-DD, or empty description: First opportunity created after the signal. x-group: CRM ContactActivity: type: object description: Outreach to one CRM contact. x-field-groups: - Contact - CRM - Outreach properties: contact_name: type: string description: The CRM contact. x-group: Contact contact_job_title: type: string description: Their job title. x-group: Contact contact_work_email: type: string description: Their CRM email. Only with include=contact_info. x-group: Contact crm_source: type: string description: The CRM the activity comes from (hubspot, salesforce). x-group: CRM outreach_contacted: type: boolean description: Your team reached out to them. x-group: Outreach outreach_replied: type: boolean description: They replied. x-group: Outreach outreach_contacted_by_name: type: string description: Who on your team reached out. x-group: Outreach outreach_contacted_by_email: type: string description: Their email. x-group: Outreach outreach_last_outbound_at: type: string x-format: date-time, or empty description: Latest outreach to them. x-group: Outreach outreach_last_reply_at: type: string x-format: date-time, or empty description: Their latest reply. x-group: Outreach outreach_reply_classification: type: string description: positive, neutral or negative. x-group: Outreach Activity: type: object description: One CRM activity. x-field-groups: - Contact - CRM - Outreach properties: activity_type: type: string description: email, call, meeting, task, … x-group: Outreach activity_at: type: string x-format: date-time, or empty description: When it happened. x-group: Outreach crm_source: type: string description: The CRM it comes from. x-group: CRM direction: type: string description: outbound or inbound, when the CRM records it. x-group: Outreach subject: type: string description: Subject line. x-group: Outreach snippet: type: string description: Opening of the body. x-group: Outreach owner_name: type: string description: Who on your team owns it. x-group: Outreach contact_name: type: string description: The contact it involves. x-group: Contact contact_work_email: type: string description: Their CRM email. Only with include=contact_info. x-group: Contact outreach_attribution: type: string x-values: - direct_reply - driven - assisted - detected - competitive_deal - pending_analysis - none description: 'For a meeting: our verdict on whether a signal led to it.' x-group: Outreach outreach_attribution_reason: type: string description: Why. x-group: Outreach Error: type: object required: - error properties: error: type: object required: - code - message properties: code: type: string enum: - invalid_request - invalid_json - invalid_cursor - cursor_expired - unauthorized - forbidden - account_not_found - not_found - rate_limited - internal_error message: type: string details: type: array items: type: object properties: path: type: string message: type: string description: 'For invalid_request: one entry per parameter that failed.' responses: Unauthorized: description: Missing or invalid credential. x-status: 401 x-codes: - unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: The credential lacks the mcp.read scope. x-status: 403 x-codes: - forbidden content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: No such account in this workspace, or no such route. x-status: 404 x-codes: - account_not_found - not_found content: application/json: schema: $ref: '#/components/schemas/Error' Unprocessable: description: A parameter failed validation; details lists each one. x-status: 422 x-codes: - invalid_request content: application/json: schema: $ref: '#/components/schemas/Error' TooManyRequests: description: Rate limited; wait Retry-After seconds. x-status: 429 x-codes: - rate_limited content: application/json: schema: $ref: '#/components/schemas/Error' headers: Retry-After: schema: type: integer description: Seconds to wait. ServerError: description: Our fault; retry, and contact support if it persists. x-status: 500 x-codes: - internal_error content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: WorkspaceKey: type: apiKey in: header name: api-key BearerAuth: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.