LoopsSchemaBehavioral
Response schema changed for GET /v1/email-messages/{emailMessageId} (EmailMessageResponse)
- Affected surface
- GET /v1/email-messages/{emailMessageId}
- Affected field
- EmailMessageResponse
What changed
Response schema changed for GET /v1/email-messages/{emailMessageId} (EmailMessageResponse) Affected surface: GET /v1/email-messages/{emailMessageId}. Root cause: schema `EmailMessageResponse`. Detected at Wed, 03 Jun 2026 01:52:15 UTC UTC.
Diff
{
"path": "GET /v1/email-messages/{emailMessageId}",
"removed_fields": [
"emailMessageId",
"success"
],
"schema_path": "schema EmailMessageResponse"
}Likely impact
The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.
Recommended action
Diff your serializers against the new schema. The diff above shows what moved.
Related changes
Other endpoints affected by the same root cause.
Catch changes like this on every API you depend on.
Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.