Authentication

PIPBIT.IO uses API keys to authenticate requests. You can view and manage your API keys in the Dashboard.

Include your API key in requests using the Authorization header with the Bearer scheme, or pass it as a URL parameter.

Replace your_api_key with your actual API key.

Security

Private API Keys

Use private keys for server-side applications. Never expose them publicly. You can restrict keys to specific IP addresses for additional security.

Public API Keys

Use public keys for client-side applications. They require trusted domain configuration and are rate limited to 10 requests per day per user.

Testing

Use these test emails to validate your integration without consuming credits:

Email Result
[email protected] Returns deliverable
[email protected] Returns undeliverable
[email protected] Returns risky
GET

Verify Email

Verify a single email address and get detailed deliverability information.

Parameters

Parameter Type Description
email REQUIRED string The email address to verify
api_key REQUIRED string Your API key (if not using header)
smtp boolean Enable SMTP mailbox verification. Connects to mail server to check if mailbox exists. Default: true
site_source string Optional identifier for tracking the source of the request

Response

Field Type Description
emailstringThe verified email address
statusstringvalid or invalid
scoreintegerDeliverability score (0-100)
deliverabilitystringdeliverable, undeliverable, or risky
disposablebooleanIs disposable email domain
rolebooleanIs role-based address
freebooleanIs free email provider
catch_allbooleanIs catch-all domain (accepts all emails)
risk_factorsarrayList of risk factors detected (e.g., smtp_rejected)
site_sourcestringSource identifier (if provided in request)
durationnumberProcessing time in seconds
POST

Batch Verification

Submit multiple emails for batch verification. Results are processed asynchronously.

Request Body

Parameter Type Description
emails REQUIRED array Array of email addresses (max 50,000)
callback_url string Webhook URL for completion notification
GET

Account

Retrieve your account information including credit balance and usage statistics.

Rate Limits

API requests are rate limited based on your subscription plan:

Plan Requests/Min Requests/Day
Free10100
Starter6010,000
Professional12050,000
Enterprise300500,000

Rate limits apply to all API endpoints including single verify, batch verify, account, and filter endpoints. Limits are enforced per API key.

Rate Limit Headers

Every API response includes headers to help you track your rate limit usage:

Header Description
X-RateLimit-Limit Maximum requests allowed per minute for your plan
X-RateLimit-Remaining Number of requests remaining in the current window
X-RateLimit-Reset Unix timestamp when the rate limit window resets
Retry-After Seconds to wait before retrying (only included in 429 responses)

429 Too Many Requests

When you exceed your rate limit, the API returns a 429 status code with the following response:

429 Response
{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Please retry after the period specified in the Retry-After header.",
  "retry_after": 45
}
Best practice: Implement exponential backoff in your client. When you receive a 429 response, wait for the number of seconds specified in the Retry-After header before making another request.

Status Codes

Code Description
200Success
400Bad Request - Invalid parameters
401Unauthorized - Invalid API key
402Payment Required - Insufficient credits
429Too Many Requests - Rate limit exceeded
500Server Error