Updating a row in a Google Fusion Table - sql

I am trying to update a row in a Google Fusion table as per the instructions on this page with a URL of the following form:
https://www.google.com/fusiontables/api/query/?sql=UPDATE<TABLEID>SET<COLUMN NAME>=<NEW VALUE>WHERE ROWID=<ROWIDVALUE>
When I enter this into a browser I get a 'File Not Found' message. Any suggestions as to what I might be doing wrong would be appreciated.

Need oauth2 to create token. See details here and here
Then simply add that token to URL
https://www.google.com/fusiontables/api/query/?sql=UPDATE<TABLEID>SET<COLUMN NAME>=<NEW VALUE>WHERE ROWID=<ROWIDVALUE>&access_token=<ACCESS TOKEN>

In order to update a table, either using the old or the new API, you need to send an authorization header along with the request. More information about authorization can be found here:
https://developers.google.com/fusiontables/docs/developers_guide#Authentication

Related

Social tables authentication with code returns 'Code has expired' message

Am request social table token endpoint from angular application with the code (authorization_code as grant type). It returns 'code has expired' exception. Can someone help me on this
It sounds like you are using an expired code.
You'll need to get a new code when the old one expires.
Have you taken a look at the tutorial?
https://developer.socialtables.com/docs/apps/tutorial.html

I am requesting access token from gfycat api. What am I doing wrong in the below screenshot?

I am requesting access token from Gfycat API.
I have entered the details in Postman as mentioned below, i.e. Client secret, still getting BAD Request error.
Please help me identifying what I am doing wrong.
For details, please see the below screenshot.
enter image description here
I can see two issues in the screenshot:
There's client_id twice, instead of one client_id and one client_secret
You put the key/values in Postman's Header tab instead of the Params tab.
It's a straightforward request, you can even get an auth token from your browser with a simple URL (no header or body)
https://api.gfycat.com/v1/oauth/token?client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&grant_type=client_credentials

Update issue fields in JIRA

Hi I am using postman client for Chrome to run my rest api calls. I am trying to update issue in JIRA via rest API. I have referred to JIRA API also for updating an issue.
I am using PUT method to update an issue fields. Here is the syntax.
PUT /rest/api/2/issue/{issueIdOrKey}
I am trying to update summary field like this.
{"update":{"summary":[{"set":"Bug in business logic"}]}}
But it is giving me the 400 bad request error.
and in the body its showing message "No content to map to Object due to end of input".
Please find the attached screenshot for more reference. Thanks in Advance.Jira Update issue
In postman rest API client, add the json object to Body as in the below picture.
I added authorization as Basic Authorization and provided JIRA credentials.
Note that the body should be raw and type should be JSON(application/json) instead of Text(default).
Response for this PUT request is 204 when update is successful.
Here is REST API Documentation for additional options.

How can I get a list of followers of a twitter account

I'm trying to get a list of the accounts being followed by https://twitter.com/verified
how can I do this?
when I try to use the api I get this
{"errors":[{"message":"Bad Authentication data","code":215}]}
I have a developer key but I dont know if I had to paste it in the URL?
please help.
thanks!
You need to obtain a access token before requesting followers.
As specified by the REST API you are required to be authenticated before making the request.
https://dev.twitter.com/docs/api/1.1/get/followers/ids
The options of getting authentication here listed here:
https://dev.twitter.com/docs/auth/obtaining-access-tokens

Flickr API: API key keeps getting invalid?

I’ve a Flickr which I’m using to upload pictures from my phone and all images are public. On my blog I want to retrieve all the images to show and for that I’ve first tried to create an application to get my API key. I’m using the Flickr API flickr.people.getPublicPhotos. This API service is said to not require authentication and putting it all together I end up with this call:
http://api.flickr.com/services/rest/?method=flickr.people.getPublicPhotos&api_key=fc94274cd0335f3c171fe22c8490b7d9&user_id=5545356%40N04&extras=description%2Cdate_upload%2Cdate_taken%2Cowner_name%2Coriginal_format%2Ctags%2C+o_dims%2C+views%2C+media%2C+path_alias%2C+url_sq%2C+url_t%2C+url_s%2C+url_q%2C+url_m%2C+url_n%2C+url_z%2C+url_c%2C+url_l%2C+url_o&per_page=40&format=php_serial&api_sig=0c48e2b6b6d9a03521e5ca86a15cf471
The problem is that every around 10 hours I fails and returns the error message a:3:{s:4:"stat";s:4:"fail";s:4:"code";i:100;s:7:"message";s:31:"Invalid API Key (Key not found)";}
I tried to create the API call when logged in to Flickr and also with not logging in and in both cases I get the error message. It’s like the API key expires or stops working. Have a missed something on Flickr about the API key or what could cause this? It is really frustrating to renew the URL twice at day.
Thank you
Sincere
- Mestika
If I read the docs correctly, the &api_sig query string parameter is constructed using an authentication token, one that eventually expires. Remove that parameter (= do not sign your API request) and I think you'll be OK.
Mestika's comment seems correct. I was getting the same problem when using the API explorer. If you use your accounts API, or go in and create a new app, then use the API given for that, then the key doesn't change every few hours.
The url to request a key is:
http://www.flickr.com/services/apps/create/apply
I got the same problem.
This is how i solved it:
removed the auth_token and the api_sig parameters
replaced the api_key value with an app key
Hope this helps.
i met this issue before. with new api key, only accept https request.
Let's change your url to: https://api.flickr.com/services/rest/?method=flickr.people.getPublicPhotos&api_key.....
I am sure it will be work right know.
thanks