Unexpected token F in JSON at position 0

giri-zano · January 19, 2026, 10:06pm

I have a couple of jobs running every day since 2021. As of Friday 16-th, they all return the following error

Unexpected token F in JSON at position 0

I have inspected the returned JSON and there is no unexpected token on POS 0.This used to be an old bug, from 2022 or 23, from memory, and it obviously has returned.

It happens in getJSON.

Anyone experiencing the same?

giri-zano · January 23, 2026, 12:31pm

Turns out the Wix IP’s (on AWS?) are suddenly being blocked by the endpoint-provider I use. The “F” is the first letter of the text-string that is returned (“Forbidden”). Solved it by switching data-provider.

Topic		Replies	Views
Error: Unexpected token : in JSON at position 5 Ask the community code , question	1	162	March 23, 2023
failed to get data from (new) server syntaxerror unexpected token in json at position 0 Ask the community code , question	4	335	May 31, 2020
Failed to get data from (new) server: SyntaxError: Unexpected token < in JSON at position 0 Ask the community code , question	0	90	April 29, 2020
Unexpected token < in JSON at position 0" Ask the community code , wix-members-area , question	13	549	August 26, 2020
Parsing Error: Unexpected Token ; Ask the community code , wix-stores , question	13	318	February 24, 2021

Unexpected token F in JSON at position 0

Related topics