Crowdsignal
Create surveys for the web and mobile.
Profile Requests
Base Request
Users may optionally enter a variety of profile information to associate with their Gravatar account. This information is openly-accessible using a similar process to requesting images.
A simple profile link looks like this:
https://www.gravatar.com/HASH
where HASH is the email hash of a user. This request will automatically redirect to their username-based URL, so for example, you might get this:
https://www.gravatar.com/205e460b479e2e5b48aec07710c08d50 --> https://en.gravatar.com/beau
An important point to note is that profile requests will only resolve for the hash of the primary address on an account. Users may have multiple addresses on a single account, so while a Gravatar image request may return a result, a profile request for the same hash may not.
hCard
Profile pages are fully marked up using hCard, a microformat for programmatically embedding information about people, companies, organizations, and places in HTML and other markup languages. The screenshot below describes some of the main markup involved on a profile page
- Email address marked up with
class=email(only available via JS/client-side parsing due to spam-protection measures) - IM accounts marked up using
class=url(some values only available via JS/client-side parsing due to spam-protection measures) - Phone numbers marked up with
class=tel(using type/value subproperties) - Verified accounts marked up with
class=urlandrel=me - Name marked up with
class=fn - Personal Links are marked up with
class=url - Image (main Gravatar) is marked up using
class=photo
Data Formats
Profile data may be requested in different data formats for simpler programmatic access. The following formats are supported: