I have a number of APIs both authenticated and not authenticated, created in earlier versions of import.io.
With the new Windows app I can't create an API, or at least pick one up. The tutorial shows a whole bunch of options, but I only get "CONFIGURE" and "EXPORT". "Configure" only gives me the option of single URL, bulk extract and URLs from another API. But there is no link to give me the API address.
Similarly, EXPORT only provides "USE IN DATA SET".
I asked their support but got this:
Hi Glenn,
Thank you for reaching out.
As you may noticed, we made some changes to our interface.
We moved the into the Export tab (next to configure) and named it
simple API integration.
Let me know if you have any questions.
Thank you,
But when I replied that I don't have that option, I got no reply.
What am I doing wrong?
Glenn.
Import.io support got back t me after I sent a screen video (http://www.evernote.com/l/AAhMJsy7INVHFauEOGFQBgEgJq2IPRSA6AU/). There's a bug in the new Windows desktop app that prevents authenticated APIs from showing.
Related
I know that Airbnb haven't opened their API to the public yet, but searching the internet I found some people are using it.
I tried to contact them, and also Airbnb, but without any answers.
Does anyone here knows any contact email, page, or phone number that I can refer to?
I have read here that you can find your API key by looking at the requests that AirBNB uses in their own website. So use the web-developer tools in chrome, or firefox, or firebug in firefox and search trough the requests in the network panel until you find the key being used in any JSON request. Some urls contain this key param, you copy that :) works for me!
Oh BTW, i'd like to remind you that the API is currently not officially released to fetch data in the background while you are logged in. When you use this key, they'll know your identity. You might get blocked or at least warned by AirBNB for using their API while you are maybe not allowed to. Read their terms & conditions to make sure. I am not taking any responsibility, of course ;)
You can now find your API key on the meta tags of the source code when logged in to your dashboard. Search for canonical_host and you will find:
{"canonical_host":"www.airbnb.com","api_config":{"key":"<your-api-key>"}
Just to update this set of answers, the api is on the following address but you need to request access first.
https://www.airbnb.com/partner
It offers an FAQ that informs you about the process and it will always be updated
As far as I can tell, they have shut down this service as of today.
"Unfortunately, this is no longer available" will be what the API returns.
EDIT:
It started working again after a few days. Very odd, maybe an internal problem, or we were rate limited or something.
Log into Airbnb.com, open up the web developer console, go to the network tab, filter by type json, and look at the url and find "client_id".
I found this answer here
I am thinking about app that will use google form and I need to create forms from that app. Is there a way how can I create form in google docs without using website but through some api or some other way?
I can offer an idea for a solution using Google App Script.
Since the beginning of 2013 you can create new forms using the App Script Forms Service API quite easily.
var form = FormApp.create(title)
.setDescription(description)
.setConfirmationMessage('Thanks for responding!')
;
The problem now is how to get that App Script running from your non App Script code.
You can use App Script to create a Web App that reacts to HTTP GET requests.
So putting it together, you may be able to create an App Script Web App that reacts to a GET request and when it gets the right URL parameters, it creates the form.
(Nov 2020) Yes, it is possible to programmatically create Google Forms. You can do it with Google Apps Script using its Forms service. You can also extend the code to read in the contents from Google Docs (with Apps Script's Document service) and use it for the creation of Google Forms.
I created a Google Workspace (formerly G Suite) Add-on, which you can think of as a Google Docs extension, called GFormIt. Its original purpose was intended for teachers to write exams/quizzes, possibly with answers, in Google Docs, then automatically convert them to Google Forms to distribute to students who submit their answers into Google Sheets (the destination for Google Forms submissions).
Furthermore, if you (the teacher) provided answers to your test questions, GFormIt would also auto-submit your answers to the Sheet as if you were a student. If you do that, and use a tool like Flubaroo to grade the exam, you could designate your row in the Sheet as “the answer key.” You can learn more about how it works, including viewing a short video, at the GFormIt page linked above.
This Google Docs add-on, along with others for Google Docs, Sheets, Slides, Forms, etc., are all certified/validated by Google and available for free to anyone from the Google Workspace Marketplace. (However, your admins may have to grant permissions for you to try to install them to your corporate Workspace account.) If interested in building your own add-on, please see the developer documentation and perhaps some of my introductory videos to get started, the most relevant being the one linked to at the top of this answer.
Apps Script is a serverless Google technology, meaning you write your code (using JavaScript) in the browser, and it is hosted by & executed on Google servers. If you wanted to create your own web app (and hosted anywhere), you would have to wait for a Google Forms REST API which does not exist at the time of this writing. (If we ever launch one, you'll find its documentation at https://developers.google.com/forms along with the others like Sheets https://developers.google.com/sheets, Gmail https://developers.google.com/gmail, Drive https://developers.google.com/drive, etc.)
Earlier this year (Mar 2022) the new Google Forms Api graduated from Beta. It is more powerful that the previous versions and caters for two main use cases:
Automated form creation and editing: Enables automated form creation
and editing. Enables rapid form generation from large volume question
banks or other data backends.
Reaction to Form responses: The API also enables developers to build
automations for acting on incoming responses. Examples include
developing real-time dashboards or visualizations and triggering
business workflows based on response data.
We have used it to build an integration that Creates documents and slides each time a form is completed: www.portant.co/google-forms-to-docs and it works really well.
I think the other key use case looks like it would be a good fit for you and others looking for a solution like this.
Cheers, James
Sorry, the API doesn't support programmatically creating forms.
Could someone please give me a single up to date tutorial for implementing OAuth with twitter. I have gone through so many tutorials I have lost count, and not a single one of them is up to date with the new xCode. I tried the MGTTwitter, but there is no tutorial for it. On his own website, where it gives link to tutorial, it just links you to this
http://ww35.2bros1blog.com/2010/07/switching-from-basic-to-xauth-with-mgtwitterengine-on-iphone/
So no idea that that is about
I tried
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
But I dont know how to add the static folders to xCode. I tried adding the targets, but nothing to add.
Tried following
http://mobile.tutsplus.com/tutorials/iphone/twitter-api-iphone/
However, it is out of date. When I run the app, using my consumer key and secret, when I click authorise, it just closes window, then brings up authorisation window again. I enter user and pass again, does the same thing over and over again.
I downloaded latest version of sharekit, didnt really want to go down this root as all I want is the twitter authorisation and I think adding over 50 files or so is a bit much for one feature, but thought I would give it a shot. But when I open it up, comes up with error around facebook
(null): error: /Users/adam/Downloads/ShareKit-ShareKit-7a05403/Classes/ShareKit/Sharers/Services/Facebook/../../../../../Submodules/facebook-ios-sdk/src/FBDialog.bundle: No such file or directory
All I want is a simple authentication so users can accept and then send tweets from the app. I dont want to use the twitter framework as then users have click send twice, i.e type message into textview, then then twitter viewcontroller appears, then they click send again. I want them to be able to tweet from within the app. Yet I just cannot seem to find any tutorial that explains how to do this in detail.
Could someone please point me in the direction of a tutorial that does this, I didnt think it would be this much hassle to implement a simple authorisation into iPhone, but this is driving me insane!!!
Edit:
I got
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
This one working, however when I sign in, app crashes and the log says
Authenticated with user (null)
Anyone have any idea about that one?
Found out why I was having a problem with these twitter tools. They were using http rather than https to authenticate with Twitter which is no longer allowed. Just changed it to https and works fine
The context is a desktop app using the client-side OAuth flow for authentication.
When I first built this app nearly a year ago, Facebook's documentation said to use the following URL to generate the login/authorization dialog:
https://graph.facebook.com/oauth/authorize?client_id=XXXXXXXX&redirect_uri=YYYYYYY
This is working right now. However, I've reviewed the newly updated Authentication Guide and now see that Facebook is saying to use:
https://www.facebook.com/dialog/oauth?client_id=XXXXXXXX&redirect_uri=YYYYYYY
Does anyone know what the difference is between them, and more importantly do I need to change it? Like I said, it is working now, but I'm a little concerned about something changing when the 10/01/2011 deadline comes around.
My second question is: Does anyone know what enabling the "OAuth Migration" setting in the Apps -> AppName -> Advanced page does?
The URLs redirect to each other. But still, please make the change to the new URL. Whenever the docs change urls and the semantics are the same, you should update so as to avoid unnecessary breaking changes. Even more so with desktop apps.
Second answer: That will issue you different access tokens for now.
how would I integrate Facebook into my Mac Application. I could give Objective-C a bit of a go, but it's going to be in an AppleScript-Objective-C project.
I could.. update the user's status a bit better instead of just opening their web browser and pointing them to "Facebook.com" , I could make my own interface that interacts with Facebook.
Any ideas?
You can interact with the Facebook API in many different ways, including submitting status updates as a POST request to the graph api. Their examples aren't at all language-specific. They demonstrate how to interact with it using curl on the command line, for instance.
Docs are here: http://developers.facebook.com/docs/
EDIT: Laziness IS one of the Three Virtues of the Programmer, but dude.... Clicking a link is too hard? Well, okay:
Here's how you authenticate your applications and get added as an application for a user:
http://developers.facebook.com/docs/authentication/desktop
Then here's how to work the Graph api. The section you want is "Publishing" most of the way down the page:
http://developers.facebook.com/docs/api/