In jetadmin it’s showing unexpected token “:” and doing same call on both side.
Has anyone else faced this issue?
In jetadmin it’s showing unexpected token “:” and doing same call on both side.
Has anyone else faced this issue?
Hi, I also need resolution for the same issue
The “Unexpected token ‘:’” error in JetAdmin usually means the body it is sending is not valid JSON for that request context, even though the raw call in Postman works. Two things worth checking: whether the request is being sent as a preformatted or raw value rather than parsed JSON, and whether any headers or query params in Postman are being dropped when you rebuild the call. Sharing the actual request definition, as asked above, would make it much easier to pin down where the payload differs.
The “Unexpected token ‘:’” detail points more at how the body is typed than at the endpoint itself, so I’d start there. In JetAdmin, confirm the body field is set to JSON rather than a preformatted string, since a stringified payload will fail to parse the same way. Then compare the rebuilt call against Postman line by line: content-type, auth, and any query params are the usual places something gets dropped. @Lakshay_Taneja, the actual request definition is really what’s needed to see where the two diverge.