Postman Collection

Import the Leadping Postman collection, configure bearer or source-key authentication, query leads, and test intake with the required TrustedForm certificate.

The Leadping Postman collection contains runnable starter requests for organization lookup, lead queries, lead retrieval, and source-key lead intake.

Import the collection

1. Download the collection JSON from the link above.
2. In Postman, select Import, then choose the downloaded file or paste its URL.
3. Set the collection variables required for your request.
4. Send requests only against an account and data you are authorized to use.

Collection variables

Variable	Purpose
baseUrl	Defaults to https://api.leadping.ai.
accessToken	OAuth access token or organization API key for authenticated organization requests.
sourceKey	lp_src_... key used only by lead-intake requests.
trustedFormUrl	Real TrustedForm certificate URL required by the intake example.
leadId	Lead identifier used by the get-lead request.

Store secrets in a private Postman environment when possible. Do not commit populated collection variables, paste credentials into shared workspaces, or use a source key on organization endpoints.

Use API Authentication to select the correct identity and Send Leads with the Intake API for lead-ingestion requirements. The interactive API reference remains the complete endpoint catalog.

Verify a read before testing intake

1. Set accessToken to an organization key or authorized user token.
2. Send Get current organization and confirm the returned organization.
3. Send List leads, copy an existing record ID into leadId, and send Get lead.

The organization and lead reads inherit the collection’s Bearer authentication. The Lead intake folder overrides it with sourceKey. Check the effective authentication if a request returns 401; changing accessToken will not replace the intake folder’s credential.

Run one controlled intake request

Set sourceKey for the intended source and trustedFormUrl to the certificate from your test submission. Edit the example contact details to use a contact you control. Check enabled automations first, because this request creates a production record and may start follow-up or incur charges.

After 201 Created, save the returned lead ID and check processing in Leadping. Sending the request again can create another lead; the example’s external ID is not an idempotency guarantee. Do not run the intake folder as a repeated collection test against production.

Share a reproducible example

Before exporting a collection or environment, clear tokens, source keys, certificate URLs, and personal data. Include the request name, HTTP status, approximate time, and redacted problem detail when asking for help. A shared collection should contain placeholders that the recipient fills locally.