A login represents a set of credentials required to access the accounts and transactions through a specific provider.

Within Spectre, a login can have one of the following statuses:

  • active - the current set of credentials is valid and allows us to properly fetch the data;
  • inactive - an error appeared while fetching the login. An inactive login cannot be refreshed;
  • disabled - in case of non-compliance with our Terms of Service, we can contact the application’s owner and disable the login.
A Login represents a permanent connection of a specific customer to a bank. A single end-user represents a single customer in Spectre. When creating a login you should make sure the customer already exists to avoid creating a new customers with the same login. Also, we don’t recommend creating multiple connections for the same customer with the same online banking access credentials.

Login Actions

The login supports four main operations:

  • Connect
  • Reconnect
  • Refresh
  • Remove

In order to use any of these actions without interacting with Salt Edge Connect, you must contact us to activate the corresponding routes for logins.


Connecting is used whenever a new login has to be created. In order to Connect a new login, you should obtain a token and redirect the user to the Salt Edge Connect page.

You can find out more about the creation and redirect process in the Salt Edge Connect section of this guide.

Once your application has received a success callback, you can query the information about the login, its accounts and transactions.


Reconnecting is used in two cases:

  • the credentials for the login have changed;
  • the provider requires an interactive field (SMS, Captcha, etc.).

In order to Reconnect a specific login, your application should supply the login_id during the token request process.


If a login is automatic and is active, you can trigger an update of the login using the refresh route. We will send a success callback once we’ve finished updating the data.

We recommend you trigger a refresh on the user’s logins when the user signs in. This way, they will always have up-to-date data.


You can remove all the data associated with a login – the login itself, all of its accounts and transactions.