AFAS is changing how other systems connect to AFAS Profit. To keep your TinQwise connection working, your AFAS administrator sets up a new connection once. It takes one short session, and we take care of the rest!
From 31 August 2027, AFAS only accepts connections based on OAuth. We recommend you do the setup before 1 May 2027, so we have time to check everything well before that date.
Your employees will notice nothing! Their accounts, groups and progress stay exactly as they are.
Who does what
Who | What |
You (your AFAS administrator) | Create a new connection in AFAS and send us three details |
Us (TinQwise) | Switch your platform over to the new connection and tell you when you're done |
Before you start
You need someone with administrator rights in AFAS Profit
Keep our email at hand, as it lists the connectors the new connection needs
Most platforms have one GetConnector, which lets TinQwise read your employee data from AFAS
If your platform also sends results back to AFAS, you have an UpdateConnector too
Your part: set up the new connection in AFAS
đ Good to know
Most customers run AFAS Profit in Dutch. Where the names in AFAS differ from the English ones in this article, the Dutch name is shown in brackets.
Step 1: Create a new app connector
An app connector is the connection TinQwise uses to reach your data in AFAS. AFAS explains every screen of this wizard in its own guide: App connector with OAuth (in Dutch). Keep it open next to this article.
In AFAS Profit, go to General > Management > App connector (Dutch: Algemeen > Beheer > App connector)
Click New (Dutch: Nieuw)
Choose authentication type OAuth (Dutch field name: Authenticatietype)
Choose flow type Client credentials (Dutch field name: Type OAuth flow), the right choice for a connection that runs on its own every night, with no one logging in
You can't change the authentication type of your current connector, so you create a new one.
Step 2: Link the same connectors as today
Link the connectors listed in our email to the new app connector. This way the new connection gives us exactly the same data as the old one.
Step 3: Choose who the connection runs as
Select the AFAS user that the connection runs as
Open the authorisation tool (Dutch: Autorisatie tool) and give this user's group access to the data filters (Dutch: filterautorisatie). You don't need to give rights on functions, tabs or actions
âď¸ Tip
Pick a functional account, not someone's personal account. If that person leaves and their account is blocked, the connection stops.
Step 4: Leave IP restrictions off
AFAS lets you limit a connector to certain IP addresses. Please don't, as our platform doesn't use a fixed IP address and a restriction would block the connection.
Step 5: Copy the client ID and client secret
When you finish the wizard (click Finish, Dutch: Voltooien), AFAS shows a client ID and a client secret. Copy both and keep them somewhere safe.
đ§ Be careful
AFAS shows the client secret only once. If you lose it, generate a new one in AFAS. The old secret stops working at that moment, so send us the new one.
Step 6: Send us three details
Send us the following, the way our email describes:
Client ID
Client secret
Your AFAS environment number, which is the number in your AFAS address, for example 12345 in
https://12345.rest.afas.online
đ§ Be careful
Please don't send the client secret in a regular email. Anyone who has it can read the data the connector gives access to.
That's all you need to do!
Our part: what happens next
We test the new connection with the details you sent
Once it gives the same result as your current connection, we switch your platform over
We tell you when it's done and when you can remove your old connector
Until we tell you, keep your old connector in place. You don't need to do anything else!
Frequently asked questions
Do our employees need to do anything?
Do our employees need to do anything?
No, they won't notice the switch!
Can we keep using our current connection?
Can we keep using our current connection?
Until 31 August 2027, yes, however after that, AFAS no longer accepts it and your platform stops receiving updates from AFAS.
We send results back to AFAS too. Do we need two new connectors?
We send results back to AFAS too. Do we need two new connectors?
No, just link both the GetConnector and the UpdateConnector to the same new app connector!
We have more than one TinQwise platform on the same AFAS environment.
We have more than one TinQwise platform on the same AFAS environment.
One new app connector can serve all of them, so link every connector listed in our email and tell us which platforms it covers.
Something went wrong. Who do I contact?
Something went wrong. Who do I contact?
Reply to the email you received from us, or contact service@tinqwise.com.