Pulse website screenshot

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.

Pulse publishes 1 API on the APIs.io network: Ivanti Connect Secure REST API. Tagged areas include Ivanti, Network Security, Secure Access, SSL VPN, and VPN.

Pulse’s developer surface includes authentication, changelog, API reference, getting-started guide, support, documentation, engineering blog, and 24 more developer resources.

37.3/100 thin ▬ flat Agent 8/100 agent aware saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
AccessPaidApproval
3 APIs 6 Features 4 Use Cases
IvantiNetwork SecuritySecure AccessSSL VPNVPNZero TrustZTNANetwork Access ControlRemote AccessIdentity and Access ManagementSecurityPulse Secure

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/pulse: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

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

Published pricing tiers and plan structures.

Pulse Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Pulse Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Pulse Finops

FINOPS

Features 6

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.

Pulse Authentication

0 schemes

SECURITY

Pulse Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Pulse Vulnerability Disclosure

security.txt · contact published

SECURITY

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

SECURITY

Use Cases 4

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

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 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

Source (apis.yml)

apis.yml Raw ↑
aid: pulse
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Paid · Requires approval
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/pulse.png
name: Pulse
description: '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.'
type: Index
url: https://raw.githubusercontent.com/api-evangelist/pulse/refs/heads/main/apis.yml
tags:
- Ivanti
- Network Security
- Secure Access
- SSL VPN
- VPN
- Zero Trust
- ZTNA
- Network Access Control
- Remote Access
- Identity and Access Management
- Security
- Pulse Secure
created: '2024-01-15'
modified: '2026-08-29'
specificationVersion: '0.23'
apis:
- aid: pulse:ivanti-connect-secure-rest-api
  name: Ivanti Connect Secure REST API
  description: REST API for managing Ivanti Connect Secure (formerly Pulse Connect Secure) VPN appliances. Provides endpoints
    for system configuration, user and role management, authentication server configuration, license management, network settings,
    resource policies, and system maintenance operations.
  humanURL: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/landingpage.htm
  baseURL: https://{ics-appliance-host}/api/v1
  baseURLNote: Templated on purpose. Ivanti Connect Secure is an appliance (hardware, virtual or Azure) the customer operates,
    so the API host is the customer's own appliance address. Ivanti's own examples use https://<ICS-ip>/api/v1 and https://<hostname>/api/v1.
    There is no vendor-hosted endpoint for this API.
  tags:
  - Authentication
  - Configuration
  - Network Security
  - Secure Access
  - SSL VPN
  - VPN
  properties:
  - type: Documentation
    url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/landingpage.htm
  - type: APIReference
    url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ics_spec_configs__using_restapis.htm
  - type: GettingStarted
    url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ovw.htm
  - type: Postman
    url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ics_postman_apis.htm
  - type: Authentication
    url: authentication/pulse-authentication.yml
  - type: ErrorCatalog
    url: errors/pulse-problem-types.yml
  - type: Conventions
    url: conventions/pulse-conventions.yml
  - type: ChangeLog
    url: changelog/pulse-changelog.yml
- aid: pulse:ivanti-policy-secure-rest-api
  name: Ivanti Policy Secure REST API
  description: REST API for managing Ivanti Policy Secure (formerly Pulse Policy Secure) network access control appliances.
  humanURL: https://help.ivanti.com/ps/help/en_US/IPS/vNow/pcs-pps-rest-api/landingpage.htm
  baseURL: https://{ips-appliance-host}/api/v1
  baseURLNote: Templated on purpose. Ivanti Policy Secure is a customer-run appliance and shares the ICS /api/v1 tree; the
    network-access-control resources sit under /api/v1/configuration/uac. There is no vendor-hosted endpoint for this API.
  tags:
  - NAC
  - Network Access Control
  - Policy
  - Security
  - RADIUS
  - TACACS+
  properties:
  - type: Documentation
    url: https://help.ivanti.com/ps/help/en_US/IPS/vNow/pcs-pps-rest-api/landingpage.htm
  - type: APIReference
    url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ips_spec_configs__using_restapis.htm
  - type: GettingStarted
    url: https://help.ivanti.com/ps/help/en_US/IPS/vNow/pcs-pps-rest-api/overview.htm
  - type: Authentication
    url: authentication/pulse-authentication.yml
  - type: ErrorCatalog
    url: errors/pulse-problem-types.yml
  - type: Conventions
    url: conventions/pulse-conventions.yml
