BusyBot

Reference · Credentials

Wise API credentials

Used by 2 BusyBot nodes.

Type wiseApi 3 fields

The Wise credential holds a personal or business API token plus an environment switch for live or test. Some sensitive operations additionally require strong customer authentication, which is what the optional RSA private key is for.

Fields

FieldTypeRequiredNotes
API Token
apiToken		 password Yes Your Wise API personal or business token.
Environment
environment		 string Yes "live" or "test"
Private Key (Optional)
privateKey		 password No Optional RSA private key for SCA.

Getting your credentials

  1. Sign in to Wise — wise.com for live, or the Wise sandbox for testing. They are entirely separate systems with separate accounts and tokens.
  2. Open the settings area covering API tokens and create one, choosing read-only or full access as appropriate.
  3. Copy the token into the credential’s API Token field.
  4. Set Environment to live or test to match where the token came from.
  5. For operations requiring strong customer authentication, register a public key with Wise and paste the matching RSA private key into the credential. Leave it empty otherwise.

Permissions and scopes

Wise tokens can be issued read-only, which is the right choice for any workflow that only reports balances or transfers. Full-access tokens can move money — scope deliberately and store the credential accordingly.

SCA applies to particularly sensitive operations. Without the private key configured, those specific calls are rejected even though the token itself is valid.

Troubleshooting

  • 401 Unauthorized — the token belongs to the other environment. Live and sandbox tokens are not interchangeable.
  • SCA challenge or 403 on a sensitive operation — the RSA private key is not configured, or does not match the public key registered with Wise.
  • 403 on a write operation — the token was issued read-only.
  • Profile not found — the token’s account does not have that profile; personal and business profiles are distinct.

Frequently asked questions

What is the private key field for?

Strong customer authentication. Some sensitive Wise operations require a signed challenge, so those calls fail without a private key matching the public key registered on your account — even though the token is valid.

Are live and test tokens interchangeable?

No. The Wise sandbox is a separate system with its own accounts and tokens, so the Environment field must match where the token came from.

Should I use a read-only token?

For any workflow that only reads balances or transfers, yes. A full-access token can move money, which is not something an automation needs unless it explicitly should.

Nodes that use Wise API

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.