Skip to content

AFAS Profit

Artific Connect · AFAS gives a key two tools over the GetConnectors and UpdateConnectors your organisation has already coupled to its own App Connector in Profit — a read and a write, both shaped exactly as your own connector configuration decides, not a fixed AFAS object model. It installs from the Marketplace like any other bundle.

What you get

One toolset, afas, holding the two connectors, plus a skill that tells the model AFAS's simple filter syntax and what to confirm before writing.

What your Profit administrator builds first

In Profit, build an App Connector, and couple to it every GetConnector and UpdateConnector you want this bundle to reach. AFAS itself refuses a call naming a connector that is not coupled — the App Connector is also where you generate the token.

What you supply at install

Your environment lives at https://<your-environment-id>.rest.afas.online, one host under every connector you coupled, so this bundle asks for it once:

  • afas_environment_url — paste https://<your-environment-id>.rest.afas.online with your own environment id filled in. Each call adds /ProfitRestServices/connectors/<connector name> to this one address itself, with the connector's own name given as part of the call rather than typed here — the model, or the person it is helping, names which coupled connector to read from or write to each time.

And afas_credential, the token generated in your App Connector, with AFAS's own AfasToken scheme included exactly as shown — this is not the plain bearer scheme, so the prefix is yours to type:

{ "type": "bearer", "secret": "AfasToken <base64 token from Profit>" }

Until both are supplied the subscription waits at needs configuration.

Before it works

Your administrator has to allow your environment's host in the key's own egress policy.

Good to know

  • Verified 2026-09-24 on help.afas.nl: the base URL shape, that the Authorization header reads AfasToken <base64 of the token>, and that "only the coupled GetConnectors" and "only the coupled UpdateConnectors" can be called through a given App Connector — AFAS itself is what refuses a call naming an uncoupled connector, whatever address or connector name this bundle sends. That is why this bundle asks for the connector's name on every call instead of baking one read connector and one write connector in at install: the coupling in Profit is the actual boundary, and naming a connector this token is not coupled to is refused by AFAS either way.
  • Verified 2026-09-24 on AFAS's own klantportaal pages: classic App Connector tokens are being retired for OAuth. Tokens get an end date of 15 February 2027 from September 2026, new ones may still be created (at the latest valid until 31 August 2027), and the final cut-over is 31 August 2027. This bundle uses a classic token today; it will move to OAuth 2.1 before that date without changing which tools a key already has attached.
  • Not verified: the exact query-parameter names AFAS's GetConnector simple filter takes (filterfieldids, filtervalues, operatortypes above, from third-party integration guides rather than AFAS's own reference); confirm them against your own connector before relying on a filtered read.
  • Every connector's own element shape is entirely your own Profit configuration's; ask whoever built the connector rather than guessing field names.
  • The mark: this bundle's card still uses Artific's own placeholder. AFAS's own house style page says its logo is for AFAS's own use, and a partner needs to check with AFAS's marketing department first, which this deployment has not done (checked 2026-09-24).