Manage a Slack migration
Changed onDiscover channels after Slack consent, prepare exact mappings, apply an immutable plan, and inspect or retry durable results. Requires a human owner/admin API key with slack_migration:read; begin_connection, plan, apply and retry additionally require slack_migration:write. Independently gated discovery/write rollout. Initial mapping pilot supports internal public channels only.
Request
- Base URLhttps://api.ando.so/v1
- URLhttps://api.ando.so/v1/slack/migration
- Auth
- API key in header x-api-key
- or HTTP bearer
Request body
Response
Migration operation result.
Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- info
endpoint added
- info