Overview

WhatPulse is a free public API that exposes keyboard, mouse, and network usage statistics collected by the WhatPulse desktop application. You can retrieve team and user pulse data without any authentication, making it a great first API to practice with. It returns simple JSON objects that are easy to parse and display.

Beginner Tip

Use your own WhatPulse username to fetch real data and confirm the response format before building anything more complex. The API has no authentication, so you can call it directly from a browser URL bar.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

WhatPulse data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "status": "success",
  "data": {
    "result": "Data from WhatPulse",
    "description": "Small application that measures your keyboard/mouse usage",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

AccountName The WhatPulse account username.
Keystrokes Total number of keystrokes recorded by the user.
Clicks Total mouse click count recorded.
DownloadedBytes Total bytes downloaded as tracked by WhatPulse.
UptimeSeconds Total computer uptime in seconds captured by the app.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://developer.whatpulse.org/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

Empty or null response The username or team name provided does not exist in WhatPulse.
Double-check the username spelling as it is case-sensitive. Visit whatpulse.org to confirm the account exists.
XML returned instead of JSON The format parameter was omitted or misspelled.
Append &format=json to your request URL to receive a JSON response.
Connection timeout The WhatPulse API servers may be temporarily unavailable.
Wait a few minutes and retry; the service occasionally has short outages.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Tracking
Difficulty Beginner
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →