Adikteev credentials

Configure the Adikteev credential fields offered by Platform Migration.

Current delivery: HTTP batch

  • The credential form does not implement the provider’s complete native API or a choice of sync actions.
  • Current delivery sends JSON row batches or a table-and-rows envelope. A compatible receiving endpoint must accept that format; a native provider API may require a separate adapter.
  • Check the migration status and logs, then verify the records in the destination.

Configure the destination

  1. Open Platform → Migration and choose New Migration.
  2. Connect the source, select its tables, and choose Adikteev as the destination.
  3. Enter the credential fields below and use Test connection. Read the test scope before relying on its result.
  4. Confirm a compatible delivery endpoint is configured before attempting a transfer.

Credential fields

UsernameRequired
Adikteev account username.
PasswordRequired
Adikteev account password.

What the connection test checks

The connector requests its configured test endpoint after preparing credentials. This verifies that request, rather than every permission needed to write records. Check delivery with a small migration.

Use the credential inputs or a supported Secret Handler reference. Keep credentials out of source tables and shared examples. Inspect the run status and logs, then verify the destination content.

Need help with your setup? Visit the Help Center or contact Genorbex.