Schema reference changed in POST /v2/profiles/{profileId}/third-party-transfers request body: "inline" → "CreateThirdPartyTransferRequestContent"
- Affected surface
- POST /v2/profiles/{profileId}/third-party-transfers
What changed
Schema reference changed in POST /v2/profiles/{profileId}/third-party-transfers request body: "inline" → "CreateThirdPartyTransferRequestContent" Affected surface: POST /v2/profiles/{profileId}/third-party-transfers. Root cause: endpoint `POST /v2/profiles/{profileId}/third-party-transfers`. Detected at Wed, 27 May 2026 01:19:23 UTC UTC.
Diff
{
"current_value": "CreateThirdPartyTransferRequestContent",
"path": "POST /v2/profiles/{profileId}/third-party-transfers",
"previous_value": "inline",
"schema_path": "POST /v2/profiles/{profileId}/third-party-transfers request body"
}Likely impact
This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.
Recommended action
Diff your serializers against the new schema. The diff above shows what moved.
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.
