API error - Please help

Tony Freeman

I am submitting the following json string to the API ("NETOAPI_ACTION", "GetItem")

{"Filter":{"SKU":"10-0101","IsActive":"True","OutputSelector":"Name"}}

I get the following error returned:

{

"CurrentTime": "2023-07-28 07:37:05",

"Ack": "Error",

"Messages": [{

"Error": [{

"Message": "Error",

"SeverityCode": "Error",

"Description": "malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before \"Filter={\"Filter\":{\"S...\")"

}, {

"Message": "JSON Error",

"SeverityCode": "Error"

}]

}

Find more posts tagged with

Accepted answers

Tony Freeman

It was a encoding issue .. all good now

All comments

Erik Merkley

That's a valid JSON string, so the problem is elsewhere in your code.

The error "at character offset 0 (before \"Filter= ..." is quite suspicious, that doesn't appear in the string you posted above. Check you are creating the JSON correctly.

I'd suggest using a tool like Postman to experiment and get familiar with the API first, then convert it to code. Then you know that you have the calls exactly right and you'll know what to expect in responses.

Deactivated Member

Hi Tony. Welcome to the Community.

I understand you are facing an API error while trying to make a request to the "NETOAPI_ACTION" with the action "GetItem." The error seems to be related to the JSON syntax of your request. As Erik responded that it is a valid JSON String, our team has also reviewed your JSON string and found that it looks fine when properly formatted as follows:

{

"Filter": {

"SKU": "10-0101",

"IsActive": "True",

"OutputSelector": "Name"

}

The issue is likely not with the JSON body itself but might be related to either the request headers or how you are sending the request.

I hope this helps. Feel free to reach out to the community with more specific details about your code, the request, and any error messages you receive. This will allow the community to provide further assistance in resolving the problem.

Tony Freeman

It was a encoding issue .. all good now