Possible Error Codes When Consuming wolkvox CRM APIs

Updated at May 29th, 2026

+ More

Table of Contents

Introduction What does code 400 – BAD REQUEST mean? What does code 401 – UNAUTHORIZED mean? What does code 403 – FORBIDDEN mean? What does code 404 – NOT FOUND mean? What does code 405 – METHOD NOT ALLOWED mean? What does code 412 – PRECONDITION FAILED mean? What does code 416 – REQUESTED RANGE NOT SATISFIABLE mean? What does code 417 – EXPECTATION FAILED mean?

Introduction

When integrating external systems with wolkvox CRM through its APIs, you may receive responses with HTTP error codes that indicate what went wrong during the request. Understanding the meaning of each code helps you quickly identify and correct issues, whether they are related to authentication, submitted parameters, the method used, or system limits.

Below you will find all possible error codes organized by category, along with their response message and an explanation in English of the most likely cause.

What does code 400 – BAD REQUEST mean?

This code indicates that the submitted request could not be processed. This may be because the requested endpoint does not exist or because required parameters are missing from the URL or the request body.

CODE	MESSAGE	EXPLANATION
400 – BAD REQUEST	THE API YOU WANT TO CONSULT DOES NOT EXIST	The API endpoint you are trying to query does not exist. Verify the URL used.
400 – BAD REQUEST	SOME PARAMETERS ARE REQUIRED	Required parameters may be missing from the URL or the request body. Review the endpoint documentation to make sure all required fields are being sent.

What does code 401 – UNAUTHORIZED mean?

This code indicates that the request does not include authentication credentials. The wolkvox token must be sent in the header of each request.

CODE	MESSAGE	EXPLANATION
401 – UNAUTHORIZED	PLEASE ENTER THE WOLKVOX-TOKEN	The authentication token was not included in the request. Make sure to send the Wolkvox-Token header in each API request.

What does code 403 – FORBIDDEN mean?

This code indicates that the submitted token does not have permission to execute the requested action. This may be due to an invalid token, exceeding the daily usage limit, or making too many simultaneous requests with the same token.

CODE	MESSAGE	EXPLANATION
403 – FORBIDDEN	TOKEN LIMIT EXCEEDED	The allowed daily usage limit for the token has been exceeded. Wait until the counter resets or review your consumption plan.
403 – FORBIDDEN	EXCEEDS THE LIMIT OF SIMULTANEOUS REQUESTS PER TOKEN (2)	The same token is being used in more than 2 simultaneous requests. Only up to 2 concurrent requests per token are allowed.
403 – FORBIDDEN	PLEASE VALIDATE TOKEN	The submitted token is not valid. Verify that the value of the Wolkvox-Token header is correct and active.
403 – FORBIDDEN	INVALID TOKEN	The submitted token is not valid. Verify that it belongs to the correct operation and has not expired or been revoked.

What does code 404 – NOT FOUND mean?

This code may indicate several situations: no records were found for the applied filters, a referenced resource (agent, skill, campaign, connector) does not exist in the operation, the requested changes had already been made previously, or the allowed record limit based on active licenses is being exceeded.

