The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trello Rest API Has Validation Errors

Userowl Bot
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 30, 2024

Trello REST API has some validation errors, which prevents me using it without manually fixing the errors. This is the file I am using, which is latests on documentation page https://dac-static.atlassian.com/cloud/trello/swagger.v3.json?_v=1.573.0


First is from codegen, second screenshot is from swagger hub. 
CleanShot 2024-11-30 at 22.59.10@2x.pngCleanShot 2024-11-30 at 22.59.55@2x.png

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Augusto Lisboa
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 2, 2024

Hi Team, 

It seems that you're facing two issues:

1. Declared path parameter "idCard" needs to be defined as a path parameter at either the path or operation level (Error 5584)

This error means the idCard parameter is likely referenced in the path (for example, /cards/{idCard}) but isn't properly defined as a path parameter in the parameters section of the corresponding path or operation.

Solution: Locate the path or operation that uses idCard. In its parameters section, ensure there's an entry for idCard with in: "path".

https://stackoverflow.com/questions/27155516/swaggerissue-with-path-parameter

2. Operations must have unique operationIds (Errors 9621 and 9672)

This indicates that you have at least two operations (likely different HTTP methods like GET or POST) within the same path that share the same operationId. operationId is used by code generators to create method names, so they must be unique.

Solution: Find the operations reported with duplicate operationIds. Give each operation a distinct operationId. For example, if you have two GET requests under /cards/{idCard}, you could have operationIds like getCard and getCardAttachments. https://stackoverflow.com/questions/43878653/cannot-have-multiple-operations-with-the-same-operationid-clearcache

 

I'm unfamiliar with Swagger, so I'm sorry if the suggestion isn't accurate.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events