AFAS Profit

AFAS exposes nothing until somebody publishes a GetConnector. That is the whole model, and it is why this adapter takes the connector name as a parameter rather than hard-coding entity paths.

1. In AFAS open Algemeen → Beheer → App connector and create an app connector for the integration.
2. Add the GetConnectors the agent should reach (e.g. Profit_Debiteuren, Profit_Facturen, or your own Custom_…). A GetConnector that has not been added to the app connector does not exist as far as the API is concerned.
3. Generate the token. AFAS gives you an XML blob like <token><version>1</version><data>ABC123…</data></token>. Base64-encode that entire string and put the result in AFAS_TOKEN. AFAS's own UI offers a base64 version — use it.
4. Set AFAS_ENVIRONMENT to your environment id, the O12345AB code in your AFAS URL.

The Authorization header is AfasToken <base64>, AFAS's own scheme.

Filtering uses three parallel parameters. filterfieldids, filtervalues and operatortypes are comma-separated lists read positionally: filterfieldids=Nummer,Datum, filtervalues=1001,2026-01-01, operatortypes=1,4. Operator 1 is equals, 2 is greater-or-equal, 3 is less-or-equal, 4 is greater, 5 is less, 6 is 'is null', 7 is 'not null', 8 is not equal, 9 is 'starts with', 10 is 'contains'. Getting the three lists out of step produces a wrong answer rather than an error.

skip and take page. take is capped at 1000 and -1 means everything, which on a large connector is not a good idea.

UpdateConnectors are deliberately not exposed. They write into AFAS with the full force of the business logic behind them, and a malformed payload is not something to discover from an agent.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.