- aid: pulse:ivanti-neurons-zero-trust-rest-api
  name: Ivanti Neurons for Zero Trust Access REST API
  description: REST API for managing Ivanti Neurons for Zero Trust Access (nZTA), providing endpoints for managing zero trust
    access policies, gateways, and user access.
  humanURL: https://help.ivanti.com/ps/help/en_US/nSA/22.x/nsa-zta/api/landingpage.htm
  baseURL: https://{nzta-tenant-host}/api/v1
  baseURLNote: Templated on purpose. nZTA is a per-customer hosted tenant, and Ivanti's own sample code builds request URIs
    as host_url + api_version + resource against the tenant address. Some nZTA surfaces (gateways, analytics, integrations,
    licenses) sit at an unversioned /api/ prefix on the same host — the provider's own inconsistency.
  tags:
  - Secure Access
  - Zero Trust
  - ZTNA
  - Analytics
  - Policy
  - Gateways
  properties:
  - type: Documentation
    url: https://help.ivanti.com/ps/help/en_US/nSA/22.x/nsa-zta/api/landingpage.htm
  - type: APIReference
    url: https://docs.ivanti.com/ps/help/en_us/nsa/22x/nsa-zta/api/api-calls
  - type: GettingStarted
    url: https://docs.ivanti.com/ps/help/en_us/nsa/22x/nsa-zta/api/retrieving-the-authentication-dsid
  - type: Authentication
    url: authentication/pulse-authentication.yml
  - type: Conventions
    url: conventions/pulse-conventions.yml
common:
- type: ParentCompany
  url: https://apis.io/providers/ivanti/
  name: Ivanti
  x-relationship: acquired
  x-evidence: Ivanti's secure-access product family, formerly Pulse Secure, acquired by Ivanti in 2020.
- type: WellKnown
  url: well-known/pulse-well-known.yml
- type: SecurityTxt
  url: well-known/pulse-security.txt
- type: Security
  url: security/pulse-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/pulse-trust-center.yml
- type: Compliance
  url: conformance/pulse-conformance.yml
- type: Conformance
  url: conformance/pulse-conformance.yml
- type: Authentication
  url: authentication/pulse-authentication.yml
- type: ErrorCatalog
  url: errors/pulse-problem-types.yml
- type: Lifecycle
  url: lifecycle/pulse-lifecycle.yml
- type: Deprecation
  url: lifecycle/pulse-lifecycle.yml
- type: ChangeLog
  url: changelog/pulse-changelog.yml
- type: Conventions
  url: conventions/pulse-conventions.yml
- type: RateLimits
  url: rate-limits/pulse-rate-limits.yml
- type: Plans
  url: plans/pulse-plans-pricing.yml
- type: LLMsTxt
  url: llms/pulse-llms.txt
- type: DeveloperPortal
  url: https://www.ivanti.com/support/api
- type: APIReference
  url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/landingpage.htm
- type: GettingStarted
  url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ovw.htm
- type: Support
  url: https://www.ivanti.com/support
- type: Postman
  url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ics_postman_apis.htm
- type: Login
  url: https://hub.ivanti.com/
- type: VulnerabilityDisclosure
  url: security/pulse-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/pulse-domain-security.yml
- type: Website
  url: https://www.ivanti.com/products/connect-secure-vpn
- type: Documentation
  url: https://www.ivanti.com/support/product-documentation
- type: PrivacyPolicy
  url: https://www.ivanti.com/company/legal/privacy-policy
- type: TermsOfService
  url: https://www.ivanti.com/company/legal
- type: StatusPage
  url: https://status.ivanticloud.com/
- type: Blog
  url: https://www.ivanti.com/blog
- type: Community
  url: https://forums.ivanti.com/s/welcome-pulse-secure?language=en_US
- type: Features
  data:
  - name: SSL VPN Remote Access
    description: Secure remote access to corporate resources through SSL VPN tunnels with granular access policies.
  - name: Zero Trust Network Access
    description: Identity-aware, application-level access control without exposing network resources.
  - name: Network Access Control
    description: Enforce security policies on endpoints before granting network access with 802.1X and agent-based checks.
  - name: Multi-Factor Authentication
    description: Integrate with MFA providers for strong authentication on VPN and network access.
  - name: Host Checker
    description: Validate endpoint compliance with security policies before granting access.
  - name: Role-Based Access Control
    description: Define granular access policies based on user roles, device type, and compliance status.
- type: UseCases
  data:
  - name: Remote Workforce Access
    description: Provide secure remote access to corporate applications and resources for distributed teams.
  - name: Zero Trust Architecture
    description: Implement zero trust security with per-application access controls and continuous verification.
  - name: BYOD Management
    description: Securely enable bring-your-own-device access with endpoint compliance checking.
  - name: Partner and Contractor Access
    description: Grant controlled, time-limited access to third-party partners and contractors.
- type: Integrations
  data:
  - name: Microsoft Active Directory
    description: Authenticate users against Active Directory for single sign-on and role mapping.
  - name: RADIUS Servers
    description: Integrate with RADIUS for centralized authentication and accounting.
  - name: SIEM Platforms
    description: Forward access logs and security events to SIEM platforms for monitoring and analysis.
  - name: MDM Solutions
    description: Integrate with mobile device management solutions for endpoint compliance verification.
  - name: Identity Providers
    description: Connect with SAML and OIDC identity providers for federated authentication.
- type: Integrations
  url: https://www.ivanti.com/partners
integrations:
- name: Two people performing a handshake.
- name: 5-star CRN Partner Program award banner
- name: Carahsoft-Blue-Logo
- name: logicalis
- name: Acceron
- name: m tech
- name: innovads
- name: sector27
- name: Lenovo
- name: infinigate
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-29'
  status: enriched
  artifacts_added: 12
  pass: local-v1
x-parent: ivanti
x-relationship: product

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/pulse"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/pulse/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/pulse/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.