The connector signs in with Oauth2, using an application you create on your own Sellsy account. Splash never sees your Sellsy password, and you can revoke the access at any time from Sellsy.

1. Create the Oauth2 application in Sellsy

In Sellsy, open Settings > Api & Integrations > Oauth2 applications, then create an application:

• give it a name that will be recognizable later, Splash Sync for instance;
• set its redirect uri to the one shown on your Splash server configuration page;
• grant it every scope the connector needs, listed in Required scopes.

Sellsy then gives you a Client ID and a Client Secret.

[!IMPORTANT] Keep the Client Secret safe: Sellsy shows it once. If you lose it, generate a new one and update it in Splash.

2. Declare the application in Splash

On your Splash server, open the Sellsy connector configuration and fill in:

Save: the page now offers to connect.

3. Authorize the connection

Click Connect to the Api. Sellsy asks you to log in and to confirm the access you are granting, then sends you back to Splash with a token.

Once connected, the configuration page shows:

• the Api access scopes, with any scope still missing on your application;
• the Vat rates and payment methods read from your account;
• the webhooks the connector installed to receive your changes.

[!TIP] The access token expires after one hour and is renewed automatically, as long as the connection has not been revoked in Sellsy. The page tells you when it expires.

Troubleshooting

[!NOTE] A refused connection is always explained on screen, with the message Sellsy itself returned.

Some scopes missing

The connector works, but every object covered by a missing scope stays out of reach. Add the scope on your Sellsy application, then connect again.

The connection is refused

Check that the redirect uri declared in Sellsy is exactly the one shown by Splash, including the scheme and any trailing path.