FoundryNet / Error codes / HTTP / REST 422
HTTP / REST error code

422 — Unprocessable Entity — body shape is wrong

The request parsed as JSON but failed validation. The response body names the offending field.

Start free HTTP / REST → canonical

Diagnosis

When you hit this


Resolution

How to fix it

  1. Send the series every time
    Include time_series with at least 16 points, oldest to newest.
  2. Validate the canonical field name
    Query the coverage endpoint to confirm the field exists before sending it.
  3. Read the error body
    It names the failing field rather than just rejecting the request.

Normalization

What Forge does about it

The statelessness is the thing to internalize: prediction endpoints do not fetch history for you. Supplying {machine_id, field, threshold} and expecting Forge to look up the series is the single most common 422.


Connect

Normalize HTTP / REST telemetry

One MCP endpoint serves every protocol adapter. 16,908 curated mappings, 366 canonical fields.

# normalize telemetry from HTTP / REST — and 13 other protocols
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header 'Authorization: Bearer YOUR_FORGE_KEY'
✓ forge connected — 32 tools available

Related

Keep reading

Other HTTP / REST codes: 401 402 403 429

Equipment that speaks HTTP / REST: Caterpillar Cummins Haas MiR (Mobile Industrial Robots) Universal Robots OTTO Motors 6 River Systems AGILOX Detroit Diesel Fetch Robotics

HTTP / REST protocol hub

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS EtherNet/IP PROFINET / S7 BACnet/IP J1939 (CAN) MTConnect ROS 2 (DDS) SNMP MAVLink CSV ingest

All error codes · All OEMs · All protocols

Industrial AI fails at the data layer. The Machine Agent explains why, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.