The API response for the POST /crm/v1/profiles endpoint does not conform to the API specification defined in crm.json#L22482. According to the spec, the status field is expected to be of type integer, but the actual response returns a string value ("NotProcessed").
Example Request:
POST {{HostName}}/crm/v1/profiles?profileName=%25&offset=1&limit=250Example Response:
{
"type": "Bad Request",
"title": "The maximum limit for this API is 200. However, it is currently being invoked with 250. Please ensure that your orchestration promptly aligns with the limit of 200.",
"status": "NotProcessed",
"detail": "The maximum limit for this API is 200. However, it is currently being invoked with 250. Please ensure that your orchestration promptly aligns with the limit of 200.",
"o:errorCode": "OPERAWS-ODE09998",
"language": "en"
}This discrepancy can cause unmarshalling or validation errors for clients relying on the API schema.
The API response for the POST
/crm/v1/profilesendpoint does not conform to the API specification defined in crm.json#L22482. According to the spec, the status field is expected to be of type integer, but the actual response returns a string value ("NotProcessed").Example Request:
POST {{HostName}}/crm/v1/profiles?profileName=%25&offset=1&limit=250Example Response:
{ "type": "Bad Request", "title": "The maximum limit for this API is 200. However, it is currently being invoked with 250. Please ensure that your orchestration promptly aligns with the limit of 200.", "status": "NotProcessed", "detail": "The maximum limit for this API is 200. However, it is currently being invoked with 250. Please ensure that your orchestration promptly aligns with the limit of 200.", "o:errorCode": "OPERAWS-ODE09998", "language": "en" }This discrepancy can cause unmarshalling or validation errors for clients relying on the API schema.