Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,857 questions
Error while saving Logic app custom connector of open api definition
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 31%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAN%3C/text%3E%3C/svg%3E)
Avinash Ninamohina
1
Reputation point
I have created a logic app custom connector with an open definition file but its showing below error while saving and all the actions look perfect without any error.
{"Code":"","Message":"PUT https://logic-apim-eastus.management.azure-api.net/apis/75337ea703654c0487ac46688e8937ed?import=true&protocols=https&protocols=http&path=apim/75337ea703654c0487ac46688e8937ed&api-version=2014-02-14 failed with BadRequest, content={\"error\":{\"code\":\"ValidationError\",\"message\":\"One or more fields contain incorrect values:\",\"details\":[{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): Property 'requestBody' has not been defined and the schema does not allow additional properties. Path 'paths['/{connectionId}/api/claimdetails'].post.requestBody', line 22, position 22.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails'].post.responses.201', line 42, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails'].post.responses.400', line 52, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails'].post.responses.401', line 65, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].get.responses.200', line 112, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].get.responses.401', line 122, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].delete.responses.401', line 161, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): Property 'requestBody' has not been defined and the schema does not allow additional properties. Path 'paths['/{connectionId}/api/claimdetails/{id}'].put.requestBody', line 196, position 22.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].put.responses.200', line 216, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].put.responses.400', line 226, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/{id}'].put.responses.401', line 239, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/'].get.responses.200', line 271, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): JSON is valid against no schemas from 'oneOf'. Path 'paths['/{connectionId}/api/claimdetails/'].get.responses.401', line 284, position 18.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): Property 'openapi' has not been defined and the schema does not allow additional properties. Path 'openapi', line 307, position 12.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): Property 'components' has not been defined and the schema does not allow additional properties. Path 'components', line 308, position 15.\"},{\"code\":\"ValidationError\",\"target\":\"representation\",\"message\":\"Parsing error(s): The input OpenAPI file is not valid for the OpenAPI specificate https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md (schema https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v2.0/schema.json).\"}]}}","Target":null,"Details":[],"Innererror":null}
{count} votes
-
MayankBargali-MSFT 68,656 Reputation points2020-07-16T03:14:58.857+00:00 Can you please confirm whether you are using the UI or not to create it?
If not looks like this open API spec is not valid and you can try to use swagger to validate it before using it. -
MayankBargali-MSFT 68,656 Reputation points
2020-07-21T03:28:04.947+00:00 Want to touch base and see if you got a chance to look into my previous comment.
-
Avinash Ninamohina 1 Reputation point
2020-07-22T09:28:10.287+00:00 I am using Swagger UI to generate the Open API Swagger JSON file. Developed the API in VS2019 in .net core 3.1 version using API template and used Swagger 5.0 Nuget package. I did not validate it Please help me to validate the swagger. If possible I will share the Open API file regarding the API.
I have been using this API to update details in COSMOSDB its working fine and running this through Postman also providing results. -
MayankBargali-MSFT 68,656 Reputation points
2020-07-23T03:38:23.03+00:00 Sure. Please send an email with the subject line “Attn:Mayank” to AzCommunity[at]Microsoft[dot]com referencing this thread along with your Azure subscription ID and swagger file. I will have a look at the file and update you with my findings.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 86%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERG%3C/text%3E%3C/svg%3E)
Rajakumar Ganesan 1 Reputation point2021-03-03T02:22:04.257+00:00 Hi @MayankBargali-MSFT , I am facing the exact same error. Can you help with the solution. For easy of analysis, I will send you the swagger file as mentioned in the above comment. Please help me solve this error.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 65%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
Trey Pogue 20 Reputation points2023-11-15T23:15:47.9333333+00:00 Did anyone get an answer for this? I'm having the same issue, thinking that my JSON doesn't match the API specified in the base url?
Sign in to comment