I am getting protocol error on following url for quote query. What is wrong here in the url?
*/market/rest/quote/GOOG:2012:2:18:CALL:400?detailFlag=OPTIONS
Any help would be much appreciated.
Thx.
Issue Resolved. You have to sign "Real Time Quote Agreement on the website" otherwise eTrade wont allow you to pull the data.
Related
Due to recent changes on API Instagram, it is not possible to use the endpoint above:
https://www.instagram.com/{username}/?__a=1
I've tried with:
https://i.instagram.com/api/v1/users/web_profile_info/?username=username
However, it is not working correctly to fetch data. Please, could someone help to find a solution?
In advance, thank you very much.
The API endpoint https://i.instagram.com/api/v1/users/web_profile_info/?username=username does in fact work if the client has the X-IG-App-ID request header set. This header value can be obtained by inspecting the request sent via any web browser.
Try with this endpoint if your account is a business account.
https://graph.instagram.com/me/media?fields={id,caption,media_type,media_url,permalink,thumbnail_url,timestamp,username}&access_token=""
I am having a lot of troubles getting verification emails to work, when a user signs up with parse-server (using MailGun & Heroku).
The verification link sent to the user has this form:
https://myapp.herokuapp.com/apps/.............
but it does not work/
I get this, when clicking it:
Cannot GET /apps/.......
And even if I type only this in the web browser:
https://myapp.herokuapp.com/apps/
I still get this:
Cannot GET /apps/
At one point I was suspecting I could have made some confusion between parse-server-mailgun and parse-server-simple-mailgun-adapter (I am in fact not fully aware of the difference between the two), so I tried both but I still got the same kind of error.
Since, I can reach the point where a user account is actually created and a verification email is sent, I suppose I must have only made some detail mistake in my settings; but I can't see where. Any help or relevant hint from some experienced person would be highly apreciated.
In case someone think I should share some code because the explanation above is not enough, please tell me what you need to know to clarifly my point. And I will provide the necessary information.
You should see your publicServerURL to https://myapp.heroku.com/parse
I have a User event which calls a restlet using nlapiRequestURL() method. The URL, headers and authorization seems fine but it returns an error message saying - "Could not determine customer compid". Has anyone had the same issue earlier or know how to work around with this. Any help is appreciated.
We see this occassionally when a Suitelet or Restlet URL isn't specific enough for NetSuite to know which company is trying to call the URL. The script id by itself is not enough to know the company if the user is not currently logged in to NetSuite.
You can add &compid=<YOUR NETSUITE ACCOUNT NUMBER> to the the URL to let NetSuite know which company is trying to call the specific URL.
Just adding this on because I had the same issue, you'll get the same error if you're hitting a sandbox and not capitalizing the SB in nlauth_account.
Eg NLAuth nlauth_account=XXXXXXX_SB1 instead of NLAuth nlauth_account=XXXXXXX_sb1.
We did face this issue, clearing browser cookies solved in most cases.
Sometimes the problem was persistent for about few hours and got fixed on its own.
If you're using NLAuth, be sure you use commas (not spaces) to separate the account, email, and signature fields. Using spaces gave me this error.
I'm trying to follow the instructions at https://developer.paypal.com/docs/classic/mass-pay/integration-guide/MassPayUsingAPI/#id101DEJ0100A for paying a customer. https://www.paypal.com/us/cgi-bin/webscr?cmd=_profile-api-signature# tells me the API username, API password and and signature. I paste those values directly into my program, and POST those parameters (as well as other parameters) to https ://api-3t.paypal.com/nvp and I get this response back:
TIMESTAMP=2015%2d05%2d06T23%3a58%3a01Z&CORRELATIONID=6eef131f4a296&ACK=Failure&VERSION=2%2e3&BUILD=16566018&L_ERRORCODE0=10002&L_SHORTMESSAGE0=Security%20error&L_LONGMESSAGE0=Security%20header%20is%20not%20valid&L_SEVERITYCODE0=Error
Any tips for troubleshooting what might be going on here?
Thanks in advance!
Kevin
That error means the API credentials you're using are not accurate. Double the check the values themselves and make sure you didn't miss any characters or add any extra white space on the ends of the values. Also, make sure you're not sending sandbox credentials to the live PayPal server or vice-verse. That's usually what's happening when people run into this.
i have instagram follow/unfollow script, i wantto use that script to another domain, but when i take new client id the is not work, give me only basic permission.
https://api.instagram.com/oauth/authorize?client_id=new id&redirect_uri=new callback&scope=likes+comments+relationships&response_type=code
anyone can help me?
ps:sorry for my bad english.
Instagram changed the terms for using POST and DELETE requests last week. You'll have to request access for your application. You can read more at the links below.
http://developers.instagram.com/post/116410697261/publishing-guidelines-and-signed-requests
https://www.facebook.com/help/instagram/contact/185819881608116#=
UPDATE:
After Nov 2015 Documentation of instagram has been changed & now you can see Review article here :
https://www.instagram.com/developer/review/