WhatPulse

About WhatPulse

WhatPulse provides a set of APIs for developers to interact with WhatPulse user data and the WhatPulse client application. The Web API offers programmatic access to user data, applications, statistics, and insights, allowing retrieval of information about users, teams, and pulses for building personal dashboards, integrations, or third-party applications. Applications built to work on behalf of other users can register as an OAuth application, letting WhatPulse users authorize the app to call the API using a scoped access token.

The Client API is a local API for interacting with the WhatPulse client running on a user's machine, providing access to real-time statistics, application usage, and other client-specific data. It is intended for developers building applications that need to communicate directly with the locally running WhatPulse client rather than with WhatPulse's remote data.

This is suited to developers building dashboards, integrations, or third-party tools on top of WhatPulse's usage-tracking data, whether working with aggregated user/team statistics via the Web API or real-time local client data via the Client API.

Key features

• Web API for programmatic access to user data, applications, statistics, and insights
• Retrieve information about users, teams, and pulses
• OAuth application registration for third-party apps acting on behalf of users
• Client API for real-time local access to the WhatPulse client's statistics and application usage

Frequently asked questions