> ## 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 full lead event payload by ID > Returns detailed event data by ID, including the full JSON payload for debugging, audit review, and workflow inspection. ## OpenAPI ````yaml /openapi.json get /events/{eventId}/detail openapi: 3.0.4 info: title: Leadping API description: >- Leadping API for lead intake, messaging, calling, automations, billing, organization settings, and compliant lead communication workflows. license: name: MIT url: https://opensource.org/licenses/MIT version: v1 servers: - url: https://api.leadping.ai description: Production security: [] tags: - name: Analytics - name: Automations - name: Contact - name: Conversations - name: Feedback - name: Leads - name: LeadStatusChanges - name: LeadStatuses - name: Notifications - name: OutboundDelivery - name: Sources - name: Suppressions - name: Tags - name: Users - name: Calls - name: PhoneNumbers - name: Sms - name: Telephony - name: Organizations - name: UserDataExports - name: CallEvents - name: Events - name: SmsEvents - name: PaymentMethods - name: Transactions - name: Usage - name: Wallets paths: /events/{eventId}/detail: get: tags: - Events summary: Get full lead event payload by ID description: >- Returns detailed event data by ID, including the full JSON payload for debugging, audit review, and workflow inspection. operationId: Events_GetDetailById parameters: - name: eventId in: path description: The ID of the event. required: true schema: type: string responses: '200': description: Event details were successfully retrieved. content: application/json: schema: allOf: - $ref: '#/components/schemas/EventDetailResponse' description: >- Response schema for the Leadping API event detail response returned to authenticated clients. '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ProblemDetails' '404': description: Event was not found. content: application/json: schema: $ref: '#/components/schemas/ProblemDetails' components: schemas: EventDetailResponse: type: object properties: eventType: type: string description: >- Event type used to classify this timeline, SMS, call, or automation event. secondaryEventType: type: string description: Secondary event type used for additional event classification. nullable: true description: type: string description: >- Human-readable description that explains this event detail response to API users. nullable: true eventCategory: type: string description: High-level category used to group this Leadping event. nullable: true timelineType: enum: - Message - Sms - Mms - Call - Voicemail - Note - LeadStatusChange - LeadCreated - LeadUpdated - Notification - Payment - Warmup type: string description: Defines the supported Event timeline type values. nullable: true timelineCategory: type: string description: Timeline category used to group events for display and filtering. nullable: true conversationId: type: string description: >- Conversation ID that links this event detail response to the Leadping inbox thread. nullable: true summary: type: string description: >- Short human-readable summary of this event detail response for lists, timelines, and notifications. nullable: true direction: type: string description: >- Communication direction for this event detail response, such as inbound or outbound. nullable: true status: enum: - Pending - InProgress - Completed - Failed - Cancelled type: string description: Defines the supported Event status values. nullable: true statusReason: type: string description: >- Human-readable reason explaining the current status of this event detail response. nullable: true fromPhoneNumberId: type: string description: Sender phone number ID used for this outbound SMS or call. nullable: true outboundPhoneNumberId: type: string description: Phone number ID selected for outbound delivery. nullable: true fromPhoneNumber: type: string description: Sender phone number used for this communication. nullable: true toPhoneNumber: type: string description: Recipient phone number used for this communication. nullable: true queuedAt: type: string description: >- UTC timestamp when Leadping queued this event detail response for processing. format: date-time nullable: true scheduledFor: type: string description: >- UTC timestamp when the related delivery or workflow action is scheduled to run. format: date-time nullable: true sendingStartedAt: type: string description: UTC timestamp when Leadping began sending this message. format: date-time nullable: true sentAt: type: string description: UTC timestamp when Leadping sent this message to the provider. format: date-time nullable: true deliveredAt: type: string description: UTC timestamp when the provider confirmed delivery. format: date-time nullable: true receivedAt: type: string description: UTC timestamp when Leadping received this inbound event or message. format: date-time nullable: true failedAt: type: string description: UTC timestamp when processing failed for this event detail response. format: date-time nullable: true undeliverableAt: type: string description: UTC timestamp when the provider marked the message undeliverable. format: date-time nullable: true blockedAt: type: string description: UTC timestamp when Leadping blocked this communication. format: date-time nullable: true canceledAt: type: string description: UTC timestamp when this delivery or workflow was canceled. format: date-time nullable: true user: type: object allOf: - $ref: '#/components/schemas/IdNamePair' description: User summary connected to this event detail response. nullable: true userId: type: string description: User ID associated with the activity that created this event. leadId: type: string description: Lead ID associated with this event detail record. nullable: true id: type: string description: The unique identifier for the entity. createdAt: type: string description: The date and time when the entity was created. format: date-time modifiedAt: type: string description: The date and time when the entity was last modified, if applicable. format: date-time nullable: true description: >- Response schema for the Leadping API event detail response returned to authenticated clients. ProblemDetails: type: object properties: type: type: string description: URI reference that identifies the problem type. nullable: true title: type: string description: Short, human-readable summary of the problem. nullable: true status: pattern: ^-?(?:0|[1-9]\d*)$ description: HTTP status code returned for the problem. format: int32 detail: type: string description: >- Human-readable explanation specific to this occurrence of the problem. nullable: true instance: type: string description: >- URI reference that identifies this specific occurrence of the problem. nullable: true IdNamePair: required: - id - name type: object properties: id: type: string description: The unique identifier. name: type: string description: The display name. description: >- A minimal Record type with an (string), (string), and maximum JSON compatibility. The reason for this type (over something like KeyValuePair, dictionary) is because of JSON serialization support. ````