# Leadping

> Learn how to set up Leadping, send leads, automate responsible SMS and calls, authenticate API requests, use SDKs, and build lead workflows.

- [Welcome to Leadping](https://leadping.ai/docs/introduction.md): Learn how Leadping connects lead intake, consent evidence, conversations, automation, and outcomes in one traceable workflow.
- [Set Up Leadping](https://leadping.ai/docs/get-started.md): Set up your Leadping organization, complete onboarding, create a lead source, and test production intake with source-key authentication and TrustedForm.
- [Configure Lead Sources](https://leadping.ai/docs/lead-sources.md): Create and manage Leadping lead sources, securely use source keys for intake, monitor lead volume, and control access for forms, partners, and CRM systems.
- [Send Leads with the Intake API](https://leadping.ai/docs/sending-leads-to-leadping.md): Use a Leadping source key to submit structured or flat leads and handle validation and processing states.
- [Require TrustedForm for External Leads](https://leadping.ai/docs/requiring-trustedform.md): Submit a TrustedForm certificate URL with every external lead and understand Leadping validation states.
- [Operate a Responsible Lead Workflow](https://leadping.ai/docs/compliance.md): Keep lead source, TrustedForm evidence, sender identity, message purpose, timing, and recipient preferences aligned.
- [Understand Number health](https://leadping.ai/docs/trustedsetup.md): Understand Leadping phone-number readiness, messaging and calling availability, usage limits, and the optional Number health add-on for ongoing monitoring.
- [Let Leadping Handle A2P 10DLC Registration](https://leadping.ai/docs/carrier-registration.md): Learn which business and messaging details to provide so Leadping can handle A2P 10DLC registration and prepare your organization for U.S. business texting.
- [Forbidden Message Categories](https://leadping.ai/docs/forbidden-message-categories.md): Review the traffic, offers, and message categories prohibited on Leadping so you can check your intended messaging before sending leads, texts, or calls.
- [Build with Leadping](https://leadping.ai/docs/developers/overview.md): Choose the correct Leadping credential, endpoint, SDK, webhook flow, or MCP server for your integration.
- [Authenticate API Requests](https://leadping.ai/docs/api-authentication.md): Choose and protect the correct Leadping user token, agent token, organization API key, or source key.
- [Leadping SDKs](https://leadping.ai/docs/sdks/overview.md): Choose and install a generated Leadping SDK for TypeScript, Python, .NET, Go, PHP, or Java, then configure authentication and make typed API requests.
- [Use the TypeScript SDK](https://leadping.ai/docs/sdks/typescript.md): Install the Leadping TypeScript SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Use the Python SDK](https://leadping.ai/docs/sdks/python.md): Install the Leadping Python SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Use the .NET SDK](https://leadping.ai/docs/sdks/dotnet.md): Install the Leadping .NET SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Use the Go SDK](https://leadping.ai/docs/sdks/go.md): Install the Leadping Go SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Use the PHP SDK](https://leadping.ai/docs/sdks/php.md): Install the Leadping PHP SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Use the Java SDK](https://leadping.ai/docs/sdks/java.md): Install the Leadping Java SDK, configure API authentication with a Kiota request adapter, and follow an example to retrieve a lead using typed API routes.
- [Postman Collection](https://leadping.ai/docs/postman.md): Import the Leadping Postman collection, configure bearer or source-key authentication, query leads, and test intake with the required TrustedForm certificate.
- [Configure Automation Webhooks](https://leadping.ai/docs/validating-webhooks.md): Configure Leadping automation HTTP requests and handle tracing, timeouts, retries, and duplicate delivery safely.
- [Handle API Rate Limits](https://leadping.ai/docs/rate-limits.md): Build Leadping API clients that respect route-specific rate limits, handle 429 responses and Retry-After headers, and retry requests safely under load.
- [Connect Leadping MCP Servers](https://leadping.ai/docs/mcp-server.md): Connect AI assistants to public Leadping documentation or authenticated organization tools through MCP.
- [API Deprecation Policy](https://leadping.ai/docs/deprecation-policy.md): How Leadping announces incompatible API changes and retires deprecated API, MCP, webhook, and discovery behavior.
- [Plan an API Integration](https://leadping.ai/docs/roadmap.md): Evaluate available API capabilities, plan integrations around released behavior, and request improvements.
- [Track API Changes](https://leadping.ai/docs/engineering-updates.md): Track Leadping API releases, review contract changes that affect your integration, plan SDK upgrades, and report mismatches between documentation and behavior.
- [Leadping Trust Center](https://leadping.ai/docs/trust/overview.md): Review Leadping security, privacy, data handling, providers, deletion practices, and vulnerability reporting.
- [Security at Leadping](https://leadping.ai/docs/trust/security.md): Understand how Leadping protects customer data through encryption, access control, isolation, monitoring, recovery, and shared responsibility.
- [Leadping Privacy Policy](https://leadping.ai/docs/privacy-policy.md): Learn how Leadping collects, uses, discloses, retains, and protects personal information across lead intake, messaging, calling, billing, and support workflows.
- [Delete a Leadping Account](https://leadping.ai/docs/account-deletion.md): Request deletion of a Leadping user or organization account and understand verification and retained records.
- [Request Data Deletion](https://leadping.ai/docs/data-deletion.md): Request deletion of eligible Leadping data or an account and understand verification, scope, and retention.
- [Leadping Subprocessors](https://leadping.ai/docs/subprocessors.md): Review providers that support Leadping infrastructure, security, communications, payments, documentation, and platform operations.
- [Leadping Business Associate Agreement](https://leadping.ai/docs/business-associate-agreement.md): Review Leadping business associate agreement terms for customers handling protected health information, including safeguards, uses, and responsibilities.
- [Report a Security Vulnerability](https://leadping.ai/docs/trust/responsible-disclosure.md): Report a suspected Leadping vulnerability without exposing data, disrupting service, or testing systems without authorization.
- [Leadping Terms of Service](https://leadping.ai/docs/terms-of-service.md): Review terms governing access to and use of Leadping products and services, including accounts, communications, billing, acceptable use, APIs, and compliance.
- [Acceptable Use Policy for Messaging and Calling](https://leadping.ai/docs/acceptable-use.md): Review Leadping acceptable use requirements for SMS, calling, lead intake, APIs, workflows, automations, prohibited conduct, and carrier compliance.
- [Leadping Cookie Policy](https://leadping.ai/docs/cookie-policy.md): Learn how Leadping uses cookies and similar technologies to operate documentation, measure traffic, remember choices, and support website security.
- [Leadping API Reference](https://leadping.ai/docs/api-reference.md): Use Leadping endpoint schemas, examples, authentication guidance, SDKs, and the public OpenAPI specification.
- [Get the Leadping A2A Agent Card](https://leadping.ai/docs/api-reference/leadpingapi/get-the-leadping-a2a-agent-card.md): Returns Leadping's public A2A Agent Card, including protocol capabilities, authentication requirements, input and output modes, and supported skills.
- [Handle an A2A request](https://leadping.ai/docs/api-reference/leadpingapi/handle-an-a2a-request.md): Send authenticated A2A JSON-RPC requests to Leadping through the API to access supported agent operations and integrate them into your agent workflows.
- [Get organization lead communication analytics](https://leadping.ai/docs/api-reference/analytics/get-organization-lead-communication-analytics.md): Returns current-organization analytics for lead communication, including event volume, response metrics, and date-range filtering.
- [Exports the current organization's analytics with the same cohort, timestamps and definitions as charts.](https://leadping.ai/docs/api-reference/analytics/exports-the-current-organizations-analytics-with-the-same-cohort-timestamps-and-definitions-as-charts.md): Downloads the current organization's analytics as a CSV file, using the same cohort, timestamps, and metric definitions as the analytics charts.
- [Create an organization lead follow-up automation](https://leadping.ai/docs/api-reference/automations/create-an-organization-lead-follow-up-automation.md): Creates an automation for current-organization leads, configuring triggers, message steps, and follow-up behavior.
- [Get an organization lead follow-up automation](https://leadping.ai/docs/api-reference/automations/get-an-organization-lead-follow-up-automation.md): Returns one automation for the current organization, including trigger criteria, message steps, routing settings, and enabled state.
- [Update an organization lead follow-up automation](https://leadping.ai/docs/api-reference/automations/update-an-organization-lead-follow-up-automation.md): Updates an automation for current-organization leads, changing triggers, message steps, routing, or active follow-up settings.
- [Delete an organization lead follow-up automation](https://leadping.ai/docs/api-reference/automations/delete-an-organization-lead-follow-up-automation.md): Deletes an automation for the current organization so it no longer schedules follow-up or routing work for captured leads.
- [Gets recent persisted execution runs for an automation console.](https://leadping.ai/docs/api-reference/automations/gets-recent-persisted-execution-runs-for-an-automation-console.md): Returns recent execution history for the specified automation in the current organization, including run state and console details.
- [Gets one persisted automation execution run for its console.](https://leadping.ai/docs/api-reference/automations/gets-one-persisted-automation-execution-run-for-its-console.md): Returns the specified persisted execution run for an automation in the current organization, including its current console state.
- [List organization lead follow-up automations](https://leadping.ai/docs/api-reference/automations/list-organization-lead-follow-up-automations.md): Lists current-user automations with paging, sorting, and filters for reviewing follow-up workflows and ownership.
- [Preview a lead follow-up automation](https://leadping.ai/docs/api-reference/automations/preview-a-lead-follow-up-automation.md): Preview matched automation steps and messages for a sample lead without creating follow-up events, or use validate_only to check the automation configuration.
- [Runs an automation through its Manual trigger.](https://leadping.ai/docs/api-reference/automations/runs-an-automation-through-its-manual-trigger.md): Starts the specified automation through its manual trigger and returns the newly created execution record.
- [Lists published blog articles.](https://leadping.ai/docs/api-reference/blogarticles/lists-published-blog-articles.md): Retrieve the list of published Leadping blog articles through the public API. This endpoint returns articles available to readers without authentication.
- [Gets a published blog article by slug.](https://leadping.ai/docs/api-reference/blogarticles/gets-a-published-blog-article-by-slug.md): Returns the public article identified by its URL slug, or a not-found response when no published article matches.
- [List current user's inbox conversations](https://leadping.ai/docs/api-reference/conversations/list-current-users-inbox-conversations.md): Lists the current user's lead conversations with paging and sorting for inbox views, recent follow-up, and communication history.
- [Marks an inbox conversation as read.](https://leadping.ai/docs/api-reference/conversations/marks-an-inbox-conversation-as-read.md): Updates the conversation's read state for the current user's inbox and returns whether the conversation was found.
- [List inbox conversations for a lead](https://leadping.ai/docs/api-reference/conversations/list-inbox-conversations-for-a-lead.md): Lists conversations for one lead, helping users inspect communication threads, recent follow-up, and related events.
- [Create product feedback for an organization](https://leadping.ai/docs/api-reference/feedback/create-product-feedback-for-an-organization.md): Creates product feedback for the current organization, capturing category, message, and context for operator review.
- [Create a lead record from an external source](https://leadping.ai/docs/api-reference/leads/create-a-lead-record-from-an-external-source.md): Creates a source-authenticated lead captured outside Leadping, starting follow-up, routing, and automation from structured lead data.
- [Create a lead record from intake payload](https://leadping.ai/docs/api-reference/leads/create-a-lead-record-from-intake-payload.md): Creates a source-authenticated lead from a flat intake payload, capturing contact fields, metadata, and automation-ready lead details.
- [Get an organization lead record for current user](https://leadping.ai/docs/api-reference/leads/get-an-organization-lead-record-for-current-user.md): Returns one lead visible to the current user, including communication details, status, source, and follow-up context.
- [Update an organization lead record and status](https://leadping.ai/docs/api-reference/leads/update-an-organization-lead-record-and-status.md): Updates lead details for the current organization, keeping contact data, status, source, and follow-up context current.
- [Delete an organization lead record by ID](https://leadping.ai/docs/api-reference/leads/delete-an-organization-lead-record-by-id.md): Mark a lead as deleted to hide it from lead, conversation, routing, and event workflows while retaining the stored lead, conversation, and event records.
- [Get a lead automation workflow status](https://leadping.ai/docs/api-reference/leads/get-a-lead-automation-workflow-status.md): Returns automation workflow status for one lead, including active runs, paused state, and follow-up progress for the current organization.
- [Archive an organization lead record by ID](https://leadping.ai/docs/api-reference/leads/archive-an-organization-lead-record-by-id.md): Archive a lead to remove it from active pipeline views while preserving communication and event history. An optional request body supplies the archive reason.
- [Unarchive an organization lead record by ID](https://leadping.ai/docs/api-reference/leads/unarchive-an-organization-lead-record-by-id.md): Restores an archived lead to active pipeline views so follow-up, communication, and routing workflows can resume.
- [List organization lead records for current user](https://leadping.ai/docs/api-reference/leads/list-organization-lead-records-for-current-user.md): Lists leads visible to the current user with paging, sorting, filters, tags, and archive status for pipeline review.
- [Replace organization tags on a lead record](https://leadping.ai/docs/api-reference/leads/replace-organization-tags-on-a-lead-record.md): Replaces all tags on a lead with the supplied current-organization tags, keeping segmentation and routing labels in sync.
- [Add organization tags to a lead record by ID](https://leadping.ai/docs/api-reference/leads/add-organization-tags-to-a-lead-record-by-id.md): Adds one or more current-organization tags to a lead so users can segment, filter, route, and review follow-up work.
- [Remove an organization tag from a lead record](https://leadping.ai/docs/api-reference/leads/remove-an-organization-tag-from-a-lead-record.md): Removes one current-organization tag from a lead while leaving the lead record, other tags, and communication history intact.
- [Assign an organization lead to an active member, or return it to the unassigned queue.](https://leadping.ai/docs/api-reference/leads/assign-an-organization-lead-to-an-active-member-or-return-it-to-the-unassigned-queue.md): Updates ownership of the specified lead after validating that the selected assignee is an active member of the current organization.
- [Set a lead's current status](https://leadping.ai/docs/api-reference/leadstatuschanges/set-a-leads-current-status.md): Sets the lead's current structured status and records the change for audit, automation, and reporting.
- [Get a lead status history entry](https://leadping.ai/docs/api-reference/leadstatuschanges/get-a-lead-status-history-entry.md): Returns one lead status change record so users can review a lead outcome, related notes, and follow-up context.
- [Update a lead status history entry](https://leadping.ai/docs/api-reference/leadstatuschanges/update-a-lead-status-history-entry.md): Update a Leadping lead status history entry through the API. When the entry is current, the operation also updates the lead's current status to match.
- [Delete a lead status history entry](https://leadping.ai/docs/api-reference/leadstatuschanges/delete-a-lead-status-history-entry.md): Deletes a lead status change from a lead when the outcome record should no longer appear in event or reporting views.
- [List current-organization lead status history](https://leadping.ai/docs/api-reference/leadstatuschanges/list-current-organization-lead-status-history.md): Returns a filtered, paginated history of lead status changes for the current organization for workflow analysis, reporting, and audit review.
- [List a lead's status history](https://leadping.ai/docs/api-reference/leadstatuschanges/list-a-leads-status-history.md): Lists lead status change outcome history for one lead, including prior outcomes, notes, follow-up context, timestamps, and actor details used for audit review.
- [Export a lead's status history](https://leadping.ai/docs/api-reference/leadstatuschanges/export-a-leads-status-history.md): Exports lead status change data for one lead, packaging outcome history for reporting, audit review, or handoff workflows.
- [List the current organization's lead statuses](https://leadping.ai/docs/api-reference/leadstatuses/list-the-current-organizations-lead-statuses.md): Lists the current organization's active lead statuses for organizing and tracking leads through the sales workflow.
- [Create an organization lead status](https://leadping.ai/docs/api-reference/leadstatuses/create-an-organization-lead-status.md): Creates a reusable lead status for the current organization to categorize, organize, and track leads consistently throughout its sales and follow-up workflow.
- [Update an organization lead status](https://leadping.ai/docs/api-reference/leadstatuses/update-an-organization-lead-status.md): Updates the name, color, and display order of a lead status owned by the current organization so pipeline stages remain clear and consistently organized.
- [Archive an organization lead status](https://leadping.ai/docs/api-reference/leadstatuses/archive-an-organization-lead-status.md): Archives a lead status for the current organization so it is unavailable for new assignments while existing lead history is preserved.
- [Get a current-user notification](https://leadping.ai/docs/api-reference/notifications/get-a-current-user-notification.md): Returns one notification for the current user and organization, including its content, read state, delivery context, and relevant account activity.
- [List notifications for current user](https://leadping.ai/docs/api-reference/notifications/list-notifications-for-current-user.md): Lists current-user notifications with paging, sorting, and filters for operational alerts, announcements, and follow-up updates.
- [Get unread notifications for current user](https://leadping.ai/docs/api-reference/notifications/get-unread-notifications-for-current-user.md): Returns the current user's unread notification count for badge updates and notification center state.
- [Mark a current-user notification as read](https://leadping.ai/docs/api-reference/notifications/mark-a-current-user-notification-as-read.md): Marks one current-user notification as read so it no longer contributes to unread counts or active notification lists.
- [Mark all current-user notifications as read](https://leadping.ai/docs/api-reference/notifications/mark-all-current-user-notifications-as-read.md): Marks all notifications for the current user as read and returns the number updated for notification center refreshes.
- [List announcements for current user](https://leadping.ai/docs/api-reference/notifications/list-announcements-for-current-user.md): Lists announcement notifications for the current user with paging and filters for release notes, notices, and operational updates.
- [Register a current-user mobile push installation](https://leadping.ai/docs/api-reference/notifications/register-a-current-user-mobile-push-installation.md): Registers or refreshes the authenticated user's mobile push installation so Leadping can deliver account and workflow notifications to the device.
- [Unregister a current-user mobile push installation](https://leadping.ai/docs/api-reference/notifications/unregister-a-current-user-mobile-push-installation.md): Removes a mobile push installation from the authenticated user's account so Leadping no longer sends notifications to that device.
- [Get organization outbound delivery overview](https://leadping.ai/docs/api-reference/outbounddelivery/get-organization-outbound-delivery-overview.md): Returns current-organization outbound capacity, scheduled work, and pacing decisions used to control lead communication delivery.
- [Create an organization lead intake source](https://leadping.ai/docs/api-reference/sources/create-an-organization-lead-intake-source.md): Creates a lead source for the current organization, storing intake credentials and routing context for captured external leads.
- [Get an organization lead intake source by ID](https://leadping.ai/docs/api-reference/sources/get-an-organization-lead-intake-source-by-id.md): Returns one lead source for the current organization, including intake settings, credentials metadata, and routing context.
- [Update an organization lead intake source](https://leadping.ai/docs/api-reference/sources/update-an-organization-lead-intake-source.md): Updates a lead source for the current organization, changing intake settings, credentials, routing context, or active status.
- [Delete an organization lead intake source](https://leadping.ai/docs/api-reference/sources/delete-an-organization-lead-intake-source.md): Deletes a lead source from the current organization so it can no longer accept or route newly captured leads.
- [Rotate a source intake credential.](https://leadping.ai/docs/api-reference/sources/rotate-a-source-intake-credential.md): Invalidates the current credential and returns the replacement secret once. Only its hash and short preview are retained.
- [List organization lead intake sources for user](https://leadping.ai/docs/api-reference/sources/list-organization-lead-intake-sources-for-user.md): Lists current-user lead sources with paging, sorting, and filters for intake configuration and routing review.
- [Get lead metrics for a source](https://leadping.ai/docs/api-reference/sources/get-lead-metrics-for-a-source.md): View lead creation metrics for an organization intake source, including accepted, rejected, duplicate, validation, and recent activity counts.
- [Create or reactivate a recipient suppression](https://leadping.ai/docs/api-reference/suppressions/create-or-reactivate-a-recipient-suppression.md): The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
- [Release an active recipient suppression](https://leadping.ai/docs/api-reference/suppressions/release-an-active-recipient-suppression.md): The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
- [Check whether a recipient is suppressed](https://leadping.ai/docs/api-reference/suppressions/check-whether-a-recipient-is-suppressed.md): The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
- [List current-organization suppression entries](https://leadping.ai/docs/api-reference/suppressions/list-current-organization-suppression-entries.md): Returns a filtered, paginated list of recipients the current organization has blocked from phone, SMS, or email outreach.
- [Get an organization suppression entry](https://leadping.ai/docs/api-reference/suppressions/get-an-organization-suppression-entry.md): Returns one suppression entry for the current organization, including its recipient, channel, reason, status, and audit timestamps.
- [List organization lead segmentation tags](https://leadping.ai/docs/api-reference/tags/list-organization-lead-segmentation-tags.md): Lists tags for the current organization, optionally including archived tags, for lead segmentation, filters, and routing labels.
- [Create an organization lead segmentation tag](https://leadping.ai/docs/api-reference/tags/create-an-organization-lead-segmentation-tag.md): Creates a tag for the current organization so leads can be segmented, filtered, routed, and reviewed by label.
- [Update an organization lead segmentation tag](https://leadping.ai/docs/api-reference/tags/update-an-organization-lead-segmentation-tag.md): Updates a current-organization tag's name, color, or archived state so lead segmentation and filters stay consistent.
- [Archive an organization lead segmentation tag](https://leadping.ai/docs/api-reference/tags/archive-an-organization-lead-segmentation-tag.md): Archives a tag for the current organization so it stops being used for new segmentation while historical lead labels remain available.
- [Get current user's billing payment method](https://leadping.ai/docs/api-reference/users/get-current-users-billing-payment-method.md): Returns the current user's default payment method details for billing displays and account payment management.
- [Get current user account profile details](https://leadping.ai/docs/api-reference/users/get-current-user-account-profile-details.md): Returns the current user's profile, roles, organization context, billing state, and compliance settings for portal sessions.
- [Update current user account profile](https://leadping.ai/docs/api-reference/users/update-current-user-account-profile.md): Updates the current user's profile fields, contact details, preferences, or organization context used across Leadping.
- [Updates the current user's notification preferences without requiring profile fields.](https://leadping.ai/docs/api-reference/users/updates-the-current-users-notification-preferences-without-requiring-profile-fields.md): Update notification channel and delivery preferences for the authenticated Leadping user through the API without submitting unrelated user profile fields.
- [Change the current user's billing plan](https://leadping.ai/docs/api-reference/users/change-the-current-users-billing-plan.md): Changes the current user's billing plan selection, updating account billing state and plan-specific capabilities.
- [Update current user compliance settings](https://leadping.ai/docs/api-reference/users/update-current-user-compliance-settings.md): Updates current-user compliance settings used for messaging eligibility, billing readiness, and organization account setup.
- [Initiate a Leadping phone call](https://leadping.ai/docs/api-reference/calls/initiate-a-leadping-phone-call.md): The call operation validates ownership and current provider state before returning the updated Leadping call representation.
- [End an active Leadping phone call](https://leadping.ai/docs/api-reference/calls/end-an-active-leadping-phone-call.md): The call operation validates ownership and current provider state before returning the updated Leadping call representation.
- [Get the status of a Leadping phone call](https://leadping.ai/docs/api-reference/calls/get-the-status-of-a-leadping-phone-call.md): The call operation validates ownership and current provider state before returning the updated Leadping call representation.
- [Transfer an active Leadping phone call](https://leadping.ai/docs/api-reference/calls/transfer-an-active-leadping-phone-call.md): The call operation validates ownership and current provider state before returning the updated Leadping call representation.
- [Search purchasable organization phone numbers](https://leadping.ai/docs/api-reference/phonenumbers/search-purchasable-organization-phone-numbers.md): Searches available phone numbers for purchase, applying country, area, and capability filters for lead communication setup.
- [List current-organization phone numbers](https://leadping.ai/docs/api-reference/phonenumbers/list-current-organization-phone-numbers.md): Lists phone numbers visible to the current organization with paging, sorting, and filters for messaging, calling, and warmup management.
- [Select conversation sender number](https://leadping.ai/docs/api-reference/phonenumbers/select-conversation-sender-number.md): Selects the outgoing phone number for an existing conversation, considering assignments, overrides, and delivery eligibility.
- [Select new lead sender number](https://leadping.ai/docs/api-reference/phonenumbers/select-new-lead-sender-number.md): Selects an outgoing phone number for a new outbound lead message using destination, source, and delivery eligibility rules.
- [Validate sender number override](https://leadping.ai/docs/api-reference/phonenumbers/validate-sender-number-override.md): Validates a manual outgoing-number override before use, checking ownership, destination, and delivery eligibility.
- [Set sender number override](https://leadping.ai/docs/api-reference/phonenumbers/set-sender-number-override.md): Sets the outgoing phone number override for a conversation so future lead messages use the selected eligible number.
- [Clear sender number override](https://leadping.ai/docs/api-reference/phonenumbers/clear-sender-number-override.md): Clears a conversation's outgoing-number override so future lead messages return to automatic number selection.
- [Get organization phone number details by ID](https://leadping.ai/docs/api-reference/phonenumbers/get-organization-phone-number-details-by-id.md): Returns one phone number visible to the current user, including messaging status, assignment, warmup, and purchase metadata.
- [Update organization phone number settings](https://leadping.ai/docs/api-reference/phonenumbers/update-organization-phone-number-settings.md): Updates phone number settings such as its optional label, assignment, messaging options, or warmup configuration.
- [Delete an organization phone number by ID](https://leadping.ai/docs/api-reference/phonenumbers/delete-an-organization-phone-number-by-id.md): Deletes a phone number from the current organization when it should no longer be used for lead communication.
- [Create an organization phone number for messaging](https://leadping.ai/docs/api-reference/phonenumbers/create-an-organization-phone-number-for-messaging.md): Purchases or creates a phone number for the current organization so it can be assigned to messaging, calls, and lead follow-up.
- [Get organization phone number provider status](https://leadping.ai/docs/api-reference/phonenumbers/get-organization-phone-number-provider-status.md): Returns provider and Leadping status for a phone number, including messaging warmup, assignments, and verification state.
- [Get organization phone number warmup status](https://leadping.ai/docs/api-reference/phonenumbers/get-organization-phone-number-warmup-status.md): Returns warmup status for a phone number, including limits and recent events used for delivery pacing.
- [Check phone number purchase availability](https://leadping.ai/docs/api-reference/phonenumbers/check-phone-number-purchase-availability.md): Checks whether a phone number can be purchased for the current organization before creating or assigning it.
- [Send an SMS message to an organization lead](https://leadping.ai/docs/api-reference/sms/send-an-sms-message-to-an-organization-lead.md): Sends an SMS message to a lead or phone number, applying current-organization sender selection, scheduling, and delivery rules.
- [Upload media for an MMS message](https://leadping.ai/docs/api-reference/sms/upload-media-for-an-mms-message.md): Uploads and validates one media attachment, returning the metadata needed to include the asset in a subsequent Leadping MMS send.
- [Cancel a scheduled SMS message for a lead](https://leadping.ai/docs/api-reference/sms/cancel-a-scheduled-sms-message-for-a-lead.md): Cancel a queued SMS message while its status is Scheduled to prevent sending and preserve the event record. Cancellation closes when message delivery begins.
- [Generate a WebRTC login token](https://leadping.ai/docs/api-reference/telephony/generate-a-webrtc-login-token.md): The issued client configuration is scoped to the authenticated user and contains only the short-lived credentials required by the calling client.
- [Get current organization account profile](https://leadping.ai/docs/api-reference/organizations/get-current-organization-account-profile.md): Returns the authenticated user's current organization profile, including account settings, billing context, and communication configuration.
- [Update current organization account profile](https://leadping.ai/docs/api-reference/organizations/update-current-organization-account-profile.md): Updates the authenticated user's current organization profile, including contact, settings, and communication configuration.
- [Create an organization account](https://leadping.ai/docs/api-reference/organizations/create-an-organization-account.md): Creates an organization account for the authenticated user, assigns them as its owner, and makes it their active organization context.
- [List organization switch options](https://leadping.ai/docs/api-reference/organizations/list-organization-switch-options.md): Lists organizations the authenticated user can switch into, including membership role and current-organization selection data.
- [Switch current organization account context](https://leadping.ai/docs/api-reference/organizations/switch-current-organization-account-context.md): Switches the authenticated user's active organization context so subsequent lead, billing, and communication requests target that organization.
- [List users for the current organization](https://leadping.ai/docs/api-reference/organizations/list-users-for-the-current-organization.md): Lists users assigned to the current organization, including roles and membership details for access management.
- [Add a user to the current organization account](https://leadping.ai/docs/api-reference/organizations/add-a-user-to-the-current-organization-account.md): Adds an existing user to the current organization with the requested role for shared lead communication and account access.
- [Change a current-organization user role](https://leadping.ai/docs/api-reference/organizations/change-a-current-organization-user-role.md): Changes a user's role in the current organization, updating access to lead, automation, billing, and admin workflows.
- [Remove a user from the current organization](https://leadping.ai/docs/api-reference/organizations/remove-a-user-from-the-current-organization.md): Removes a user from the current organization, revoking their access to its leads, settings, billing, and communication data.
- [Leave the current organization without changing its subscription or deleting organization data.](https://leadping.ai/docs/api-reference/organizations/leave-the-current-organization-without-changing-its-subscription-or-deleting-organization-data.md): Removes the authenticated user's membership from the current organization while preserving the organization and its billing state.
- [List invitations for the current organization](https://leadping.ai/docs/api-reference/organizations/list-invitations-for-the-current-organization.md): Lists pending and historical invitations for the current organization, including recipient, role, status, and expiration.
- [Create a current-organization user invitation](https://leadping.ai/docs/api-reference/organizations/create-a-current-organization-user-invitation.md): Creates an invitation for the current organization so another user can join with the requested role and account access.
- [Resend a current-organization user invitation](https://leadping.ai/docs/api-reference/organizations/resend-a-current-organization-user-invitation.md): Resends a pending current-organization invitation, refreshing delivery while preserving recipient, role, and acceptance token.
- [Revoke a current-organization user invitation](https://leadping.ai/docs/api-reference/organizations/revoke-a-current-organization-user-invitation.md): Revokes a pending current-organization invitation so the recipient can no longer use it to join the organization.
- [Update organization 10DLC notes](https://leadping.ai/docs/api-reference/organizations/update-organization-10dlc-notes.md): Updates the shared 10DLC registration notes for the current organization, keeping carrier review context and messaging compliance details current.
- [List current-organization API keys](https://leadping.ai/docs/api-reference/organizations/list-current-organization-api-keys.md): The operation enforces organization ownership or platform-admin authorization and returns state suitable for membership, billing, and support workflows.
- [Gets a safe API key detail row for a key the caller can access.](https://leadping.ai/docs/api-reference/organizations/gets-a-safe-api-key-detail-row-for-a-key-the-caller-can-access.md): The operation enforces organization ownership or platform-admin authorization and returns state suitable for membership, billing, and support workflows.
- [Creates an organization-owned API key.](https://leadping.ai/docs/api-reference/organizations/creates-an-organization-owned-api-key.md): The operation enforces organization ownership or platform-admin authorization and returns state suitable for membership, billing, and support workflows.
- [Deletes an organization-owned API key without deleting the organization.](https://leadping.ai/docs/api-reference/organizations/deletes-an-organization-owned-api-key-without-deleting-the-organization.md): The operation enforces organization ownership or platform-admin authorization and returns state suitable for membership, billing, and support workflows.
- [Request a current-user data export report](https://leadping.ai/docs/api-reference/userdataexports/request-a-current-user-data-export-report.md): Requests a data export for the current user, starting asynchronous report generation for account, lead, and event records.
- [Get a current-user data export report](https://leadping.ai/docs/api-reference/userdataexports/get-a-current-user-data-export-report.md): Returns the status and metadata for one current-user data export, including readiness, expiration, and download availability.
- [Download a current-user data export report](https://leadping.ai/docs/api-reference/userdataexports/download-a-current-user-data-export-report.md): Validates an export download token and redirects to the generated file when the current-user report is ready.
- [List current-user lead call event history](https://leadping.ai/docs/api-reference/callevents/list-current-user-lead-call-event-history.md): Lists call events visible to the current user with paging, sorting, and filters for call history and lead follow-up review.
- [Get lead call event details by event ID](https://leadping.ai/docs/api-reference/callevents/get-lead-call-event-details-by-event-id.md): Returns one call event, including call metadata, provider status, related lead, and communication context.
- [List call event history for an organization lead](https://leadping.ai/docs/api-reference/callevents/list-call-event-history-for-an-organization-lead.md): Lists call events for one lead with paging, helping users review call attempts, outcomes, and follow-up history.
- [List call event history for a phone number](https://leadping.ai/docs/api-reference/callevents/list-call-event-history-for-a-phone-number.md): Lists call events for one phone number with paging, helping users review volume, outcomes, and communication history.
- [List current-user lead events](https://leadping.ai/docs/api-reference/events/list-current-user-lead-events.md): Lists event records visible to the current user with paging, sorting, and filters across lead, SMS, call, and automation events.
- [List organization lead event history](https://leadping.ai/docs/api-reference/events/list-organization-lead-event-history.md): Lists event records for an organization with paging and filters so admins can review lead communication and automation events.
- [List a conversation's event history](https://leadping.ai/docs/api-reference/events/list-a-conversations-event-history.md): Lists event records for one conversation with paging, including notes, messages, calls, and follow-up history.
- [List event history for a lead](https://leadping.ai/docs/api-reference/events/list-event-history-for-a-lead.md): Lists event records for one lead with paging, covering communication, routing, automation, and event changes.
- [Get lead event details by ID](https://leadping.ai/docs/api-reference/events/get-lead-event-details-by-id.md): Returns one event record by ID, including event type, timestamps, related entities, and summary payload data.
- [Get full lead event payload by ID](https://leadping.ai/docs/api-reference/events/get-full-lead-event-payload-by-id.md): Returns detailed event data by ID, including the full JSON payload for debugging, audit review, and workflow inspection.
- [Add a note to a conversation](https://leadping.ai/docs/api-reference/events/add-a-note-to-a-conversation.md): Creates a note event on a conversation so users can document lead context, handoffs, and follow-up details.
- [List current-user lead SMS event history](https://leadping.ai/docs/api-reference/smsevents/list-current-user-lead-sms-event-history.md): Lists SMS events visible to the current user with paging, sorting, and filters for message history and follow-up review.
- [Get lead SMS event details by event ID](https://leadping.ai/docs/api-reference/smsevents/get-lead-sms-event-details-by-event-id.md): Returns one SMS event, including message metadata, provider status, related lead, and delivery context.
- [List message event history for a lead](https://leadping.ai/docs/api-reference/smsevents/list-message-event-history-for-a-lead.md): Lists SMS events for one lead with paging, helping users review sent messages, scheduled messages, and delivery outcomes.
- [List SMS event history for a phone number](https://leadping.ai/docs/api-reference/smsevents/list-sms-event-history-for-a-phone-number.md): Lists SMS events for one phone number with paging, helping users review volume, delivery outcomes, and communication history.
- [List payment methods](https://leadping.ai/docs/api-reference/paymentmethods/list-payment-methods.md): Lists the payment methods available to the current organization for billing, invoice payments, and wallet funding.
- [List current-organization Stripe invoices](https://leadping.ai/docs/api-reference/paymentmethods/list-current-organization-stripe-invoices.md): Returns the current organization's Stripe invoices with their amounts, payment status, billing period, and hosted invoice details.
- [Get invoice PDF access](https://leadping.ai/docs/api-reference/paymentmethods/get-invoice-pdf-access.md): Creates a short-lived, secure URL that lets the current organization view or download a private Stripe invoice PDF without exposing a permanent file link.
- [Get an organization billing payment method](https://leadping.ai/docs/api-reference/paymentmethods/get-an-organization-billing-payment-method.md): Returns one payment method for the current user or organization, including card metadata used for billing management.
- [Delete an organization billing payment method](https://leadping.ai/docs/api-reference/paymentmethods/delete-an-organization-billing-payment-method.md): Deletes a payment method so it is no longer available for wallet funding, invoices, or billing account management.
- [Set default payment method](https://leadping.ai/docs/api-reference/paymentmethods/set-default-payment-method.md): Sets a payment method as the default for the current organization's future invoices and billing activity.
- [Get a current-user billing transaction](https://leadping.ai/docs/api-reference/transactions/get-a-current-user-billing-transaction.md): Returns one transaction visible to the current user, including amount, status, wallet context, and billing metadata.
- [List current-user billing transactions](https://leadping.ai/docs/api-reference/transactions/list-current-user-billing-transactions.md): Lists current-user transactions with paging, sorting, and filters for wallet events, billing history, and reconciliation.
- [List organization messaging usage ledger entries](https://leadping.ai/docs/api-reference/usage/list-organization-messaging-usage-ledger-entries.md): Lists current-organization usage ledger entries with paging, sorting, and filters for messaging, billing, and wallet review.
- [Get organization messaging usage summary](https://leadping.ai/docs/api-reference/usage/get-organization-messaging-usage-summary.md): Returns current-organization usage totals for the active billing period, including spend, limits, and event summary data.
- [Get an organization wallet balance by ID](https://leadping.ai/docs/api-reference/wallets/get-an-organization-wallet-balance-by-id.md): Returns one wallet by ID, including balance, billing context, and funding status for account payment workflows.
- [Get the current organization wallet balance](https://leadping.ai/docs/api-reference/wallets/get-the-current-organization-wallet-balance.md): Returns the current organization wallet, including balance and funding status used for communication delivery and billing.
- [Receive an automation webhook using get](https://leadping.ai/docs/api-reference/receive-an-automation-webhook-using-get.md): Receives a consumer-configured Leadping automation request. Correlation headers are for tracing and deduplication, not authentication or proof of origin.
- [Receive an automation webhook using put](https://leadping.ai/docs/api-reference/receive-an-automation-webhook-using-put.md): Receives a consumer-configured Leadping automation request. Correlation headers are for tracing and deduplication, not authentication or proof of origin.
- [Receive an automation webhook using post](https://leadping.ai/docs/api-reference/receive-an-automation-webhook-using-post.md): Receives a consumer-configured Leadping automation request. Correlation headers are for tracing and deduplication, not authentication or proof of origin.
- [Receive an automation webhook using patch](https://leadping.ai/docs/api-reference/receive-an-automation-webhook-using-patch.md): Receives a consumer-configured Leadping automation request. Correlation headers are for tracing and deduplication, not authentication or proof of origin.

## OpenAPI Specs

- [openapi](/docs/openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.