ContributionsMost RecentMost LikesSolutionsRe: HTTP error 400 from Quickbase REST apiMakes sense. Both our issues seem to map back to Quickbase making a stealthy change to the REST api where it's less tolerant of format errors in the request. ------------------------------ Kerry Schwab ------------------------------ Re: HTTP error 400 from Quickbase REST api Ours turned out to be that we were passing the value for mergeFieldId in the JSON as a string, like: 'mergeFieldId': '6' Changing it pass as an integer (no quotes) fixed it: 'mergeFieldId': 6 Quickbase does have it documented as needing to be an integer, but allowed the string up until today. Seem like they pushed some sort of unannounced update with stricter type checking of the JSON. So you might want to check for similar issues with other things. Like, for example, "fieldsToReturn" should be an array of ints, and not an array of strings. Edit: I checked, and we're using lowercase 'value', and it's working after my above fix. ------------------------------ Kerry Schwab ------------------------------ HTTP error 400 from Quickbase REST api Suddenly, several scripts we have that use the Quickbase rest api are getting 400 errors when trying to update data. No changes on our side, it just started failing around noon PST. Anyone else seeing problems, specifically with UPDATES via the REST (not XML) api? ------------------------------ Kerry Schwab ------------------------------