JSON Feed Throws AJAX Error Because of Expected Array in JsonPathParser

I tried your configuration and I could reproduce the issue!

I found out that the configured context doesn't match with the JSON data. Instead of $.event.*, use $.event as context in your case.

Apparently, $.event.* should be used when your JSON is structured as follows:

{
  "event": [
    {
      "id": 1234,
      "title": "Foo"
    },
    {
      "id": 1235,
      "title": "Bar"
    },
    {
      "id": 1236,
      "title": "Baz"
    }
  ]
}

But your JSON looks like this:

{
  "event": {
    "id": 1234,
    "title": "Foo"
  }
}

When the context query is executed, it should return the rows to import. If context is $.event.*, then the rows from the first JSON example are:

1. {
       "id": 1234,
       "title": "Foo"
   }
   

2. {
       "id": 1235,
       "title": "Bar"
   }
   

3. {
       "id": 1236,
       "title": "Baz"
   }
   

From the second example, the rows would be instead this:

1. 1234
2. Foo

And these are not arrays, which a row should be.

It would be cool though if this would error in a more friendly way instead of "An AJAX HTTP error occurred."

Thanks, @megachriz! I'm much more familiar with XML. Your super-clear explanation got me reviewing JSON path syntax so that I was able to build out my mappings pretty quickly.

It would be great, as you say, to trap Ajax/500 errors and to direct the user to review the logs instead, where the real insight into the problem is.

-- Mark