MODULE 01 // LESSON 02
Request Anatomy
The First Signal
A request is a contract. The structure you send, the headers you include, and the endpoint you target tell ABIS exactly what you need. Let's dissect the anatomy of a perfect behavioral signal.
VISUAL: Transparent glass cube floating in neon data center // JSON payload assembling piece by piece
CORE ARCHITECTURE
The 4 Components
An ABIS request isn't random; it requires four specific keys to unlock the door: 1. HTTP Method: Usually POST for analysis. 2. Endpoint: The specific service URL. 3. Headers: Authentication tokens & content types. 4. Payload: The behavioral JSON body.
PAYLOAD SCHEMA
Strict Typing
ABIS rejects ambiguity. Your JSON payload must follow a strict schema containing four non-negotiable fields: user_id, session_id, event_type, and timestamp. Missing any of these breaks the causal chain, forcing the system to reject the signal with a 400 Bad Request.
// DEPLOYMENT CHECKLIST
✓Authentication header included (API Key)
✓Content-Type set to application/json
✓REQUIRED: user_id present
✓REQUIRED: session_id present
✓REQUIRED: event_type present
✓REQUIRED: timestamp (ISO 8601)
KNOWLEDGE CHECK // Q02
What are the four non-negotiable fields required in every ABIS payload?
A. user_id, email, password, timestamp
B. user_id, session_id, event_type, timestamp
C. api_key, secret, user_id, action