CODE	MESSAGE	EXPLANATION
404 – NOT FOUND	VALIDATE DATES ENTERED	The endpoint is correct, but there are no records for the queried date range. Verify the dates entered.
404 – NOT FOUND	NO DATA FOUND	The endpoint is correct, but no data was found for the filters applied within the specified date range.
404 – NOT FOUND	CANNOT CREATE A NEW AGENT, THERE ARE SOME AGENTS WITHOUT INFORMATION	One or more agents in the operation have incomplete information. Complete the missing data before attempting to create a new agent.
404 – NOT FOUND	AGENTS EXCEED ASSIGNED LICENSES	It is not possible to create more agents because the limit of licenses assigned to the operation has been reached. The number of licenses must be increased.
404 – NOT FOUND	THIS AGENT DOES NOT EXIST IN YOUR OPERATION, TRY AGAIN	The referenced agent does not exist in the operation. Verify the agent identifier sent in the request.
404 – NOT FOUND	THIS CODE ALREADY EXISTS	The code you are trying to register already exists within the operation. Use a different code.
404 – NOT FOUND	REVIEW THE ERROR MESSAGE TO CORRECT POSSIBLE PROBLEMS	One of the submitted parameters may be misspelled or may have an incorrect format. Carefully review the name and value of each parameter.
404 – NOT FOUND	ERROR NO FOUND MOBIL WHATSAPP	The submitted ID does not correspond to a mobile WhatsApp connector. Verify that the connector identifier is correct and of the appropriate type.
404 – NOT FOUND	SKILL_ID X DOES NOT EXIST IN YOUR OPERATION.	The referenced skill does not exist in the operation. Verify the skill identifier sent in the request.
404 – NOT FOUND	CAMPAING_ID X DOES NOT EXIST IN YOUR OPERATION.	The referenced campaign does not exist in the operation. Verify the campaign identifier sent in the request.
404 – NOT FOUND	THE CAMPAIGN HAS NOT BEEN STARTED, PLEASE VALIDATE THE DATA	The campaign was already started. No changes were made because the requested status matches the current status.
404 – NOT FOUND	THE CAMPAIGN HAS NOT BEEN STOPPED, PLEASE VALIDATE THE DATA	The campaign was already stopped. No changes were made because the requested status matches the current status.
404 – NOT FOUND	THE CAMPAIGN HAS NOT BEEN UPDATED, PLEASE VALIDATE THE DATA	The changes you are trying to apply to the campaign had already been made previously. Validate the submitted data.
404 – NOT FOUND	THIS ACTION IS ALLOWED ONLY IN PEDICTIVE CAMPAIGNS	The requested action is only available for predictive campaigns. Verify the campaign type before executing this operation.
404 – NOT FOUND	NO RECORD HAS BEEN CODED, PLEASE VALIDATE THE DATA	No record was coded. Validate that the submitted data is correct and that the record exists in the system.
404 – NOT FOUND	YOU ARE UPLOADING (X) RECORDS TO THE SYSTEM. ACCORDING TO QUANTITY ACTIVE LICENSES, YOU CAN UPLOAD X. TRY AGAIN.	The number of records you are trying to upload exceeds the limit allowed based on the operation's active licenses. Reduce the number of records or increase the available licenses.
404 – NOT FOUND	X RECORDS HAS BEEN ADDED, PLEASE VALIDATE THE DATA	Not all records were added correctly. Some may have been omitted due to data errors. Validate the submitted information.
404 – NOT FOUND	THE CAMPAIGN RECORDS HAVE NOT BEEN DELETED, PLEASE VALIDATE THE DATA	The campaign records you are trying to delete had already been deleted previously or do not exist. Validate the submitted data.

What does code 405 – METHOD NOT ALLOWED mean?

This code indicates that the HTTP method used in the request is not the correct one for the queried endpoint. Each wolkvox CRM API only supports the HTTP method defined in its documentation.

CODE	MESSAGE	EXPLANATION
405 – METHOD NOT ALLOWED	ONLY THE USE OF THE GET METHOD IS ALLOWED IN THIS REQUEST	This endpoint only accepts requests using the GETmethod. Change the HTTP method in your request.
405 – METHOD NOT ALLOWED	ONLY THE USE OF THE POST METHOD IS ALLOWED IN THIS REQUEST	This endpoint only accepts requests using the POSTmethod. Change the HTTP method in your request.
405 – METHOD NOT ALLOWED	ONLY THE USE OF THE PUT METHOD IS ALLOWED IN THIS REQUEST	This endpoint only accepts requests using the PUTmethod. Change the HTTP method in your request.
405 – METHOD NOT ALLOWED	ONLY THE USE OF THE DELETE METHOD IS ALLOWED IN THIS REQUEST	This endpoint only accepts requests using the DELETEmethod. Change the HTTP method in your request.

What does code 412 – PRECONDITION FAILED mean?

This code indicates that the query exceeds the maximum limits allowed by the system, either in response size, number of records returned, or number of records submitted in a single upload. To resolve it, reduce the queried date range or split the upload into smaller batches.

CODE	MESSAGE	EXPLANATION
412 – PRECONDITION FAILED	YOUR QUERY EXCEEDS THE SIZE LIMIT (200 MB), PLEASE DECREASES THE RANGE OF DATES	The query generates a response that exceeds the 200 MB limit. Reduce the date range to obtain a smaller result.
412 – PRECONDITION FAILED	YOUR QUERY EXCEEDS THE RECORDS LIMIT (60000), PLEASE DECREASES THE RANGE OF DATES	The query returns more than 60,000 records, which exceeds the allowed limit. Reduce the date range to obtain fewer results per request.
412 – PRECONDITION FAILED	YOUR QUERY EXCEEDS THE RECORDS LIMIT (10000), PLEASE DECREASES THE RECORDS NUMBERS	You are trying to upload more than 10,000 records in a single request. Split the upload into batches of up to 10,000 records.

What does code 416 – REQUESTED RANGE NOT SATISFIABLE mean?

