Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.plura.ai/llms.txt

Use this file to discover all available pages before exploring further.

Response Format

All errors return this structure:
{
  "status": "failed",
  "message": "Human-readable error description"
}

HTTP Status Codes

CodeMeaningAction
200SuccessRequest completed
400Bad RequestCheck your JSON format and required fields
401UnauthorizedVerify your API key is correct
404Not FoundCheck Journey ID, Agent ID, or Lead ID
409ConflictResource already exists or state conflict
429Rate LimitedSlow down — implement exponential backoff
500Server ErrorRetry with backoff (temporary issue)

Common Issues

ProblemCauseSolution
”Workflow not found”Using Flow ID instead of Journey IDExtract Journey ID from URL: /journey/[ID]/
”Could not find or create lead”Phone missing or invalidUse E.164 format: 17145551234
”Unauthorized”Bad API keyRegenerate in Settings → API Keys
Custom fields won’t saveFields don’t exist in workspaceCreate in Settings → Custom Fields first
Call won’t initiateBad phone formatStrip all non-digits, add country code
”Invalid agent”Wrong Agent IDCopy exact UUID from workspace

Rate Limiting

Exceeding the rate limit returns a 429 response. Implement exponential backoff to handle it gracefully.
Best practices:
  • Start with 5 requests/minute max
  • Implement exponential backoff: 2s → 4s → 8s
  • Add random jitter to prevent thundering herd
  • Contact support for enterprise rate limits