Let me be clear. There is one thing I know fairly well, it is copyright law. I am not a lawyer, however, knowledge of copyright was a constant requirement of my consultancy for 30 years. As an added bonus, I consulted primarily to telecos and often worked with subscriber data and data analysis and presentation of said data for sale and re-use. I am at least, ...
The first and main difference between them is that with most APIs there’s a request followed by a response. No request is required for a webhook, it just sends the data when it’s available.
The API is an interface to your data on example.com. The API is used
from your server to the example.com platform and can be used to List,
API is doing stuff when you ask it to, while Webhook does stuff on it's own when certain criteria match.
So, in a nutshell: The API is where you tell us things and Webhooks is where we tell you things.
Whenever there’s something new, the webhook will send it ...
There doesn't seem to be a standard.
The StackOverflow answer leans towards 410 GONE, but I think 301 MOVED PERMANENTLY is more appropriate.
To make the correct choice, we have to look at your specific case. If your goal is to have all calls being made to API v1 fail without taking any further action, 410 GONE works for that. If you want some continuity, ...
I'm not sure what you mean by "update/modify the data", but there are probably few free file hosting services that allow hotlinking. It's just not a sustainable business model, especially if you have an exposed API wherein not even the uploader will have to come to your site. There are also a lot of copyright infringement liabilities regarding public file ...
IFrame's are by nature slower due to the overhead they add while rendering a new page within the browser window. And some browsers are slower at rendering iFrame's than others (i.e., IE).
As the chart here demonstrates, iFrames can cost up to 100x more time to create elements than scripts and styles.
IFrame's will also block a window's onload event until ...
One thing that doesn't seem very clear in the other answers here...
Whether it's "legal" or not, first and foremost, depends on the country. If we're talking about the United States, for example, then using the data itself is not illegal. However, I'd advise you to use the real data from the US Census. They offer tons of data through what they call TIGER ...
While closetnoc has discussed the issue of the data itself, there's a larger legal concern: you are not authorized to access the API offering the data.
The baseline for most computer crime laws involves the notion of "unauthorized access to a computer system". You should not confuse this reference to authorization in the legal sense with the concept of ...
I'll illustrate this with a concrete example: Credit card payments.
When your site wants to charge a credit card, you call an API at your credit card processor. The credit card processor then charges the credit card returns a success or failure status to that API call.
The credit card processor may need some way of updating your site about this ...
What you're looking for is called the Product Advertising API, specifically the ItemSearch - http://docs.aws.amazon.com/AWSECommerceService/2011-08-01/DG/ItemSearch.html
This should help you get a set of product given the title of movie, the category [DVD], etc.
I work in the address verification field for SmartyStreets. Actually we added geocoding and residential/business indication (RDI) features to our address API not too long ago and so I think I can point you in the right direction as you do your own research to find what fits your needs the best.
You'd be interested to know that Google and Bing may know more ...
From this similar question on StackOverflow:
National Climatic Data Center (NCDC) (web services)
World Weather Online (paid)
More from this question:
National Digital Forecast Database (NDFD) SOAP Web Service
Wolfram Alpha for developers
And even more:
Infochimps Geo API
We looked at this for an implementation earlier this year. We considered 2:
European Central Bank
refer : ECB
lists exchange rates against the Euro
Limited number of currencies
refer : XE
USD540 a year for daily lookups
available for a variety of base currencies
very wide currency support
In the end, we went with XE, as we needed to support ...
It will depend on your DNS hosting is done.
I personally use Zonomi. They have a DNS API. I can issue a request like https://zonomi.com/app/dns/dyndns.jsp?action=SET&name=mynewsubdomain.example.com&value=10.0.0.1&type=A&api_key=apikeyvaluehere to set the IP address for a new subdomain.
Another solution would be use use Route53 from ...
It probably depends on the nature of the data. Pure data (think telephone directory) cannot be copyrighted. So a list of cities from an API should be fair game to copy and show to users. However, if that API has descriptions of the city those descriptions would fall under copyright law and you wouldn't be able to use them without violating copyright.
It seems that I'm able to answer my own question while using the new Custom Search API.
Creating a Custom Search Engine will initially ask you to provide sites or pages that you want your CSE to search in. By filling in a sample website and creating the CSE you are then able to manage and adjust it after the creation process. Here you can tell the CSE that ...
According to the official Flickr api documentation it is 3600 API calls per hour
Limits: Since the Flickr API is quite easy to use, it's also quite easy to abuse, which threatens all services relying on the Flickr API. To help prevent this, we limit the access to the API per key. If your application stays under 3600 queries per hour across the whole key (...
This artictle has good instructions for getting Google Alerts RSS feeds:
To use the feature, log in to your Google Alerts account and make sure you have at least one entry. If you don’t, create one by picking a search query for Google to track for you.
Next, click on Manage Alerts and hit the Edit button on an alert you want to get an RSS feed for. ...
(IANAL, and laws and norms vary widely throughout the world, but certain things tend to remain consistent due to IP treaties. If you have a professional issue outside of your specialty, consult with a profesional.)
Generally, legally, an API is not considered to be "intended for public consumption" unless it's actively documented as a public API, with ...
I entered my email address in on the site, and requested to reset my password. Then after receiving the email and resetting my password I noticed that I was able to use the email address on the account to login instead of Twitter. When I used my email address and what the password was reset to, I was able to obtain an access token.
I've never pulled activity data out of Github, so the below only applies directly to Twitter. I would imagine a lot of it is more or less the same for Github, though.
I wouldn't rely on RSS for anything from Twitter. They've been killing it off ever since they started previewing NewTwitter. I actually think it's entirely gone now except for a few places ...
You can become a enom reseller and use their API: http://www.enom.com/resellers/api-reseller.aspx
Domai.nr has an interesting API and concept: http://domai.nr/api
iwantmyname.com will have an API soon: http://iwantmyname.com/developer/domain-dns-api
name.com has a reseller api: http://www.name.com/reseller/
I would start with an existing platform like OpenCart or any other open source framework and THEN customize it to meet your needs. Definitely no reason to do all of the hardwork that's already been done, but definitely worth customizing the remaining items on your to-do list.
I don't think W3C had your use case in mind when they made the validator. Why not run your own? The script you made is going to be very slow because it is relaying all requests. Also, your script won't run cleanly on E_STRICT. Also, your script doesn't encode URI parameters. Also, you are unnecessarily using regexes. Also, you are not HTML encoding your URI.
Regarding the server to server communication, it's not really necessary to run SSL on example.com, since the communication it makes with api.example.com will be encrypted and the identity of api.example.com will be trusted (using its certificate). If the main site must authenticate itself with the API subdomain, however, it's a good idea to use SSL there too ...
As an advice, if you're current skills are limited, and the project is a little too much, don't take it, there will be tons of other oportunities when you're skills have increased.
Having said so, i recommend that you invest time into any one of available php frameworks, some are incredibly easy to work with, and will make your tasks super easy.