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. The typed tools use the standard Profit_Debtor, Profit_Debtor_Invoices (outstanding debtor items) and Profit_Employees; anything else, including your own custom GetConnectors, goes through afas_profit_get_data. 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 the 5-digit environment number, e.g. 12345 (for environment O12345AA that is 12345), not the full O… code. The adapter calls the production host https://12345.rest.afas.online/ProfitRestServices; for a test or acceptance environment change the base URL to ….resttest.afas.online or ….restaccept.afas.online.

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 'contains', 7 is not equal, 8 is 'is empty', 9 is 'is not empty', 10 is 'starts with', 11 'does not contain', 12 'does not start with', 13 'ends with', 14 'does not end with'. Operators 8 and 9 still need a (possibly empty) value. A comma between entries means AND; a semicolon starts an OR group. Getting the three lists out of step produces a wrong answer rather than an error.

skip and take page, default 0 and 100. Always pass orderbyfieldids when paging (AFAS calls it mandatory: without a sort the row order can change between calls). skip=-1&take=-1 returns everything, which AFAS strongly discourages. The query string is limited to about 2,000 characters; past that AFAS answers 404.

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.

Checked against AFAS's API documentation (docs.afas.help), not yet a live tenant. Paths, query parameters, operator codes and the standard GetConnector names come from AFAS's published docs and OpenAPI files. A 404 on a typed tool usually means that GetConnector has not been added to the app connector; afas_profit_list_connectors shows what is.