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

McAfee (Trellix) Authentication API

Session authentication and management

McAfee (Trellix) Authentication API is one of 26 APIs that McAfee (Trellix) 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, and authentication docs.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 5.10.

Requests are made against a single base URL, https://{epo-server}:8443/remote.

5 operations 5 paths 2 schemas 1 DELETE4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
5.10
Base URL
https://your-epo-server:8443/remote
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

McAfee (Trellix) Authentication API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using ePO administrator credentials. Credentials are transmitted as a Base64-encoded username:password pair.

Paths & Operations 5

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

Authentication 5

Session authentication and management

POST
/v2/login
McAfee Authenticate and create session
login body → 200401
DELETE
/v2/logout
McAfee End current session
logout → 200401
POST
/iam/v1.1/token
McAfee Obtain access token
getToken body → 200401
POST
/login
McAfee Authenticate and create session
login body → 200401
POST
/logout
McAfee End current session
logout → 200401

Schemas 2

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

TokenResponse
object
4 properties
LoginResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mcafee-authentication-api-openapi.yml Raw ↑

Other APIs McAfee (Trellix) publishes across the network.

McAfee Threat Intelligence Exchange (TIE) API
McAfee Data Exchange Layer (DXL) API
McAfee (Trellix) Alarms API
McAfee (Trellix) Cases API
McAfee (Trellix) Core API
McAfee (Trellix) Data Sources API
McAfee (Trellix) Detections API
McAfee (Trellix) Devices API
McAfee (Trellix) Events API
McAfee (Trellix) File Operations API
McAfee (Trellix) Investigations API
McAfee (Trellix) Lists API
Where this information came from

This is an independent, third-party profile of McAfee (Trellix) 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.