Skip to main content

API tokens

Tokens let your own systems push into Cogentic. Disable one to pause a sync; delete one only when you mean it.

Settings, then API tokens. A token is how your own systems reach Cogentic: pushing customers and the wallets they have declared. You need Admin or Owner to see this page at all.

Generating one

  1. 1

    Name it after the system that will use it

    Only your organisation sees the name. Nightly customer sync tells you what breaks if you delete it. Token 3 does not.

  2. 2

    Choose what it may do

    Read-only, or read and write. A sync that pushes customers needs read and write. Anything that only reads should not have more.

  3. 3

    Copy it now

    Afterwards the list shows only the last few characters, enough to tell one token from another.

Disable, or delete

DisableDelete
Stops workingYesYes
Can be undoneYes, the same token works againNo
Use it whenPausing a sync, or isolating a problemThe token is compromised, or gone for good

The list shows when each token was last used, or that it never has been. A token that has never been used is usually a sync that was never finished.

Related

Last checked against the product on .


Compliance intelligence for VASPs

Regulation moves fast. Cogentic moves faster.

See how your compliance team gets the intelligence to act decisively. Across every jurisdiction. For every transfer.