API

• Real-time updates
• oEmbed
• Widgets

Real-time updates and Firehose

We provide Atom feeds that include entries for every dailymile user marked up with Activity Streams. Updates are provided in real-time using PubSubHubbub. Learn more »

oEmbed

oEmbed is an open standard that's used to embed dailymile entries on to your site. You do not need to register your application to use oEmbed. Learn more »

Widgets

Looking for widgets or badges for your blog or site? Get them here »

Please let us know if you have any questions or suggestions or if you'd like to do something that isn't supported. We're just getting started and we'd love your feedback to improve it.

Having trouble coming up with an idea for an app? Here are some things the community would love to see built:

• Mobile clients: develop mobile apps for iPhone, Android, Blackberry and other devices
• Libraries: develop clients for different platforms and languages then let us know and we'll link to them (here)
• Blog Integration: allow users to have their dailymile entries posted to their blog automatically (Wordpress, Blogger, Tumblr, etc.)
• Google Health: push dailymile workout data into Google Health
• Nutrition: integrate calories burned from dailymile with intake from a nutrition site
• Twilio app: allowing people log workouts via SMS
• Bulk import: import your history from other services (Nike+, Garmin, other online logs)

dailymile is a social experience for active people and a community and it's important to keep that in mind when you're building your app. Before you start using our API, we have a few guidelines that we'd like you to follow. You can check out our Showcase to find some great apps built using our API.

You may use the dailymile brand and logo, but not in ways that make users think that we built or endorse your app. Please read our Branding Guidelines if you'd like to use our brand and download our assets.

Commercial apps: If you're building an application that derives revenue from its use of the dailymile API, please contact us. We reserve the right to ensure it doesn't harm our business interests.

Do:

• Use the API responsibly. Please cache data when possible and handle errors appropriately.
• Make it easy to include the message field with workouts shared to dailymile. Encourage social interaction over bot-like behavior.
• Validate workout data on the client before posting. A mis-typed 1,000 mile workout can ruin a challenge and disrupt leaderboards.
• Make a great user experience that integrates dailymile in a valuable and expected way. Delight people.

Don't:

• Don't use dailymile anywhere in the name of your application, URL or branding except as allowed by our Branding Guidelines.
• Don't replicate the core user experience of dailymile.com.
• Don't replicate premium features of dailymile.com available only to PRO members.
• Don't store users username and password or any other user data without their express consent (using the API or crawling).
• Don't abuse the API with too many requests. If you're unsure, ask us.

Applications that don't follow the guidelines above may be in violation of our Terms of Service and may have their API access revoked. We reserve the right to modify these terms and guidelines from time to time without notice.

You may use the dailymile brand and logo, but not in ways that make users think that we built or endorse your app. You shouldn't use the word dailymile anywhere in the name of your application, the URL, or in any trademark. Users should never be confused as to whether they're using your product or ours. You can of course use language to indicate that the app is build using the dailymile API.

Assets

Coming soon...