Tessian Endpoints API is one of 10 APIs that Tessian publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
12 operations
across 9 paths,
and defines 25 schemas.
It is described by OpenAPI 3.0.0, at version 1.0.1.
Requests are made against 2 base URLs: https://your-domain.tessian-platform.com, https://your-domain.tessian-app.com.
12 operations9 paths25 schemas1 DELETE7 GET3 POST1 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.0
API Version
1.0.1
Base URL
https://your-domain.tessian-platform.com
Resource Areas
1
Paths & Operations 12
Across 9 paths, the API surfaces 12 operations — 1 DELETE, 7 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are Trigger (18 properties), Anomaly (9 properties), BaseEmailDetails (8 properties), ScoresDatapoint (7 properties). Each schema is shown below with its type and property counts.
ScoresDatapoint
object
risk drivers
7 properties7 required
DefenderEvent
BaseEmailDetails
object
Details about an email.
8 properties8 required
GroupMembers
array
Input members data for adding/removing members from group, expects one of address or domain
ArchitectEvent
Anomaly
object
9 properties
Event
BaseEvent
object
Properties that all events have.
5 properties5 required
Attachment
object
Details about an attachment
2 properties
EnforcerTrigger
Represents a trigger by the Enforcer module
ConstructorTrigger
Represents a trigger by the Constructor module (legacy)
Links
object
Contains URLs that are associated with this event.
1 property
SyncState
string
How far along in the onboarding process the user is
GroupMetadata
object
Information about a group.
4 properties1 required
OutboundEmailDetails
object
1 property1 required
DomainMember
object
1 property1 required
DefenderTrigger
Represents a trigger by the Defender module
ArchitectTrigger
Represents a trigger by the Architect module
InboundEmailDetails
object
1 property1 required
AddressMember
object
1 property1 required
Trigger
object
18 properties
GuardianEvent
OutboundTrigger
Represents a trigger for one of the outbound modules
GuardianTrigger
Represents a trigger for the Guardian module
UserMonitoringStatus
string
How well we have been connecting with the user
Specification
The full machine-readable OpenAPI contract behind this narrative.