Get Pillars

GET/customers/{clientId}/pillars

Returns the four-pillar breakdown alongside the most recent score date. Use this to understand which dimension of resilience is driving the composite score.

Path parameters

clientIdstringrequired

Client ID issued by the customer’s ORION environment (an opaque identifier beginning with osc_)

Response fields

clientIdstringrequired

The Client ID the breakdown was retrieved for

scoreDatestringrequired

ISO calendar date the breakdown corresponds to (YYYY-MM-DD, UTC)

pillarScoresobjectrequired

Individual pillar scores (0–100 each)

properties

structuralIntegrityinteger

Network architecture robustness

failureResistanceinteger

Network continuity under failure scenarios

deviceHealthinteger

Current device health and risk status

recoveryCapabilityinteger

Expected recovery performance under simulated failures

Example

curl https://api.overspace.io/orion/v1/customers/osc_x7k2q9_9f8b7c6d5e4f3a2b1c0d9e8f7a6b5c4d/pillars \
  -H "x-api-key: your-api-key"

const res = await fetch(
  'https://api.overspace.io/orion/v1/customers/osc_x7k2q9_9f8b7c6d5e4f3a2b1c0d9e8f7a6b5c4d/pillars',
  { headers: { 'x-api-key': process.env.API_KEY } },
);
const pillars = await res.json();

import os
import requests

response = requests.get(
    "https://api.overspace.io/orion/v1/customers/osc_x7k2q9_9f8b7c6d5e4f3a2b1c0d9e8f7a6b5c4d/pillars",
    headers={"x-api-key": os.environ["API_KEY"]},
    timeout=10,
)
response.raise_for_status()
pillars = response.json()

{
  "clientId": "osc_x7k2q9_9f8b7c6d5e4f3a2b1c0d9e8f7a6b5c4d",
  "scoreDate": "2026-03-18",
  "pillarScores": {
    "structuralIntegrity": 84,
    "failureResistance": 82,
    "deviceHealth": 86,
    "recoveryCapability": 84
  }
}

Reading pillars over time

The pillar breakdown is most useful over time. The snapshots below follow one organization through a four-quarter transformation program: note that Device Health was strong from day one, yet the composite graded Improve, because resilience depends on the architecture connecting healthy devices and on recovery around core business processes.

Pillar	Baseline 2025-03-19	Foundations 2025-09-15	Cutover dip 2025-10-20	Sustained 2026-03-18
Structural Integrity	36	58	52	84
Failure Resistance	38	56	50	82
Device Health	74	76	76	86
Recovery Capability	36	58	58	84
Composite	46	62	59	84

Pulling the breakdown daily and storing each snapshot, as in the complete report pattern, builds exactly this history for any organization you’re authorized to assess. For the full story behind these snapshots, see Security Transformation.