"HTTP/1.1 422 Unprocessable Entity" error

109 views
Skip to first unread message

jack.s...@gmail.com

unread,
Jan 4, 2018, 10:19:26 AM1/4/18
to Developer Group for QPP APIs
Colleagues,

I am hoping that someone can help me. I am trying to post a new submission to the test bed at https://qpp-submissions-sandbox.navapbc.com/submissions. This is my test post text:

{
  "entityType": "individual",
  "taxpayerIdentificationNumber": "000666666",
  "nationalProviderIdentifier": "0123012301",
  "performanceYear": 2017
}

That text when submitted to the Swagger site here: https://qpp-submissions-sandbox.navapbc.com/#/ works like a gem and I get a "201" code back and all is well. However, when I submit the same text from my server I get this header info back:

HTTP/1.1 422 Unprocessable Entity
Access-Control-Allow-Headers: Content-Type, X-Requested-With, Authorization
Access-Control-Allow-Methods: PUT, PATCH, GET, POST, DELETE, OPTIONS
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8
Date: Thu, 04 Jan 2018 14:19:41 GMT
ETag: W/"1f9-eNxckKKpqPRHw5q2nhPDbjAwksU"
Vary: Accept
X-Powered-By: Express
Content-Length: 505
Connection: keep-alive

And I get this in my output file:

{
  "error": {
    "type": "ValidationError",
    "message": "invalid submission object",
    "details": [
      {
        "message": "field 'entityType' in Submission is missing",
        "path": "$.entityType"
      },
      {
        "message": "field 'taxpayerIdentificationNumber' in Submission is missing",
        "path": "$.taxpayerIdentificationNumber"
      },
      {
        "message": "field 'performanceYear' in Submission is missing",
        "path": "$.performanceYear"
      }
    ]
  }
}


Does anyone have any suggestions? I am able to GET data readily from the test bed, but I can't POST due to the above.

Thanks,

Jack

Srini

unread,
Jan 8, 2018, 2:56:51 PM1/8/18
to Developer Group for QPP APIs
Hello,

Just wanted to check to see if this issue is resolved if you update XML as per the below posting?

https://groups.google.com/forum/#!topic/qpp-apis/nd_Qfdhr1vk

Jack @Duke

unread,
Jan 11, 2018, 1:33:10 PM1/11/18
to Developer Group for QPP APIs
Srini,

No, my post was in JSON and not XML format. I have heard nothing back.

Thanks,

Jack

Sarah White

unread,
Jan 11, 2018, 2:27:39 PM1/11/18
to Developer Group for QPP APIs
Hi Jack,

My understanding is that your requests are going through successfully through the public sandbox (https://qpp-submissions-sandbox.navapbc.com) and through clients like Postman. You are encountering issues when you are routing your request through an application that you’re building. If this is the case, the issue may be on your end, and the QPP API team cannot offer additional support beyond verifying whether this is a bug in the QPP Submissions APIs. 

However, we encourage other developers within the QPP Developer Community to chime in with ideas or past experience that might be helpful here.

abhijeet mahajan

unread,
Jan 11, 2018, 3:37:52 PM1/11/18
to Sarah White, Developer Group for QPP APIs
Please check the structure of request you are sending. Request structure is different in sandbox and production environment of CMS. I got this error when I used production structure in sandbox environment.

--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/qpp-apis.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/20950792-ef1d-4d55-abd8-eff35839b707%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jack Shostak

unread,
Jan 12, 2018, 7:20:19 AM1/12/18
to abhijeet mahajan, Sarah White, Developer Group for QPP APIs
Abhjeet,

Thanks very much. It sounds like I will just have to use the production environment for testing based on the issues I have seen posted so far. It seems like the sandbox and production environments behave differently.

Thanks very much,

Jack

--
You received this message because you are subscribed to a topic in the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qpp-apis/JqSQayq_EZQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qpp-apis+unsubscribe@googlegroups.com.

abhijeet mahajan

unread,
Jan 12, 2018, 7:36:35 AM1/12/18
to Jack Shostak, Sarah White, Developer Group for QPP APIs
No problem :-) Let us know if you find any such interesting errors or observations. Will help us as well. Not everything is documented for this API so we have to learn few things hard way..trial and error sometimes.

Shane Jarrell

unread,
Jan 15, 2018, 10:23:38 AM1/15/18
to Developer Group for QPP APIs
Can you define the two different structures you had to use, please? This sounds troubling.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages