New features
📅 On May 21, 2026, public onboarding URLs will switch to the current onboarding API for all new onboardings. The previous public onboarding interface will be retired.
If you use public onboarding URLs without any prefilling, no action is needed. If you prefill onboarding fields through the API before redirecting to the onboarding URL, refer to the migration guide or reach out to your Swan contact to plan your migration.
Improvements
✏️ Custom details for the Other purpose: when a supporting document with the purpose Other is requested, a new purposeDetails field on the SupportingDocumentPurpose object specifies what document is needed (for example, "Company structure chart"). Query purposeDetails under requiredSupportingDocumentPurposes and display the description to your account holders to guide their upload. See the supporting documents guide for details.
API updates
Upcoming breaking changes
⏱️ On May 20, 2026, the consent notification endpoint timeout will be reduced from 3 seconds to 2 seconds. This change applies to consent flows (sensitive operations), not OAuth2 flows such as login or authentication. The shorter timeout gives Swan enough time to fall back to text message within the 3.5-second 3-D Secure (3DS) window.
If your integration uses in-app consent notifications, make sure your endpoint responds within 2 seconds. Aim for 1.5 to 1.8 seconds to leave margin. If your response is slower, Swan falls back to text message. No action is required if you don't use in-app consent notifications.
⚠️ On September 30, 2026, the previous onboarding API will be shut down and all previous endpoints will no longer be available. The current onboarding API has been generally available since March 2026. If you're still using the previous API, migrate before this date. Refer to the migration guide or reach out to your Swan contact to plan your transition.