I am using Postman to house my API definitions and collections. I know that you are able to update collections via Postman's custom version control (fork, merge, etc.). This works wonderfully except for when I regenerate the collection from the API definition, any previously merged changes are gone.
Is there any way to update an API's definition while using Postman's version control? It has been such a nice feature for my team that I do not want to give it up.
Related
I am developing a REST API using C#/ASP .NET Core. As part of this, I am using Swagger to generate OpenAPI specifications to represent all of the models and endpoints that this API exposes.
When I want to test these endpoints locally using Postman, I need to go through the process of opening the web browser to https://localhost:xxxx/swagger/v1/swagger.json to access the spec, I then need to copy it, go to Postman and follow Collections -> Import -> Raw text -> paste -> Continue. Then I need to set the global collection variables like the URL over and over as it's wiped every time a new collection is imported.
This gets very arduous when you are making quick small changes that need to be tested.
Is there any way to get Postman to automatically update its copy of a collection when a new local build of the ASP .NET Core solution succeeds? Or the reverse - somehow getting Visual Studio to 'push' the updated local spec to Postman?
I know this may be a stretch, just wondering if anyone else has come across this problem before. Thanks!
I'm trying to use a Google API for a project, but I have a problem ;
Sometimes, there are versions like v1beta, v4.3, v2alpha2.5 etc, guessable but I don't want to bruteforce it to find the versions.
So I was wondering, how to list all available versions of an API without using the endpoint https://discovery.googleapis.com/discovery/v1/apis ?
Like a parameter for all individual APIs, would be cool to have a <api>.googleapis.com/$discovery/rest/versions
Thank you in advance.
I have been working with Google and Google Cloud APIs for more than a decade. There is no shortcut that I know of. Google does not publicize all API versions.
Knowing all available API versions will not do you any good in most cases. Some API versions require prior approval (whitelisting) to use them. Others might be in alpha status and should not be used except in certain situations. Some API versions require a relationship with the PM to obtain details. Some API versions require an NDA for either the API, the service, or both.
For the APIs that you require, subscribe to or follow the blogs and release notes.
Unless you have a specific requirement, only use the latest production (GA) version. GA versions have published documentation detailing the interface, methods, and parameters.
I recently started to work on a friend's project in Django and we want to provide a REST API so other projects can consume our data. I'm starting to learn django-rest-framework (and django-rest-swagger for documentation). Is it possible to create the API as a separate service? this way we dockerize it and serve the api in one container, and keep the application on its original container preventing that if many requests to the API were made, it will not interfere on the application (by bringing it down for example). If it is not possible what is the best way for implement the API on the project?
Yes, this is possible. See here. Structurally, you will probably want to write the project by keeping all presentation-related apps separate from the API-related apps.
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.
I know there are currently two methods that can be used to do this, documented (poorly) on Facebook's Developer site:
The old (depreciated) JavaScript SDK FB.Connect.createApplication
A new FBJS method Facebook.createApplication (only for use on Canvas pages)
The problem is that I not using a Canvas app that runs FBJS, and I am not using the OLD JS SKD. I am trying to do this on a regular old PHP website that uses the current JavaScript SDK and the PHP SDK.
I am doing the usual Open Graph API calls and such with the current SDK, so I understand the basics, I'm just not sure how to proceed to use the OLD SDK, or if (fingers crossed) I even really have to?
So, is there a way to make new Facebook Apps with the current JS SDK? Or with a server side PHP SDK call to the Graph?
And if not, how do I call the old SDK to do this?
Thanks
UPDATE: You still can't do this, but there is an official bug in the Facebook tracker about it: http://developers.facebook.com/bugs/295627350461318
There isn't outside of the OLD SDK as you indicated. It's been removed (what Facebook calls "deprecated"). I put in a feature request recently for them to add it back into the API:
Me:
The Facebook Developer tool is
considerably lacking in features. We'd
like to be able to create a third
party application that adds layers of
functionality to the developer
application, but we'd need to be able
to create and administer applications
via the Graph API.
The Graph API supports querying for
information on existing applications.
To create, administer or delete
applications developers must go to the
Developer Application.
Them:
------- Comment #1 From Jeff Bowen 2010-12-07 16:59:12 (-) [reply]
------- Thanks for the request. We’ll track this on our wishlist