Skip to main content
POST
/
leads
curl --request POST \
  --url https://usejuiced.com/api/leads \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "first_name": "Katy",
  "last_name": "Berry",
  "email": "katy.berry@thirstyleads.com",
  "phone": "555-123-4567",
  "address_1": "742 Orchard Lane",
  "city": "Paradise Bay",
  "state": "FL",
  "zip": "33139"
}
'
{
  "lead_uuid": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "status": "assigned",
  "price": 45
}

Authorizations

​
Authorization
string
header
required

Use your source's API key as the username and API secret as the password. Base64 encode the credentials in the format api_key:api_secret.

Body

application/json
​
zip
string
required

Postal code. Must be valid for your account's operating countries.

Example:

"33139"

​
ping_id
string<uuid>

Reference to a previous ping request. Include to link this lead to prior pricing.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"

​
bid_id
string<uuid>

Specific bid to accept from the ping response. Only applicable for internal sources.

Example:

"7c9e6679-7425-40de-944b-e07fc1f90ae7"

​
{key}
any

Additional fields as configured for your source and lead type.

Response

Lead created successfully

​
lead_uuid
string

Unique identifier for the created lead.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"

​
status
enum<string>

Current status of the lead.

Available options:
pending,
assigned,
duplicate,
unassigned,
marketplace
Example:

"assigned"

​
price
number<float>

Price paid for the lead. Zero if not yet assigned.

Example:

45