Summary and recommendation
No public REST API, developer portal, or SCIM endpoint has been found in official TinyPulse or WebMD Health Services documentation as of the policy date.
The only documented programmatic identity integration path is SAML 2.0 SSO via Okta or OneLogin.
User lifecycle management - provisioning, updates, and deprovisioning - is performed through the admin UI or CSV import only.
Post-acquisition API capabilities may exist behind enterprise agreements, but none are publicly documented.
Any identity graph built on TinyPulse data would require manual export or vendor-negotiated access;
there is no confirmed API surface to query user state programmatically.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No publicly documented webhook system found in TinyPulse/WebMD Health Services official documentation.
Alternative event strategy: User management is performed via the admin UI or CSV bulk import. SSO via SAML 2.0 (Okta, OneLogin) is the documented integration path for identity management.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM endpoint found in official TinyPulse or WebMD Health Services documentation.
- The context reference indicates no native SCIM support; SSO prerequisite noted but SCIM provisioning is not confirmed as available.
- TinyPulse has been absorbed into WebMD Health Services (formerly Limeade); API capabilities may have changed post-acquisition and are not publicly documented.
Common scenarios
No API scenarios can be documented from available sources.
TinyPulse does not expose a confirmed public endpoint for user management, group sync, or lifecycle events.
Teams requiring programmatic integration should contact the vendor to determine whether private enterprise API access exists under their agreement.
For platforms that do support SCIM or REST user APIs, an MCP server with 60+ deep IT/identity integrations can automate provisioning and deprovisioning at scale
but TinyPulse cannot be included in that automation chain without a confirmed API surface.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core integration risk with TinyPulse is the gap between SSO coverage and full lifecycle automation. SAML 2.0 SSO handles authentication, but it does not provision or deprovision users - meaning joiners and leavers must still be managed manually in the admin UI or via CSV.
This creates a deprovisioning blind spot: a user can be disabled in your IdP but remain active in TinyPulse until an admin manually removes them.
Additionally, TinyPulse has undergone two ownership changes (Limeade, then WebMD Health Services), and API capabilities may have shifted significantly post-acquisition without public changelog or documentation. There are no confirmed rate limit headers, webhook events, or pagination contracts to build against, and the identity graph cannot be maintained programmatically without a stable API reference.
Any engineering investment in a TinyPulse integration carries high obsolescence risk until the vendor publishes confirmed endpoint documentation.
Automate TinyPulse workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
