Developers & API — PulseLeadz

1. Create API key (admin session)

Log in as workspace admin first. Keys look like plz_… and are shown once.

Key name

—

2. Auth

Authorization: Bearer plz_your_key_here

# or

X-API-Key: plz_your_key_here

3. Endpoints

Method	Path	Scope	Use
GET	`/v1/health`	—	Public ping
GET	`/v1/me`	read	Workspace + plan limits
GET	`/v1/usage`	read	Minutes / SMS used + overage estimate
GET	`/v1/campaigns`	read	List campaigns
POST	`/v1/leads`	write	Import leads batch
GET	`/v1/leads`	read	List leads
POST	`/v1/calls`	dial	Originate / queue dial
POST	`/v1/sms`	sms	Paused: requires an authenticated agent and assigned sending number
GET	`/v1/dispositions`	read	Dispo list

4. Examples

curl -s -H "Authorization: Bearer plz_XXX" https://pulseleadz.com/v1/me

curl -s -X POST -H "Authorization: Bearer plz_XXX" -H "Content-Type: application/json" \

  https://pulseleadz.com/v1/leads \

  -d '{"leads":[{"phone":"3055551212","first_name":"Ada","company":"Acme"}]}'

curl -s -X POST -H "Authorization: Bearer plz_XXX" -H "Content-Type: application/json" \

  https://pulseleadz.com/v1/calls \

  -d '{"phone":"13055551212"}'

API-key SMS sending is paused. It returns HTTP 409 until an authenticated agent and owned sending number can be verified. Agents can send through Conversations using their assigned number.

5. Make / Zapier / n8n

HTTP module → URL /v1/leads or /v1/calls
Header Authorization: Bearer plz_…
Body JSON as above · map CRM fields → phone / name
Poll /v1/usage for billing dashboards

Pricing (API customers)