Reference
Errors and Validation
Error handling, validation responses, and troubleshooting
Teamfluence API uses standard HTTP response codes. Successful requests return 2xx codes and JSON payloads.
Common Status Codes
| Code | Meaning |
|---|---|
| 200 | Success |
| 401 | Missing or invalid bearer token |
| 403 | Access denied for current workspace/user |
| 404 | Resource not found |
| 422 | Validation error |
| 5xx | Server-side failure |
Validation Error Format
When request validation fails, endpoints return an HTTP 422 payload in this shape:
{
"detail": [
{
"loc": ["body", "status"],
"msg": "Input should be 'NEW', 'QUALIFIED' or 'DISQUALIFIED'",
"type": "enum",
"input": "INVALID_STATUS",
"ctx": {}
}
]
}ValidationError Fields
| Field | Type | Description |
|---|---|---|
| loc | array[string|integer] | Path to invalid value |
| msg | string | Human-readable validation message |
| type | string | Error category |
| input | any | Received invalid input |
| ctx | object | Optional context |
Troubleshooting Checklist
- Confirm your base URL is https://api.teamfluence.com and endpoint begins with /v2.
- Confirm Authorization header is exactly Bearer <token>.
- Confirm date fields use ISO date format: YYYY-MM-DD.
- Confirm enum values are valid, especially lead status and sort_by.
- For paginated leads calls, pass cursor exactly as returned by previous response.