How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Citrix Authentication API

Login and session management

Citrix Authentication API is one of 27 APIs that Citrix publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and a getting-started guide.

This API exposes 7 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 5 base URLs: https://{netscaler-ip}/nitro/v1, https://api.cloud.com, https://api.citrixcloud.jp, https://{xms-server}:4443/xenmobile/api/v1, https://{storefront-server}/Citrix/Store.

7 operations 7 paths 1 schemas 7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{customer-id}.xendesktop.net
Authentication
API Key, HTTP Bearer, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 4

Citrix Authentication API declares 4 security schemes for authenticating requests. An API key is passed in the cookie as NITRO_AUTH_TOKEN (nitroAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as auth_token (authToken). An API key is passed in the header as Csrf-Token (csrfToken).

  • nitroAuth — Session cookie from NITRO login
  • bearerAuth — OAuth 2.0 bearer token from client credentials grant
  • authToken — Authentication token from login endpoint
  • csrfToken — CSRF token from session cookie for POST requests

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication 7

Login and session management

POST
/config/login
Citrix Log in to NITRO
login body → 200401
POST
/cctrustoauth2/{customerId}/tokens/clients
Citrix Obtain access token
getAccessToken 1 param body → 200401
POST
/authentication/login
Citrix Authenticate to the API
login body → 200401
POST
/authentication/logout
Citrix Log out
logout → 200
POST
/Authentication/GetAuthMethods
Citrix Get authentication methods
getAuthMethods → 200
POST
/ExplicitAuth/Login
Citrix Log in with explicit credentials
explicitLogin body → 200401
POST
/ExplicitAuth/Logout
Citrix Log out
explicitLogout 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is TokenResponse (3 properties). Each schema is shown below with its type and property counts.

TokenResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

citrix-authentication-api-openapi.yml Raw ↑

Other APIs Citrix publishes across the network.

Citrix Workspace API
Citrix Analytics API
Citrix Monitor Service OData API
Citrix StoreFront Store Services API
Citrix StoreFront Authentication SDK
Citrix Access Policies API
Citrix Application Domains API
Citrix Applications API
Citrix Certificates API
Citrix Content Switching API
Citrix Delivery Groups API
Citrix Devices API
Where this information came from

This is an independent, third-party profile of Citrix Authentication API, 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.