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 Service Principals API

Manage service principals for API automation

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

Tagged areas include Service Principals. 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 4 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.cloud.com, https://api.citrixcloud.jp.

4 operations 2 paths 2 schemas 1 DELETE2 GET1 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
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Citrix Service Principals API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 bearer token from client credentials grant

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Service Principals 4

Manage service principals for API automation

GET
/serviceprincipals
Citrix List service principals
listServicePrincipals 1 param → 200401
POST
/serviceprincipals
Citrix Create a service principal
createServicePrincipal 1 param body → 201400401
GET
/serviceprincipals/{principalId}
Citrix Get a service principal
getServicePrincipal 2 params → 200401404
DELETE
/serviceprincipals/{principalId}
Citrix Delete a service principal
deleteServicePrincipal 2 params → 204401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ServicePrincipal (5 properties), CreateServicePrincipalRequest (1 property). Each schema is shown below with its type and property counts.

CreateServicePrincipalRequest
object
1 property 1 required
ServicePrincipal
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

citrix-service-principals-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 Authentication API
Citrix Certificates API
Citrix Content Switching API
Citrix Delivery Groups API
Where this information came from

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