Introducing the New api.embed.ly
'oooooooo pretty' - Your reaction to the new http://api.embed.ly.
Today marks the first major release to api.embed.ly. We have completely overhauled the site from top to bottom and we have added 35 new providers in the process. So what changed and why?
When we started 9 months ago, we tried to move as fast as we could. This means doing whatever it took to ship code and add new features. As we went we learned how to do things and how not to. This learning lead us to scrap 80% of our old code base and start all over again. This is what we are launching today. So what’s new and what can you expect going forward?
Our process for building oEmbed responses has changed. We now use meta tags, Open Graph and microformats to fill in the blanks left by oEmbed responses. We also verify that the image we are sending back exists and is of the right dimensions. Everything is also done in parallel, so you will see faster response times with better information.
Request a Service
We want to make api.embed.ly a community-driven resource. Tell us what providers you want to add and we will. With the re-arch we can now add, verify, test and deploy new providers in under a couple hours. Any service with an oEmbed API, meta attributes like video_src or open graph take even less time. We added a Request a Service page to make this process even easier.
We added 35 new providers. Here are a few samples:
Terms of Service
We now have one! It pretty much just states everything we have always said in lawyer speak. You can find the full version at http://api.embed.ly/terms, but here is a run down.
api.embed.ly is a community resource offered by Embedly. We do not offer guaranteed up times or unlimited access. If someone is abusing the service we will rate limit or block access in order to better serve the community as a whole.
To be clear we have not had to rate limit anyone and we have only blocked 2 people for being malicious. We have had a great community of developers thus far and we hope that continues, but in case it doesn’t we will take actions to better serve the community as a whole.
api.embed.ly is only a pass through, the end developer is responsible for adhering to the terms of service for each provider.
As an intermediary we cannot control how you, the end developer, display content. We ask that you do the following:
- Give credit where credit is due. Link back to the original piece of content.
- Don’t be evil. Use the content in the manner in which it was intended.
Lastly we have added some language to protect Embedly as a service.
- Developers cannot use api.embed.ly to compete with any tools that we offer with pro.embed.ly or as a replacement for api.embed.ly. We don’t want people creating services that just bundle up our service.
- We are not responsible if api.embed.ly is not reachable for a period of time. We have had great uptime thus far, but If you need an SLA you should use pro.embed.ly.
- We are not responsible if one of the providers goes down or disappears entirely. A few sites have gone out of service or disabled their oEmbed endpoints and there isn’t anything we can do about it.
- We will fix bugs and respond to support tickets as best we can, but there is no guarantee that they will be solved in a set amount of time. We try our hardest to respond and fix issues within a few hours or days, but sometime it’s just not possible.
If you have any questions about the Terms of Service please do not hesitate to contact us at firstname.lastname@example.org
We are launching a new service in the next couple of months called pro.embed.ly. This will be a productized version of api.embed.ly with a bunch of added features that a number of people have requested. They include the ability to get meta data about any url, analytics and lots of additional information. These features are already in production in sites like http://yammer.com and http://storify.com. If you are interested in participating in a beta program drop your email address at http://pro.embed.ly. We will send out invites in the coming weeks.
We are changing the default api endpoints from /v1/api/oembed to just /1/oembed. The old one will still work and we have no plans for deprecating it, but going forward this seems like a much more sane and simple way to do the endpoints.
We are excited about where we are heading in the traction we are seeing. api.embed.ly now serves over 800k urls a day. Keep up the embedding and let us know what you think about the new api.embed.ly!