A normal use case in Postman seems to be to generate a collection from an API. This lets you do things like importing an externally defined API, and then generating a collection of calls that you can then make from Postman. I have the converse situation. I have a complete Postman collection from an API provider, but no API definition. Is there anything like "Turn this collection into an API definition." in Postman?
I recommend starting here - https://github.com/joolfe/postman-to-openapi but we are also working on other solutions at Postman as well--stay tuned.
I've built a tool that allows you to do this for a GraphQL API. (https://www.npmjs.com/package/graphql-testkit)
You could simply do something like this
graphql-testkit \
--endpoint=https://api/spacex.land/graphql\
--header="Authorization:123,x-ws-system-id=10" \
--maxDepth=4
and it would automatically generate the collection for you.
Related
We're evaluating Istio and KrakenD for our API Gateway solution and trying to understand the differences in their functionality. One thing that stood out in the KrakenD docs is its ability to merge the content of multiple backend APIs into a single endpoint response to caller, as well as the ability to filter the content of responses, to remove "extra" data and/or change the names of attributes, etc. Trying to determine if Istio has similar capabilities but so far the Istio documentation hasn't been too helpful.
Does anyone has experience/info with this?
As of v1.16.x istio does not have capability of aggregation and transformation out of the box.
But it supports Proxy Extensions with WASM plugin.
That allows you to write custom code to decorate request/response.
You can use any language as long as it compiles to WASM.
https://events.istio.io/istiocon-2021/slides/c8p-ExtendingEnvoyWasm-EdSnible.pdf
https://istio.io/latest/docs/concepts/wasm/
We have a Postman collection. We want to verify data created from API in web. One way is we can integrate both in jenkins, but we want to perform all verification through nightwatch only. Is there any way to utilise Postman collection in Nightwatch?
In terms of using postman ‘in’ Nightwatch, you wouldn’t be able to do this I believe and I wouldn’t recommend it if you could.
If what you are saying is you want to be able to make api calls from within Nightwatch, then that is certainly possible and I’d recommend trying something like axios
I didn't find such kind of an information in your documentation so I would like to know if there any opportunities/tools for testing API for the whole diagram? like a set of API call one after another? Will it be OK if I put several rest API calls in one test method? Are there better approaches for doing that?
Thanks,
We didn't find any lib for that but we used RestAssured library for testing API calls.
I'm considering using GraphQL with a Django backend service but I couldn't find much information regarding the API documentation. I need some solution to dynamically generate the documentation, perhaps like npm's graphql-docs with a result similar to GitHub's API docs.
Is it feasible to accomplish with graphene-django? If not, what's a good alternative for a python environment?
Yes, it's very easy to do by using GraphiQL, which is embedded in to Graphene.
The instructions on how to integrate this with Graphene are here in the graphene-python documentation. --- basically you need to add the parameter graphiql=True when setting up the API route in your urls.py file.
After it is set up, if go to your API endpoint in your browser, you'll see a nice interface for sending API calls, getting API responses, and reading documentation for both queries and mutations. The documentation is initially hidden on the right until you click on the "< Docs" link.
I'm new to Facebook development. I'm working on migrating an existing app in accordance to the Graph API upgrade guide. I'm looking for guidance around calls such as api.facebook.com/method/Fql.multiquery.
My question is: does this type of API need to be upgraded as well, or does it only apply to graph.facebook.com calls? I want to ensure that api.facebook.com/method/Fql.multiquery calls will still work after 4/30/15.
You may want to take a look at the Batch Requests of the Graph API. You can also specify dependencies between the requests.
Calls to http://api.facebook.com/method/Fql.multiquery will no longer work. The REST API is long deprecated anyway.
As #luschn said, you have to migrate to the Graph APIs batch requests, and use the /fql endpoint. You can only use FQL if you have a v2.0 app, and not higher.