Parsing error: syntax error: unexpected line terminator

monday Apps & Developers
, , , ,
1

Hello, good day everyone. I have two different applications that use the monday API to create items within a board and today they simply stopped working (Yesterday they were still working) and show this error when sending requests to create an item:
{
“errors”: [
{
“message”: “parsing error: syntax error: unexpected line terminator”,
“locations”: [
{
“line”: 6,
“column”: 40
}
],
“extensions”: {
“code”: “PARSING_ERROR”
}
},
{
“message”: “parsing error: syntax error: expected a valid Value”,
“locations”: [
{
“line”: 18,
“column”: 25
}
],
“extensions”: {
“code”: “PARSING_ERROR”
}
}
],

this is an example of a request i sent:
{“query”:“mutation { \n create_item (\n board_id: 4485776595, \n group_id: "grupo_nuevo", \n item_name: "Emma",\n column_values: "{\"date4\": \"2024-10-24\", \"phone\": \"\", \n \"dup__of_pescado\": \"2\", \"dup__of_lim_n\": \"0\", \n \"numbers52\": \"0\", \"dup__of_menta\": \"0\", \n \"n_meros__1\": \"0\", \n \"personas\": \"31119901\", \"estado_19\": \"Congreso Internacional de Pediatría\", \n \"n_meros\": \"0.00\", \"estado_18\": \"Sin Efecto Fiscal\", \n \"estado_1\": \"No\", \"estado_165\": \"No\", \n \"estado_11\": \"No\", \n \"texto\": \"Selecciona una Especialidad\", \"texto8\": \"\",\n \"tel_fono_1\": \"\", \"dup__of_colonia\": \"\", \n \"dropdown9\": \"Seleccione un Estado\",\n \"metodo_de_pago\": \"Transferencia\"}"\n ) { \n id \n }\n }”}

Has anyone started experiencing any similar errors when using the API?

2

Hi @Emma2324,

Welcome to the community!

I found this recent thread that describes the exact error that you’re getting! Are you also using make.com?

Best,
Rachel

3

Hello Rachel,

This is unrelated to make.com.

The issue is actually pretty straightforward: the \n is no longer supported in query.

For example, in python:

query = “”"
mutation {
create_update (item_id: %s, body: “%s”) {
id
}
}
“”" % (ITEM_ID, UPDATE_TEXT)

If UPDATE_TEXT includes \n, it will trigger the parsing error. In this specific case, replacing the \n with the HTML tag
does the job. But existing code systematically breaks.

This behaviour appeared just a few days ago.

4

Hi @Yoeld,

At first glance, this could be related to updates made to the parser (see here).

If not or if you still have an issue/questions, I suggest opening a support ticket here so our team can do a deeper investigation!

Best,
Rachel

5

Why would a potentially breaking change to the API be released in the middle of a version cycle instead of included in the next release? Just going to say, this isn’t how its supposed to be done.