Does google code provide an API for accessing information about a project like github does on http://developer.github.com/v3/? I haven't found any.
It provides API for its tracker, but other API features present in GitHub might not yet be present.
You can use Google API discovery service (based on its lib) to make sure of that, though.
Related
I am trying to use google drive and dropbox API's with Flutter and React. I came across googleapi libraries in pub.dev and npmjs for same. My question is why do we need another library when we can directly call the URL's mentioned in API documentation with suitable request body and access token with HTTP clients. I assume they might reduce the complexity than directly calling API endpoints themselves, but i want to know the full purpose of same.
Also if i don't want to use one of such libraries, what are the complexities i have to face?
Is there a way to integrate the api in c++?? I was looking for a way to read from an online google spreadsheet and I need it to be in C++, but the google available library seems to be outdated and is not recommended to use anymore, what can I do??
There is no official Google C++ API Client.
You have a couple of options:
Embedded another language, like Python, into C++ and use that for the API calls.
Call the API endpoints with your own HTTP methods.
Switch to a language with a supported API Client.
Hope this helps.
I'm new to this api documentation era.
Vising this api documentation, I get to post and query data. I understand that's a demo api documentation with swagger.
But what happens with real world API documentation? do I have a documentation in demo.api.myawesome.com and actual api on api.myawesome. com using different data stores?
But again digging deeper, I got to find out that an api can be self documenting using swagger libraries. This seems like both api and documentation are using the same data store which can't be the case.
What am I missing here?
From the Swagger website:
Swagger is a set of rules (in other words, a specification) for a format describing REST APIs. The format is both machine-readable and human-readable. As a result, it can be used to share documentation among product managers, testers and developers, but can also be used by various tools to automate API-related processes.
So yes, it uses the same "back end" as the actual API. It's just visualizing it, allowing you to interact with it via the Swagger UI.
If you mean Swagger UI - the "try it out" button sends requests to the server specified by the host property in your spec. If host specifies your production server, requests will be sent to production; if it points to a sandbox, "try it out" will use the sandbox. You may have a version of the spec for internal use that points to production, and a public version that points to sandbox.
Note that Swagger supports authentication as a way to ensure that only authorized users (e.g. your actual customers with valid credentials or API keys) can make API calls.
You can omit host from the spec to disable the "try it out" functionality - this way you can still have the API docs, just without the interactive part.
I am working with google cloud platform. Learning and trying out a few things like Bigquery and Google Cloud Storage.
I find it confusing that there are two official APIs for all those things: gcloud API and Google API Python Client. In google cloud's "getting started" tutorial, the recommended API is Google API (Python) Client and it seems that the documentation for gcloud api is not very detailed.
In short, to access Google Cloud Platform programmatically,
which api library is better?
Where can I find nice documentation for that?
My answer
I would recommend gcloud API, this choice also applies to other languages: nodejs, ruby.... And then
Explanations
It is confusing, that Google have these two APIs have overlapping functionalities. And it is more confusing that they use Google API Client in their tutorial, while gcloud seems to be a more Google Cloud SDK specific package.
Here is what I found out: on the page of the gcloud API page, there is this FAQ section saying:
The Google APIs Python Client is a client library for using the broad set of Google APIs. gcloud-python is built specifically for the Google Cloud Platform and is the recommended way to integrate Google Cloud APIs into your Python applications. If your application requires both Google Cloud Platform and other Google APIs, the 2 libraries may be used by your application.
Addtionally, the gcloud api is part of the Google Cloud SDK. So it is standard.
Both the gcloud command-line tool and gcloud-python package are a part of the Google Cloud SDK: a collection of tools and libraries that enable you to easily create and manage resources on the Google Cloud Platform. The gcloud command-line tool can be used to manage both your development workflow and your Google Cloud Platform resources while the gcloud-python package is the Google Cloud Client Library for Python.
Based on my experience of using the python and nodejs api, the gcloud api is much more easier to use than the google api client. Here is another question for your reference:
When accessing Bigquery using Python API, what is the difference of using google client API and gcloud
So obviously, for a project working around Google Cloud Platform, using the gcloud API is an better choice.
Documentation
What about the documentation?
The documentation seems not very helpful(especially for rookie programmer like me) if you look at a page like this:
https://googlecloudplatform.github.io/gcloud-python/#/docs/master/gcloud/storage/blob/blob
I found two ways to get more detailed instructions: look for the doc for stable version or go to the github page. For instance:
https://googlecloudplatform.github.io/gcloud-python/stable/storage-blobs.html
https://github.com/GoogleCloudPlatform/gcloud-python
This is the result of the little research I did on it. I am still curious why Google mention gcloud library so little in its tutorials. Anyway, I hope this will help people to get an idea of which library to use, and save some time researching on it.
Assume I have a server example.com. And it is a service with exposed api. But I do not have a documentation, is there way to see the api paths?
Paths like example.com/users,
example.com/events,
etc
There is supposed to be documentation, since the api is the work of someone, and it will be difficult to know what that person is thinking, or how he has structured his api. You should request the documentation if you can or get an alternative api that can do the same thing but is well documented