This code indicates that there is an issue with the date range sent in the request: it may be in an incorrect format, the start date may be greater than the end date, or the range may exceed the maximum number of days allowed for that endpoint.

CODE	MESSAGE	EXPLANATION
416 – REQUESTED RANGE NOT SATISFIABLE	THE VALID FORMAT FOR THE (DATE_INI) IS YYYYMMDDHHIISS (20211103164009)	The start date (DATE_INI) does not have the correct format. The required format is YYYYMMDDHHIISS. Example: 20211103164009.
416 – REQUESTED RANGE NOT SATISFIABLE	THE VALID FORMAT FOR THE (DATE_END) IS YYYYMMDDHHIISS (20211103164009)	The end date (DATE_END) does not have the correct format. The required format is YYYYMMDDHHIISS. Example: 20211103164009.
416 – REQUESTED RANGE NOT SATISFIABLE	DATE_INI CANNOT BE GREATER THAN DATE_END	The start date is greater than the end date. Correct the range so that DATE_INI is earlier than DATE_END.
416 – REQUESTED RANGE NOT SATISFIABLE	THE VALID FORMAT FOR THE (RECALL_DATE) IS YYYYMMDDHHIISS (20211103164009)	The callback date (RECALL_DATE) does not have the correct format. The required format is YYYYMMDDHHIISS. Example: 20211103164009.
416 – REQUESTED RANGE NOT SATISFIABLE	YOU CAN ONLY MAKE INQUIRIES FOR A MAXIMUM OF 31 DAYS	The submitted date range exceeds the maximum allowed limit of 31 days for this endpoint. Adjust the range so it does not exceed that limit.
416 – REQUESTED RANGE NOT SATISFIABLE	YOU CAN ONLY MAKE INQUIRIES FOR A MAXIMUM OF 1 DAY FOR THIS API	This endpoint only allows querying a maximum of 1 day per request. Adjust the date range accordingly.

What does code 417 – EXPECTATION FAILED mean?

This code is exclusive to WhatsApp-related operations. It indicates that the message could not be sent because certain conditions were not met: the template does not exist, the interaction with the customer has not been initiated, more than 24 hours have passed since the last message, the number has an incorrect format, or there was a connectivity issue with the server or database.

CODE	MESSAGE	EXPLANATION
417 – EXPECTATION FAILED	ERROR NO FOUND TEMPLATE WHATSAPP	The referenced WhatsApp template does not exist. Verify the template identifier before sending it.
417 – EXPECTATION FAILED	UNABLE TO SEND THE MESSAGE NO INTERACTION HAS BEEN INITIATED	No interaction has been initiated with the customer. An approved template must be sent first to open the conversation.
417 – EXPECTATION FAILED	UNABLE TO SEND THE MESSAGE THERE IS NO CHAT WITH THE CUSTOMER	There is no active chat with the customer. A template must be sent beforehand to start the conversation.
417 – EXPECTATION FAILED	UNABLE TO SEND THE MESSAGE THE CLIENT HAS NOT RESPONDED YET	The customer has not yet responded to the previously sent message. It is not possible to continue the messaging flow until their response is received.
417 – EXPECTATION FAILED	IT WAS NOT POSSIBLE TO SEND THE MESSAGE MORE THAN 24 HOURS HAVE PASSED	More than 24 hours have passed since the last template message was sent to the customer. The conversation window has expired. Send a new template to reactivate it.
417 – EXPECTATION FAILED	NUMBER LESS THAN 7 DIGITS	The submitted phone number has fewer than 7 digits and is not valid. Verify the recipient's number.
417 – EXPECTATION FAILED	UNABLE TO CONNECT	It was not possible to establish a connection to the database. Try again later.
417 – EXPECTATION FAILED	COULD NOT SEND TEMPLATE	The template could not be sent because one had not been sent to the customer previously. Make sure to always start the conversation with an approved template.
417 – EXPECTATION FAILED	NO RECORD INSERTED	It was not possible to insert the record into the database due to a connectivity issue. Try again later.
417 – EXPECTATION FAILED	MESSAGE COULD NOT BE SENT	It was not possible to send the message due to a connectivity issue with the affected server. Try again later.
417 – EXPECTATION FAILED	NOT SENT MESSAGE: THE NUMBER OF VARIABLES IS: X	The message was not sent because the number of variables submitted does not match the number of variables expected by the template. Review the number of parameters sent.
417 – EXPECTATION FAILED	MESSAGE HAS NOT BEEN SENT	The message could not be sent. Verify the status of the WhatsApp connector and the request data.

wolkvox crm api errors