Track API Changes

Track Leadping API releases, review contract changes that affect your integration, plan SDK upgrades, and report mismatches between documentation and behavior.

Use this page to find release information relevant to an existing Leadping integration. The machine-readable API changelog is the release record for public contract changes.

Find the information you need

Question	Resource
What API behavior changed?	API changelog
What can the current API accept and return?	API reference and OpenAPI document
How do I use a generated client?	SDK guides
Is an older behavior being retired?	Deprecation policy and the affected change notice
How do I reproduce a request?	Postman collection guide

Evaluate a change for your integration

Record the SDK version and operations your application currently uses. Compare a release notice with those dependencies, including optional fields, status values, authentication, and retry behavior. A new endpoint may require no action; a changed field or retired behavior may require a migration.

Keep one controlled request and expected result for each workflow you depend on. Re-run the affected examples after an upgrade and check the resulting records as well as the HTTP status. Avoid using live message sends, calls, or number purchases as routine release checks.

Report a contract mismatch

If a documented request behaves differently, send support the operation, SDK and runtime versions if applicable, time and time zone, HTTP status, and a redacted example. Include the documentation URL and expected result so the team can distinguish a documentation problem from a service or configuration issue.

Do not include credentials, full lead records, or private certificate URLs. Send reports to [e-mail].