Under the V1 API a connect link, once completed by the end user, returned the destination_id it had created. The V2 activation connect link returns the same fields before and after completion (id, uri, expiration, expired, revoked, group_id, type, redirect_uri) and never names the activation it created.

For an embedded customer that means matching the new activation back to the pending link by listing activations in the link’s group and picking the one created after the link that we don’t already hold. That works, and support has confirmed it’s the intended approach, but it can’t tell two links apart if a customer has two of the same type open in one group, and it means a list call and a timing heuristic where a single field would do.

The request: once a connect link has been completed, expose the created activation’s id on the link object (and ideally a completed_at timestamp), the way the V1 link exposed its destination id.