Hi Michael - did you get the API to work in the Twitter console first?
I did this for the trends closest API - once I got the OK response - I copied the appropriate parameters in the REST Connector:
This worked for me -- however:
this API https://api.twitter.com/1.1/trends/place.json does not work in the console - I get a 404 page not found:
So I think the problem might be with the twitter REST API itself.
Let me know what you find.
Please mark the appropriate replies as CORRECT / HELPFUL so our team and other members know that your question(s) has been answered to your satisfaction.
Hi Mike, I'm pretty sure I did get this to work through the Twitter API console, but I'll test again later to be sure.
The actual error message I recieved was when went to the next screen and tried to choose "JSON" as the response type. Did you try that too?
Also, what type of details did you put behind the blanked out boxes, as the PDF guide only has the ones you haven't blanked out.
Easiest way to troubleshoot this would be to install Fiddler or any other web proxy to check the request/response to/from Twitter. It would then be easy to spot if Content-Type is set to application/json;charset=utf-8 in the response as it looks like you're not getting JSON back
There's nothing wrong with the URL https://api.twitter.com/1.1/trends/place.json?id=1 I tried it myself and works fine so that's not the issue here (you need to add an id or you will get 404 page not found back).
If authentication would be wrong, you would get an authentication error (401) so that doesn't seem to be the issue either:
REST Connector should pick up the response type automatically if "Auto detect response type" is set. If you uncheck "Auto detect response type" you have the option on the next screen to select response type, but there shouldn't be any need for this in general.
See if you can download and run Fiddler. You should find the request in the left pane and in the bottom right pane you will see the response (select Raw to see the pure response being sent back). Check header content-type in the response:
I have a similar issue when I try to connect to Google Analytics. I’m not able to find the correct Token. I can find one that I can use in the playground but it expires.
I have to make a dashboard for a customer where there shall be a few KPI’s from google analytics that updates every 2-3 minutes.
I have used my own credentials (Client ID and Client Secret) in the playground. Where should I look for the Oauth_consumer_key?
I can connect when I configure the query headers with
Value: Bearer ya29.ZwLGNIry0jEsjdNIAuMfpgVVfruff-ITbY_b5-q1IElw25FPCCc6TWDxrrJfcSAMQ6ho
The value is the access token I found in the OAuth playground. The problem is that the token expires and then I cannot connect any more.
I ran into another issue. I need variables in the URL. I created vURL and added it in “WITH CONNECTION”. This is not working.
LET vURL = 'https://www.googleapis.com/analytics/v3/data/ga?ids%2ga%%3A98567028&metrics%2ga%%3Atransactions%%2Cga%%3AtransactionRevenue&start-date%2'& date(now(),'YYYY-MM-DD') & '&end-date%2' & date(now(),'YYYY-MM-DD');
CUSTOM CONNECT TO "Provider=QvRestConnector.exe;
FROM "columnHeaders" FK "__FK_columnHeaders"),
FROM "totalsForAllResults" FK "__FK_totalsForAllResults")
FROM JSON (wrap on) "root" PK "__KEY_root"
WITH CONNECTION (
HTTPHEADER "Authorization" "Bearer $(vAccessToken)"