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

CodeMeaning
200Success
401Missing or invalid bearer token
403Access denied for current workspace/user
404Resource not found
422Validation error
5xxServer-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

FieldTypeDescription
locarray[string|integer]Path to invalid value
msgstringHuman-readable validation message
typestringError category
inputanyReceived invalid input
ctxobjectOptional context

Troubleshooting Checklist

  1. Confirm your base URL is https://api.teamfluence.com and endpoint begins with /v2.
  2. Confirm Authorization header is exactly Bearer <token>.
  3. Confirm date fields use ISO date format: YYYY-MM-DD.
  4. Confirm enum values are valid, especially lead status and sort_by.
  5. For paginated leads calls, pass cursor exactly as returned by previous response.