Migration at a glance
The embed pattern is unchanged — you still display a URL in an iframe or share it directly. Only the endpoint you call on the server side is different, and the new URL format uses
https://dash.nectarclimate.com/p/i/{token} instead of the legacy p/connect/... path.
Do I need to migrate existing magic links?
No. Outstanding magic-link URLs continue to work. You only need to update the endpoint your server calls when creating new links.Legacy request and response reference
The legacy endpoints remain available for backward compatibility; the examples below are preserved for reference only.Create a company magic link (legacy)
Create a company magic link (legacy)
publicCompanyId, companyMagicLinkSecret, and magicLinkUrl (shape:
https://dash.nectarclimate.com/p/connect/{publicCompanyId}/{companyMagicLinkSecret}).Create an edit magic link for an existing connection (legacy)
Create an edit magic link for an existing connection (legacy)
publicCompanyId and connectionMagicLinkSecret (shape:
https://dash.nectarclimate.com/p/connect/{publicCompanyId}/workflow/{connectionMagicLinkSecret}).Next steps
Connection invitations
The recommended replacement for all magic-link use cases.
Sandbox testing
Test invitation flows with mock data.
Webhooks
Listen for
connection.created.v2 and connection.updated.v2 events.