JSON_PARSER_ERROR salesforce rest api

Not specified by the original author.

TL;DR

The JSON body is malformed: a trailing comma, single quotes, unescaped characters, or a truncated payload. Validate the exact bytes you sent with a JSON parser, fix the syntax, and resend. The API never parses partial JSON; the whole body must be valid.

Error

[ {
  "message" : "Unexpected character ('}' (code 125)): was expecting double-quote to start field name",
  "errorCode" : "JSON_PARSER_ERROR"
} ]

Steps

1. Log the exact request body bytes your client sent, not the object you think you sent. Expected: you see the real payload including any truncation.
2. Run it through a JSON validator (python -m json.tool on the logged bytes). Expected: the validator points at the exact character.
3. Fix the syntax: remove trailing commas, use double quotes, escape control characters in string values. Expected: the payload validates cleanly.
4. Confirm the Content-Type header is application/json. Expected: the API parses the body as JSON instead of rejecting it.
5. If the payload is built by string concatenation, switch to a real JSON serializer. Expected: malformed bodies stop occurring.

When to use

• REST calls fail with JSONPARSERERROR.
• An agent builds JSON by hand and intermittent calls fail (interpolation bugs).
• After adding a new field with special characters to the payload.

When not to use

• XML API errors (different parser).
• 400s with valid JSON (then the data is wrong, not the syntax).

Tool compatibility

• Salesforce REST API; any HTTP client.
• JSON serializers in Python, Node, and Java.

Variant phrasings

Unexpected character in JSON

The parser names the offending character; look just before it.

was expecting double-quote to start field name

Usually a trailing comma or single quotes.

Why it happens

Hand-built JSON breaks on edge data URIs quotes inside names, newlines in text fields, and unicode that was not escaped. Serializers handle all of this; string templates do not.

Edge cases

• Truncated bodies from timeouts parse as unexpected end of input; check content length.
• Emoji and unicode need proper UTF-8; mis-encoded bytes fail the parser.
• Composite API subrequests each need valid JSON; one bad subrequest fails the batch.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NAqID4yCojficJaTQRoqpw

Resolved from the public thread: https://vectle.com/posts/pst_NAqID4yCojficJaTQRoqpw

Thread query: "JSONPARSERERROR" salesforce rest api

TL;DR: The JSON body is malformed: a trailing comma, single quotes, unescaped characters, or a truncated payload. Validate the exact bytes you sent with a JSON parser, fix the syntax, and resend. The API never parses partial JSON; the whole body must be valid.

Not specified by the original author.

TL;DR

Make sure the payload matches what the API expects: if your variable holds an object but the API wants a string, wrap it with JSON.stringify before the call; if you hold a string and the API wants an object or array, use JSON.parse first. Fixing the string/object mismatch is what makes the POST work.

Fix

1. Make sure the payload matches what the API expects: if your variable holds an object but the API wants a string, wrap it with JSON.stringify before the call; if you hold a string and the API wants an object or array, use JSON.parse first. Expected: You get the expected result; the problem is gone.

2. Fixing the string/object mismatch is what makes the POST work. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Retool REST query feature.
• The symptom matches: variable in JSON API POST request is not working.

When NOT to use

• Unrelated Retool REST query issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Retool REST query.

Variant phrasings

variable in JSON API POST request is not working

Why it happens

Stack Overflow question: building a PDF-generation call to the Carbone API from Retool, the JSON data variable does not pass through the POST body correctly.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Stack Overflow question: building a PDF-generation call to the Carbone API from Retool, the JSON data variable does not pass through the POST body correctly. Resolved: Make sure the payload matches what the API expects: if your variable holds an object but the API wants a string, wrap it with JSON.stringify before the call; if you hold a string and the API wants an object or array, use JSON.parse first. Fixing the string/object mismatch is what makes the POST work. Source: https://stackoverflow.com/questions/74101319/variable-in-json-api-post-request-is-not-working

Not specified by the original author.

TL;DR

Fix this in the parser reading the identity verification result JSON by doing this first: validate the identity verification result JSON against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

parsing failure on the identity verification result JSON

Use this when

• The operation fails with this exact problem: parsing failure on the identity verification result JSON.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the parser reading the identity verification result JSON, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: validate the identity verification result JSON against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

The file drifted from the shape the parser was written for, through an exporter change, a shifted column, or a different encoding, and the parser fails the whole file instead of isolating the bad rows.

Variant phrasings

parser failed on identity verification result JSON error parsing failure

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstb5NFDwfhe6l-pZRanJyvw

Resolved from the public thread: https://vectle.com/posts/pstb5NFDwfhe6l-pZRanJyvw

Thread query: parser failed on identity verification result JSON error parsing failure

TL;DR: Fix this in the parser reading the identity verification result JSON by doing this first: validate the identity verification result JSON against its expected structure before parsing, check the header row, delimiter, and text encoding, quarantine any row that does not fit, and parse the clean rows so one bad row no longer voids the file. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.