Forum Discussion
Solved
Push Datasets - Datasets PostDataset 'The request could not be processed due to missing or invalid
Has anyone encountered a 400 error when pushing data via a POST API since yesterday? We haven’t made any changes to the codebase for some time so we’re not sure if this is related to any serverside c...
Hi ejQap,
A 400 error on POST /datasets usually indicates that your JSON definition no longer passes schema validation or that the API has recently become more strict. It may also relate to authentication changes at tenant level. Validate the JSON structure carefully, test the request in the official API console, and confirm that your access token and permissions are still valid.Changes at tenant or Azure AD application level can cause:- expired or invalid tokens
- altered scopes
- loss of the Dataset.ReadWrite.All permission
In these cases, the service may return a 400 rather than a 403 due to the point at which validation fails.To confirm this, test a simple authorised request such as:If this also fails, the problem may relate to authentication rather than the payload.
