POST /api/v2/outbound/contactlists returns 400 INVALID_VALUE despite valid JSON

Docs state: “The contact list name must be unique and the status must be either ‘ACTIVE’ or ‘INACTIVE’.” I’m trying to create a new outbound contact list via the REST API. The payload looks correct. I’ve validated it against the schema in the developer docs.

Here’s the request:

POST /api/v2/outbound/contactlists
Authorization: Bearer <token>
Content-Type: application/json

{
 "name": "Q3_Campaign_List",
 "description": "Test list for Q3 outreach",
 "status": "ACTIVE",
 "contactListType": "API",
 "wrapUpCodes": []
}

The response is a 400 Bad Request with this body:

{
 "message": "Invalid value for field: name",
 "status": 400,
 "code": "INVALID_VALUE",
 "errors": [
 {
 "message": "Invalid value for field: name"
 }
 ]
}

The name is unique. I checked the existing lists. No collisions. The status is valid. The type is valid. I even tried changing the name to something generic like “test123”. Same error.

I’m using Python with the requests library. The token is fresh. It works fine for other outbound endpoints. Getting contacts? Fine. Updating a list? Fine. Just creating one fails.

Is there a hidden constraint? The docs don’t mention special characters or length limits for the name field in this specific error context. I’ve seen this error before with invalid phone numbers in contact imports. But this is just the list metadata.

Any ideas what “Invalid value” refers to here? The error message is unhelpful. It doesn’t say why it’s invalid. Just that it is.

I’m stuck. The code is straightforward. The payload is minimal. Nothing fancy. Just a name and a status. Why is the API rejecting it?