Report legacy account migration
const url = 'https://example.com/api/v1/system/integrations/legacy-migration';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/system/integrations/legacy-migration \ --header 'Authorization: Bearer <token>'Return the latest migration state and safe error codes for legacy accounts that did not move to Connected Accounts. A signed-in User with data scope is required. Requests can return 401 if the session is missing or 403 if the User lacks data scope. Route: /api/v1/system/integrations/legacy-migration. Inputs: . Safe reads can use bounded retries.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Safe Settings view of migration state, with User-scoped IDs and no secret data (#407, DESIGN §49 I6).
object
User-scoped migration failure with stable cache identity and a safe code only (§49 I6, #407).
object
Safe reasons why a legacy account could not link to a shared account (#407, DESIGN §49 I6).
Observable result of legacy account reconciliation (#407, DESIGN §49 I6).
Example
{ "error_code": "database", "failed_accounts": [ { "error_code": "database" } ], "state": "pending"}The standard API error response: { "error": { ... } }.
object
Example
{ "error": { "code": "bad_request" }}The standard API error response: { "error": { ... } }.
object
Example
{ "error": { "code": "bad_request" }}