Developer API

Customer intelligence feeds with explicit source and freshness metadata.

TrapLayer customer APIs are tenant-scoped, tier-gated, and designed for SIEM, SOAR, reporting, and defensive enrichment workflows.

Reference Data Notice

Examples are synthetic

All API payloads, indicators, IP addresses, timestamps, actor references, and SIEM examples shown on this page are fictional documentation examples. They are provided only to describe response structure and integration behavior, and must not be treated as live TrapLayer intelligence, customer telemetry, threat attribution, or evidence of activity by any real system or person.

Authentication

Use a customer API key

API keys are managed from the customer portal and inherit the tenant subscription, data tier, API-call allowance, and feed limits.

Authorization: Bearer tl_live_or_test_customer_key
X-TrapLayer-API-Key: tl_live_or_test_customer_key

Use one key per integration, keep keys server-side, rotate keys after staff or vendor changes, and cache responses according to indicator TTL.

Core endpoints

EndpointPurposeTier
GET /api/customer/intel.jsonCustomer-safe event indicators with risk, confidence, source, TTL, and recommended action.Yellow 1+
GET /api/customer/iocs.jsonSource IP IOC feed for block, challenge, enrichment, and hunting workflows.Yellow 1+
GET /api/customer/payloads.jsonPayload hashes, families, delivery vectors, and related indicators without raw payload bodies.Yellow 2+
GET /api/customer/analytics.jsonCampaign, actor-hypothesis, behavior, MITRE/CVE, and executive-summary analytics.Yellow 3+
GET /api/customer/reports/latest.pdfLatest customer brief or executive report as a protected PDF download.Plan-gated

CEF and STIX-style variants are available at matching .cef and .stix.json endpoints when enabled for the tenant.

Example response

This sample uses reserved documentation values and synthetic intelligence fields.

{
  "generated_at": "2026-10-05T21:10:00Z",
  "example_data": true,
  "notice": "Synthetic documentation sample. Not live intelligence.",
  "data_contract": {"tier": "yellow_2", "label": "Yellow 2 SOC intelligence"},
  "indicators": [
    {
      "indicator_id": "demo-indicator-0001",
      "type": "source_ip",
      "value": "203.0.113.24",
      "classification": "ssh_login_failed",
      "source": "synthetic-demo:ssh",
      "observed_at": "2026-10-05T21:05:12Z",
      "risk_score": 82,
      "confidence_score": 94,
      "ttl_hours": 168,
      "recommended_action": "block_or_challenge"
    }
  ]
}

Rate Limits

Allowance and pagination

Each tenant has a monthly API-call allowance and per-request result limit. Use limit, since, and cached successful responses. A 429 means the monthly allowance is exhausted or the request is too aggressive.

Freshness

Source transparency

Customer-facing panels and API payloads should be treated as actionable only when the source, generated timestamp, confidence, and stale/cache warnings are acceptable for your workflow.

SIEM examples

The commands and field names below demonstrate integration shape only. Output examples should be generated from your tenant feed after authentication.

# Splunk
curl -s -H "Authorization: Bearer $TRAPLAYER_API_KEY" \
  "https://traplayer.com/api/customer/intel.json?limit=250" \
  | jq -c '.indicators[]'

# Microsoft Sentinel custom table fields
IndicatorValue_s, Classification_s, RiskScore_d, ConfidenceScore_d,
RecommendedAction_s, Source_s, ObservedAt_t, TtlHours_d

Error codes

401Missing, invalid, inactive, or revoked API key.
402Billing status does not currently allow intelligence access.
403The tenant data tier does not include the requested feed.
429API-call allowance or rate limit exceeded.
5xxTrapLayer service or collector path error. Retry with backoff and use cached data if available.

Versioning and changelog

The current customer API is v1-compatible and additive by default. New fields may appear without breaking existing keys. Breaking changes require a published migration window and customer notice.

Intelligence summary

Summary