Weird behavior with service request's custom fields

Hey guys.
I’m trying to create a service request through API, but the API returns 400 error:

{
“description”: “Validation failed”,
“errors”: [
{
“field”: “tipo_de_solicitacao_para_ramal_-_atendimento_resolutivo”,
“message”: “Unexpected/invalid field in request”,
“code”: “invalid_field”
}
]
}

But when I try to make this API without that custom field, the API returns 400 error with another field:

{
“description”: “Validation failed”,
“errors”: [
{
“field”: “ipo_de_solicitacao_para_ramal_-_atendimento_resolutivo”,
“message”: “Unexpected/invalid field in request”,
“code”: “invalid_field”
}
]
}

But the field "ipo_de_solicitacao_para_ramal_-_atendimento_resolutivo" without “t” at the beginning doesn’t exist.

Have you ever faced this kind of issue? If so, how did you solve it?

Thank you!

Hi @omarcelo,

Based on the error message, I guess the field doesn’t exist in the portal. With “t” or without, the error doesn’t change though.
Could you verify if the right field exists in the portal and the spelling is correct?

If the field exists and the request suppose to accept this field, could you attach the code snippet of making the API with this field in the body? Also, any screenshot of this field appearing from the portal?