The endpoint is /api/v2/outbound/contactlists. Every time the backend service fires a POST request, the server responds with a 400 Bad Request and the error code INVALID_VALUE. The payload points directly at the name field as the culprit. That doesn’t make much sense since the value is just a plain alphanumeric string.
Here is the JSON going over the wire:
{
"name": "Q3_Campaign_Test",
"description": "Automated import for routing",
"columns": [
{
"name": "phone_number",
"dataType": "STRING",
"label": "Phone"
}
],
"contactType": "INTERACTIVE_VOICE",
"contactSource": "API"
}
I’ve checked the Swagger docs and the schema looks fine. The name field accepts underscores. Stripping it down to TestList123 still triggers the exact same error. The request headers have Content-Type: application/json and the OAuth token is definitely valid since other outbound calls work perfectly.
My reasoning goes like this. Step one: verify the string format. The API expects name: string and I’m passing const listName = 'Q3_Campaign_Test'. Step two: check for duplicates. I ran a query against /api/v2/outbound/contactlists and got an empty array. Step three: inspect the schema validation logic. If INVALID_VALUE fires, it usually means the platform is rejecting a hidden constraint. I tried wrapping the payload in a try/catch block and logging error.response.data.errors[0].message. The output just repeats INVALID_VALUE without pointing to a specific rule. Maybe the columns array structure is interfering with the name validation. Or perhaps there is a required field missing that the error message completely ignores. The docs mention contactType and contactSource are optional on creation, but I included them just in case. I don’t see why it’s failing on a basic string. Headers are set correctly. Token is fresh. Still getting blocked. The raw response headers show a correlation id that points back to the same validation layer without giving a clear path forward. The stack trace just cuts off at the validation layer and the logs don’t show any nested schema mismatches.