Upload to Postman completed with status: 400 - Bad Request

[PaulCluver]

Hi there Portman community,

Hopefully someone can help me here. I am trying to automatically sync my generated postman collection to postman and I keep getting the following error:

Debugging this a bit deeper, the following error is being returned from the PostmanAPIService:

[thim81]

hi @PaulCluver

To not overload the Postman API when syncing the generated Postman collections, Portman keeps a local cache of the workspaces and collections in the workspace.

It might be that there is something off in the cache which causes the error to occur.

Some CLI options to try:

--postmanRefreshCache      Postman sync will refresh all local cached Postman API data (default: false)     [boolean]
--postmanFastSync          Postman sync creates new collection (new UID),instead of update (default: false) [boolean]

If none, of this works, could you try to find the file .portman.cache.json (usually in the "tmp" folder), and remove that file?
Portman will try to rebuild the cache on the next sync towards Postman.

[PaulCluver]

Hi Tim,

Thanks so much for the advice. I will give it a whirl and revert back.

Kind regards,
Paul.

[PaulCluver]

Hi Tim,

Unfortunately, none of the above suggestions worked. I will keep digging and update this post when I have found the root cause of the 400 response.

Kind regards,
Paul

[thim81]

Can you try to remove the collection from the Postman app?

[PaulCluver]

I have tried to remove the collection. The strange thing is that I can manually import it without any exceptions.

[thim81]

Sometimes the postman API has it quirks.

Some more options to try out:

• verify if the API key is still valid
• Remove the collection from Postman, be sure to remove it from the postman trash since it is soft-deleted. Next remove the Portman cache file

[PaulCluver]

Hi Tim,

After a bit of debugging a bit, I decided to extract the values being sent to the below method:

I then went into my Postman instance and tried to update the collection using the portman generated postman collection. This revealed a malformedRequestError as detailed below:

I do not believe this to be an issue with Portman. Rather, it is related to the API spec file which is being built and maintained in Mulesoft. I fixed this by simply adding the following to the API spec before sending the file to Portman.

Kind regards,
Paul

[thim81]

hi @PaulCluver

We only recently introduced the inclusion of the Postman info.version data, which in your case did not properly got convert.
So that might be a bug.

Could you share what your OpenAPI info looks like?
Does it have a version?

[PaulCluver]

Hi Tim,

Please find below the version information:

Regards,
Paul

[thim81]

That is interesting, we will add a test case and try to improve the version conversion to handle the swagger2 versioning.

[thim81]

hi @PaulCluver

We have a PR ready that should solve the "version":"v1" and other version related cases.