-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to submit collection through API #47
Comments
@Raja-Simha could you please help me troubleshoot this issue? |
Additionally, I am able to import same collection, JSON file through Postman application, but not through API. |
@amitdotagarwal can you share the collection json file you are trying to import? or a sample one if it doesnt have any sensitive information? |
really thanks for your response, please find attached, requested JSON file. |
@preethammavin The OpenAPI converter is converting the OAS spec to a valid collection. The Postman Collection file is importing correctly in the app, but not in the API (even using the POST /collection endpoint, which has nothing to do with openAPI). Probably linked to a transformer version mismatch across app/api/sync |
Attaching the Postman Collection V2 file that imports in the app but not in the API. |
@amitdotagarwal While we fix this in our converter, changing |
@amitdotagarwal We've pushed out a fix. Can you confirm you're able to import the collection through the API now? Closing the ticket - feel free to add a comment if you still face issues. |
I face similar issue. Flow:
I'm using this simple function to communicate with the API
Which results in the following errors:
While I can import the collection using the Postman Import option, without any problem. Should I send it to the API using different parameters or query string properties? |
Hi Team,
We need your help, we are trying post collection through API, and facing some strange issues. For your reference please find below code error and API key.
below is the code error
This is API request, I have API key
The text was updated successfully, but these errors were encountered: