> ## Documentation Index > Fetch the complete documentation index at: https://leadping.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get organization lead communication analytics > Returns current-organization analytics for lead communication, including event volume, response metrics, and date-range filtering. ## OpenAPI ````yaml /openapi.json get /analytics/my openapi: 3.1.1 info: title: Leadping API description: >- The Leadping API helps businesses capture and manage leads, automate follow-up, send SMS and MMS messages, place calls, track conversations, enforce contact suppression, and analyze communication workflows. Use this OpenAPI 3.1 contract to integrate lead sources, build organization tools, or generate a typed API client. Authenticate protected operations with a Leadping user access token or WorkOS organization API key. Lead intake operations also accept a Leadping source key. termsOfService: https://leadping.ai/docs/terms-of-service contact: name: Leadping Support url: https://leadping.ai/contact email: support@leadping.ai license: name: MIT url: https://opensource.org/licenses/MIT version: v1 summary: Lead management, messaging, calling, and automation API servers: - url: https://api.leadping.ai description: Production security: [] tags: - name: leadping.Api description: >- Agent-to-agent discovery and request handling for Leadping's supported AI agent integrations. - name: Analytics description: >- Provides lead, communication, conversion, and organization performance analytics. Use these endpoints to measure activity over time, compare outcomes, and power operational dashboards and reporting workflows. - name: Automations description: >- Manages automated lead follow-up workflows and their execution history. Use these endpoints to configure SMS automation steps, preview eligible leads, run workflows, and inspect individual automation executions. - name: BlogArticles description: >- Provides published Leadping blog content. Use these endpoints to list published articles and retrieve an individual article by its public slug. - name: Conversations description: >- Provides lead conversation timelines and inbox-oriented conversation views. Use these endpoints to list recent conversations and retrieve the cross-channel communication history associated with a lead. - name: Feedback description: >- Captures Leadping product feedback and supports administrative triage. Users can submit feedback, while authorized staff can search, inspect, classify, and update feedback throughout the review process. - name: Leads description: >- Manages lead intake, records, assignment, routing, and lifecycle operations. Use these endpoints to ingest leads from trusted sources, search and update lead records, manage ownership and tags, and archive or delete leads. - name: LeadStatusChanges description: >- Manages the auditable history of lead status transitions. Use these endpoints to change a lead's status, correct transition records, search status history, and export status activity for reporting. - name: LeadStatuses description: >- Manages the lead statuses used to classify and track leads throughout their lifecycle. Use these endpoints to list, create, update, and archive organization-specific lead statuses for consistent pipeline organization and reporting. - name: Notifications description: >- Manages user notifications, announcements, and push-notification installations. Use these endpoints to retrieve notification feeds and unread counts, update read state, and register or remove client push installations. - name: OutboundDelivery description: >- Reports outbound delivery pacing and sending capacity for the current organization. Use these endpoints to determine whether outbound communications can proceed and to understand active throttles, limits, or capacity constraints. - name: Sources description: >- Manages lead sources, intake credentials, routing defaults, and attribution. Use these endpoints to create and configure sources, search source records, inspect source activity, rotate intake access, and remove obsolete sources. - name: Suppressions description: >- Manages recipient suppression state for compliant Leadping communication workflows. Use these endpoints to check contact eligibility, record or release suppressions, and review suppression history before sending messages or placing calls. - name: Tags description: >- Manages organization-defined tags for categorizing and routing leads. Use these endpoints to list, create, update, and archive reusable tags that support lead filtering, automation, assignment, and reporting. - name: Users description: >- Manages the current Leadping user's profile, preferences, setup, and account workflows. Use these endpoints to retrieve and update user data, configure communication and compliance preferences, complete onboarding, manage plan-related actions, and request account operations. - name: Calls description: >- Manages outbound Leadping calls and active call-control workflows. Use these endpoints to initiate or cancel a call, retrieve call state, and transfer an active call within supported telephony flows. - name: PhoneNumbers description: >- Manages phone-number discovery, purchasing, assignment, configuration, and compliance. Use these endpoints to search available numbers, manage owned numbers and caller identity, configure messaging or voice behavior, and monitor registration and warmup state. - name: Sms description: >- Sends and manages SMS and MMS communications through Leadping. Use these endpoints to send messages, upload MMS media, and cancel eligible scheduled messages while preserving conversation and delivery tracking. - name: Telephony description: >- Provides shared authentication and bootstrap data for Leadping telephony clients. Use this endpoint to obtain the scoped credentials and configuration required to initialize supported calling experiences. - name: Organizations description: >- Manages Leadping organizations, memberships, invitations, settings, and API credentials. Use these endpoints to maintain organization profiles and branding, manage members and invitations, configure options, and issue or revoke organization API keys. - name: UserDataExports description: >- Creates and delivers user-requested exports of Leadping account data. Use these endpoints to request an export, monitor its preparation status, and download the completed archive through a time-limited redirect. - name: CallEvents description: >- Provides call event records for auditing, diagnostics, and reporting. Use these endpoints to search and inspect lifecycle events emitted as Leadping calls are initiated, connected, completed, or fail. - name: Events description: >- Provides a unified record of Leadping activity across communication channels. Use these endpoints to retrieve event timelines, search event history, inspect event details, and record supported application events. - name: SmsEvents description: >- Provides SMS and MMS event records for delivery tracking and diagnostics. Use these endpoints to search and inspect message lifecycle events, including outbound delivery updates and inbound messaging activity. - name: PaymentMethods description: >- Manages organization payment methods and billing invoices. Use these endpoints to add, confirm, inspect, and remove payment methods or retrieve invoices associated with the current organization's billing account. - name: Transactions description: >- Provides organization wallet and billing transaction records. Use these endpoints to search transaction history, inspect individual charges or credits, review transaction summaries, and issue administrative credits. - name: Usage description: >- Provides billable usage records for Leadping services. Use these endpoints to review messaging and calling consumption, inspect usage summaries, and reconcile provider activity for an organization. - name: Wallets description: >- Manages organization wallet balances, funding, and credit activity. Use these endpoints to inspect wallet state and history, configure wallet behavior, add funds, and record credits or adjustments. externalDocs: description: >- Leadping API documentation, authentication guide, concepts, and integration guidance. url: https://leadping.ai/docs/api-reference paths: /analytics/my: get: tags: - Analytics summary: Get organization lead communication analytics description: >- Returns current-organization analytics for lead communication, including event volume, response metrics, and date-range filtering. operationId: Analytics_GetCurrentOrganization parameters: - name: startAt in: query description: Optional inclusive start timestamp for the analytics period. schema: type: string format: date-time - name: endAt in: query description: Optional exclusive end timestamp for the analytics period. schema: type: string format: date-time - name: days in: query description: >- Optional number of recent days to include when explicit timestamps are not supplied. schema: type: - 'null' - integer format: int32 responses: '200': description: OK content: application/json: schema: allOf: - $ref: '#/components/schemas/CustomerAnalyticsResponse' description: >- Aggregates an organization's lead performance, response speed, communication usage, automation health, and activation insights. '400': description: The request was invalid or failed validation. content: application/problem+json: schema: allOf: - $ref: '#/components/schemas/ProblemDetails' description: >- Standard problem-details response containing machine-readable and human-readable information about an HTTP API error. example: type: about:blank title: Bad Request status: 400 detail: The request could not be completed. '401': description: Authentication credentials are missing or invalid. content: application/problem+json: schema: allOf: - $ref: '#/components/schemas/ProblemDetails' description: >- Standard problem-details response containing machine-readable and human-readable information about an HTTP API error. example: type: about:blank title: Unauthorized status: 401 detail: The request could not be completed. '403': description: >- The authenticated user or organization does not have permission to perform this operation. content: application/problem+json: schema: allOf: - $ref: '#/components/schemas/ProblemDetails' description: >- Standard problem-details response containing machine-readable and human-readable information about an HTTP API error. example: type: about:blank title: Forbidden status: 403 detail: The request could not be completed. '429': description: The API rate limit for this account or client has been exceeded. headers: Retry-After: description: Number of seconds to wait before retrying the request. schema: minimum: 0 type: integer format: int32 content: application/problem+json: schema: allOf: - $ref: '#/components/schemas/ProblemDetails' description: >- Standard problem-details response containing machine-readable and human-readable information about an HTTP API error. example: type: about:blank title: Too Many Requests status: 429 detail: The request could not be completed. security: - Bearer: [] components: schemas: CustomerAnalyticsResponse: type: object properties: range: allOf: - $ref: '#/components/schemas/AnalyticsDateRange' description: Range associated with this Leadping customer analytics. summary: allOf: - $ref: '#/components/schemas/CustomerAnalyticsSummary' description: Human-readable summary for this Leadping customer analytics. leadTrend: allOf: - $ref: '#/components/schemas/CustomerLeadTrend' description: Lead trend associated with this Leadping customer analytics. responseMetrics: allOf: - $ref: '#/components/schemas/CustomerResponseMetrics' description: Response metrics associated with this Leadping customer analytics. communicationUsage: allOf: - $ref: '#/components/schemas/CustomerCommunicationUsage' description: >- Communication usage associated with this Leadping customer analytics. leadSources: type: array items: allOf: - $ref: '#/components/schemas/CustomerLeadSourceBreakdown' description: >- Attributes an organization's lead volume, qualification, and conversion outcomes to a specific acquisition source. description: >- Collection of lead sources included with this Leadping customer analytics. automationHealth: allOf: - $ref: '#/components/schemas/CustomerAutomationHealth' description: Automation health associated with this Leadping customer analytics. activationHealth: allOf: - $ref: '#/components/schemas/CustomerActivationHealth' description: Activation health associated with this Leadping customer analytics. needsAttention: type: array items: allOf: - $ref: '#/components/schemas/CustomerNeedsAttentionItem' description: >- Identifies an organization-level issue or opportunity and provides severity, supporting context, and a recommended action. description: >- Date and time when this Leadping customer analytics was needs attention. generatedAt: type: string description: Date and time when this Leadping customer analytics was generated. format: date-time description: >- Aggregates an organization's lead performance, response speed, communication usage, automation health, and activation insights. ProblemDetails: type: object properties: type: type: - 'null' - string description: URI reference that identifies the problem type. title: type: - 'null' - string description: Short, human-readable summary of the problem. status: type: - 'null' - integer description: HTTP status code returned for the problem. format: int32 detail: type: - 'null' - string description: >- Human-readable explanation specific to this occurrence of the problem. instance: type: - 'null' - string description: >- URI reference that identifies this specific occurrence of the problem. errors: type: object additionalProperties: type: array items: type: string description: >- Validation errors keyed by the JSON request field name. Present for request validation failures. traceId: type: string description: >- Request trace identifier used to correlate this problem with Leadping diagnostics. description: >- Standard problem-details response containing machine-readable and human-readable information about an HTTP API error. AnalyticsDateRange: type: object properties: startAt: type: string description: Date and time when this Leadping analytics date range was start. format: date-time endAt: type: string description: Date and time when this Leadping analytics date range was end. format: date-time bucketSize: allOf: - $ref: '#/components/schemas/AnalyticsBucketSize' description: Bucket size associated with this Leadping analytics date range. description: >- Defines the inclusive reporting window and comparison window used to calculate Leadping analytics. CustomerAnalyticsSummary: type: object properties: leads: type: integer description: >- Number of leads represented by this Leadping customer analytics summary. format: int32 leadsComparison: allOf: - $ref: '#/components/schemas/AnalyticsComparison' description: >- Date and time when this Leadping customer analytics summary was leads comparison. averageResponseMinutes: type: - 'null' - number description: Average time, in minutes, before a lead receives a response. format: double medianResponseMinutes: type: - 'null' - number description: Median response minutes measured in minutes. format: double respondedWithinFiveMinutesPercent: type: number description: Responded within five minutes percent expressed as a percentage. format: double missedLeads: type: integer description: >- Number of missed leads represented by this Leadping customer analytics summary. format: int32 unreadMessages: type: integer description: >- Number of unread messages represented by this Leadping customer analytics summary. format: int32 missedCalls: type: integer description: Number of calls missed during the reporting period. format: int32 smsSent: type: integer description: Number of SMS messages sent during the reporting period. format: int32 smsReceived: type: integer description: Number of SMS messages received during the reporting period. format: int32 callsPlaced: type: integer description: Number of outbound calls placed during the reporting period. format: int32 callsReceived: type: integer description: Number of inbound calls received during the reporting period. format: int32 callMinutes: type: number description: >- Total connected call duration, in minutes, during the reporting period. format: double usageSpend: type: number description: Usage spend represented by this Leadping customer analytics summary. format: double walletBalance: type: number description: >- Wallet balance represented by this Leadping customer analytics summary. format: double billingStatus: type: string description: Current billing status for this Leadping customer analytics summary. walletStatus: type: string description: Current wallet status for this Leadping customer analytics summary. description: >- Summarizes an organization's primary lead, response, communication, and conversion KPIs for the selected period. CustomerLeadTrend: type: object properties: total: type: integer description: >- Total number of total records represented by this Leadping customer lead trend. format: int32 totalErrors: type: integer description: Total number of lead submissions rejected during intake. format: int32 comparison: allOf: - $ref: '#/components/schemas/AnalyticsComparison' description: Date and time when this Leadping customer lead trend was comparison. points: type: array items: allOf: - $ref: '#/components/schemas/AnalyticsTrendPointOfint' description: >- Associates a typed analytics value with one normalized time bucket in a trend series. description: >- Collection of points included with this Leadping customer lead trend. errorPoints: type: array items: allOf: - $ref: '#/components/schemas/AnalyticsTrendPointOfint' description: >- Associates a typed analytics value with one normalized time bucket in a trend series. description: >- Lead intake errors grouped into the same reporting buckets as Points. description: >- Measures lead creation, qualification, and conversion activity within one reporting time bucket. CustomerResponseMetrics: type: object properties: averageMinutes: type: - 'null' - number description: Average minutes measured in minutes. format: double medianMinutes: type: - 'null' - number description: Median minutes measured in minutes. format: double respondedWithinFiveMinutesPercent: type: number description: Responded within five minutes percent expressed as a percentage. format: double respondedLeads: type: integer description: >- Number of responded leads represented by this Leadping customer response metrics. format: int32 unrespondedLeads: type: integer description: >- Number of unresponded leads represented by this Leadping customer response metrics. format: int32 unreadMessages: type: integer description: >- Number of unread messages represented by this Leadping customer response metrics. format: int32 missedCalls: type: integer description: Number of calls missed during the reporting period. format: int32 averageMinutesTrend: type: array items: allOf: - $ref: '#/components/schemas/AnalyticsTrendPointOfdecimal' description: >- Associates a typed analytics value with one normalized time bucket in a trend series. description: >- Collection of average minutes trend included with this Leadping customer response metrics. description: >- Measures how quickly and consistently an organization responds to leads across supported communication channels. CustomerCommunicationUsage: type: object properties: smsSent: type: integer description: Number of SMS messages sent during the reporting period. format: int32 smsReceived: type: integer description: Number of SMS messages received during the reporting period. format: int32 failedOrBlockedSms: type: integer description: >- Number of SMS messages that failed or were blocked during the reporting period. format: int32 callsPlaced: type: integer description: Number of outbound calls placed during the reporting period. format: int32 callsReceived: type: integer description: Number of inbound calls received during the reporting period. format: int32 callErrors: type: integer description: >- Number of calls that failed or were blocked during the reporting period. format: int32 answeredCalls: type: integer description: Number of calls answered during the reporting period. format: int32 missedCalls: type: integer description: Number of calls missed during the reporting period. format: int32 callMinutes: type: number description: >- Total connected call duration, in minutes, during the reporting period. format: double usageSpend: type: number description: >- Usage spend represented by this Leadping customer communication usage. format: double trend: type: array items: allOf: - $ref: '#/components/schemas/CustomerCommunicationUsagePoint' description: >- Measures organization messaging and calling activity within one analytics time bucket. description: >- Collection of trend included with this Leadping customer communication usage. description: >- Aggregates an organization's SMS, MMS, and calling activity, delivery outcomes, and billable usage over time. CustomerLeadSourceBreakdown: type: object properties: source: type: string description: >- Source classification for this Leadping customer lead source breakdown. leads: type: integer description: >- Number of leads represented by this Leadping customer lead source breakdown. format: int32 percent: type: number description: Percent expressed as a percentage. format: double description: >- Attributes an organization's lead volume, qualification, and conversion outcomes to a specific acquisition source. CustomerAutomationHealth: type: object properties: automationCount: type: integer description: >- Total number of automation records represented by this Leadping customer automation health. format: int32 enabledCount: type: integer description: >- Total number of enabled records represented by this Leadping customer automation health. format: int32 executions: type: integer description: >- Number of executions represented by this Leadping customer automation health. format: int32 successCount: type: integer description: >- Total number of success records represented by this Leadping customer automation health. format: int32 failureCount: type: integer description: >- Total number of failure records represented by this Leadping customer automation health. format: int32 trend: type: array items: allOf: - $ref: '#/components/schemas/CustomerAutomationHealthPoint' description: >- Measures automation execution activity within one analytics time bucket. description: Automation execution activity over the reporting period. lastFailure: type: - 'null' - object allOf: - $ref: '#/components/schemas/CustomerFailingAutomation' description: >- Last failure associated with this Leadping customer automation health. failingAutomations: type: array items: allOf: - $ref: '#/components/schemas/CustomerFailingAutomation' description: >- Identifies an automation with recent execution failures and summarizes its affected leads and failure context. description: >- Collection of failing automations included with this Leadping customer automation health. description: >- Summarizes automation coverage, execution success, failures, and workflows requiring organization attention. CustomerActivationHealth: type: object properties: overallStatus: type: string description: Current overall status for this Leadping customer activation health. items: type: array items: allOf: - $ref: '#/components/schemas/CustomerActivationHealthItem' description: >- Describes the state, severity, and recommended next action for one organization activation requirement. description: >- Collection of items included with this Leadping customer activation health. description: >- Summarizes an organization's progress and blockers across onboarding, billing, telephony, compliance, and launch readiness. CustomerNeedsAttentionItem: type: object properties: severity: type: string description: >- Severity associated with this Leadping customer needs attention item. title: type: string description: >- Human-readable title for this Leadping customer needs attention item. detail: type: string description: >- Human-readable detail for this Leadping customer needs attention item. actionHref: type: - 'null' - string description: Relative URL for the recommended follow-up action. actionText: type: - 'null' - string description: >- Action text associated with this Leadping customer needs attention item. description: >- Identifies an organization-level issue or opportunity and provides severity, supporting context, and a recommended action. AnalyticsBucketSize: enum: - 3 - 0 - 1 - 2 type: integer description: >- Selects the time interval used to aggregate points in a Leadping analytics trend series. format: int32 AnalyticsComparison: type: object properties: current: type: number description: Metric value for the current reporting period. format: double previous: type: number description: Metric value for the preceding comparison period. format: double changePercent: type: - 'null' - number description: >- Percentage change between the current and previous reporting periods. format: double direction: type: string description: Direction classification for this Leadping analytics comparison. description: >- Compares a metric with the preceding period and reports its absolute and percentage change. AnalyticsTrendPointOfint: type: object properties: startAt: type: string description: Date and time when this Leadping analytics trend point was start. format: date-time endAt: type: string description: Date and time when this Leadping analytics trend point was end. format: date-time label: type: string description: Human-readable label for this Leadping analytics trend point. value: type: integer description: Value associated with this Leadping analytics trend point. format: int32 description: >- Associates a typed analytics value with one normalized time bucket in a trend series. AnalyticsTrendPointOfdecimal: type: object properties: startAt: type: string description: Date and time when this Leadping analytics trend point was start. format: date-time endAt: type: string description: Date and time when this Leadping analytics trend point was end. format: date-time label: type: string description: Human-readable label for this Leadping analytics trend point. value: type: number description: Value associated with this Leadping analytics trend point. format: double description: >- Associates a typed analytics value with one normalized time bucket in a trend series. CustomerCommunicationUsagePoint: type: object properties: startAt: type: string description: >- Date and time when this Leadping customer communication usage point was start. format: date-time endAt: type: string description: >- Date and time when this Leadping customer communication usage point was end. format: date-time label: type: string description: >- Human-readable label for this Leadping customer communication usage point. smsSent: type: integer description: Number of SMS messages sent during the reporting period. format: int32 smsReceived: type: integer description: Number of SMS messages received during the reporting period. format: int32 smsErrors: type: integer description: >- Number of SMS messages that failed or were blocked in this time bucket. format: int32 calls: type: integer description: >- Number of calls represented by this Leadping customer communication usage point. format: int32 callsPlaced: type: integer description: Number of outbound calls placed in this time bucket. format: int32 callsReceived: type: integer description: Number of inbound calls received in this time bucket. format: int32 callErrors: type: integer description: Number of calls that failed or were blocked in this time bucket. format: int32 callMinutes: type: number description: >- Total connected call duration, in minutes, during the reporting period. format: double spend: type: number description: >- Spend represented by this Leadping customer communication usage point. format: double description: >- Measures organization messaging and calling activity within one analytics time bucket. CustomerAutomationHealthPoint: type: object properties: startAt: type: string description: Gets or sets the start at. format: date-time endAt: type: string description: Gets or sets the end at. format: date-time label: type: string description: Gets or sets the label. executions: type: integer description: Gets or sets the executions. format: int32 successCount: type: integer description: Gets or sets the success count. format: int32 failureCount: type: integer description: Gets or sets the failure count. format: int32 description: Measures automation execution activity within one analytics time bucket. CustomerFailingAutomation: type: object properties: automationId: type: - 'null' - string description: >- Unique identifier of the automation associated with this Leadping customer failing automation. name: type: string description: Human-readable name of the customer failing automation. failedAt: type: - 'null' - string description: Date and time when the customer failing automation failed. format: date-time error: type: - 'null' - string description: Error associated with this Leadping customer failing automation. description: >- Identifies an automation with recent execution failures and summarizes its affected leads and failure context. CustomerActivationHealthItem: type: object properties: key: type: string description: Key associated with this Leadping customer activation health item. label: type: string description: >- Human-readable label for this Leadping customer activation health item. status: type: string description: Current status for this Leadping customer activation health item. detail: type: string description: >- Human-readable detail for this Leadping customer activation health item. actionHref: type: - 'null' - string description: Relative URL for the recommended follow-up action. description: >- Describes the state, severity, and recommended next action for one organization activation requirement. securitySchemes: Bearer: type: http description: >- Authorization header using the Bearer scheme. Accepted values are Leadping user JWT access tokens and WorkOS organization API keys beginning with sk_. scheme: bearer bearerFormat: JWT or organization API key ````