Pulse
Ivanti's secure-access product family, formerly Pulse Secure, acquired by Ivanti in 2020. Three administrator-facing REST APIs configure and observe it: Ivanti Connect Secure for SSL VPN remote access, Ivanti Policy Secure for 802.1X and RADIUS/TACACS+ network access control, and Ivanti Neurons for Zero Trust Access for per-application ZTNA. Connect Secure and Policy Secure are customer-run appliances whose management API is reached at the customer's own host; nZTA is a hosted tenant. All three are configuration and management interfaces rather than data-plane APIs — they change who can reach what on a corporate network. Ivanti publishes no OpenAPI and no SDK for any of them; the published contract is prose documentation with worked curl examples plus a customer-portal Postman collection.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Pulse the way a machine reads it — 20 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pulse scores 37.3/100 (thin), with a separate agent-readiness read of 8/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Pulse's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pulse/"
title="Pulse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pulse.svg"
alt="Pulse Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/pulse/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pulse/"
title="Pulse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pulse/card.svg"
alt="Pulse Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Pulse
Each block below is one kind of artifact we hold for Pulse. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Ivanti Connect Secure REST API
REST API for managing Ivanti Connect Secure (formerly Pulse Connect Secure) VPN appliances. Provides endpoints for system configuration, user and role management, authentication...
Ivanti Policy Secure REST API
REST API for managing Ivanti Policy Secure (formerly Pulse Policy Secure) network access control appliances.
Ivanti Neurons for Zero Trust Access REST API
REST API for managing Ivanti Neurons for Zero Trust Access (nZTA), providing endpoints for managing zero trust access policies, gateways, and user access.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Pulse Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Pulse Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Pulse Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
SSL VPN Remote Access
Secure remote access to corporate resources through SSL VPN tunnels with granular access policies.
Zero Trust Network Access
Identity-aware, application-level access control without exposing network resources.
Network Access Control
Enforce security policies on endpoints before granting network access with 802.1X and agent-based checks.
Multi-Factor Authentication
Integrate with MFA providers for strong authentication on VPN and network access.
Host Checker
Validate endpoint compliance with security policies before granting access.
Role-Based Access Control
Define granular access policies based on user roles, device type, and compliance status.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Pulse Trust Center
SOC 2 Type 2, ISO/IEC 27001, FedRAMP, U.S. Federal Government Authorization to Operate (ATO), Common Criteria, IRAP, Cyber Essentials, SIG Lite, VPAT 2.4 / Section 508
SECURITYUse Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Remote Workforce Access
Provide secure remote access to corporate applications and resources for distributed teams.
Zero Trust Architecture
Implement zero trust security with per-application access controls and continuous verification.
BYOD Management
Securely enable bring-your-own-device access with endpoint compliance checking.
Partner and Contractor Access
Grant controlled, time-limited access to third-party partners and contractors.
Resources
Every other property we hold for Pulse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 6
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/pulse · machine-readable index on apis.io
This is an independent, third-party profile of Pulse, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.