AFAS Software
Service ID: afas
AFAS Software provides comprehensive business software solutions including ERP, HR, and payroll management for small to medium-sized businesses.
At a Glance
- Difficulty
- π§ADVANCEDNon-OAuth Token Auth + Multi-Step Per-Consumer App Connector Setup
- Authentication
- API KeyAn AFAS App Connector token sent in the Authorization header, prefixed with AfasToken. Not OAuth.
- Webhooks
- Virtual webhooksβ β polling-based created/updated events for 14 HRIS and accounting resource families (employees, customers, invoices, bills, and 10 more).
- Partnership Required
- No(Certifying your integration through the optional Partner Program adds 1-2 AFAS test environments on the Accept platform.)
- Partnership Application
- AFAS Partner Programβ
- Apideck Credentials
- Not available(Every consumer connects with their own AFAS environment name and App Connector token.)
- Costs
- No separate API or connector fee β REST access is included in an AFAS Profit or AFAS Online license. No free trial for non-customers.
- Sandbox Availability
- Not available(Every AFAS environment is licensed; customers clone a Test copy. AFAS Connect (connect.afas.nl) freely builds and tests connector calls.)
- Account Type Required
- A licensed AFAS Profit or AFAS Online environment with the modules you need (HRM for HRIS; Financieel, Facturering and Inkoop for accounting).
- Consumer Access Level
- AFAS administrator, to create the App Connector and issue the token.
- Rate Limits
- No published per-minute or per-day limit β AFAS applies a fair-use policy.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enable Connector & Configure Vault | β | β | Docs provided |
| Create App Connector in AFAS | Share required connector list | β (AFAS Administrator) | Specifies required connectors |
| Publish required GetConnectors & UpdateConnectors | Share specifications | β | Connector specs provided |
| Generate Token & Provide Environment Name | β | β | β |
| Authorize Connection (Vault) | Implement Vault | β Enters environment name + token | Handles connection |
| Build via Unified API | β | β | Maintains connector |
| Connection Sync | β | β | β Polls via virtual webhooks |
| Monitor Connections | β Via Dashboard | β Can revoke the token in AFAS | Logs & alerts |
Environments
- Test / Acceptance
- For development and testing against non-production data. The environment name is the company number plus its type, e.g. 12345.resttest (Test) or 12345.restaccept (Acceptance), each with its own separately issued App Connector token.
- Production
- For live consumer data. The environment name is the company number plus rest, e.g. 12345.rest, with its own App Connector token. A Test or Acceptance token cannot be used against a production environment.
π¨Important to Know About AFAS Software
- One AFAS environment and token serves two unified APIs: HRIS (live) and Accounting (beta). Employees and departments are HRIS-only β those operations are disabled on the Accounting API β so which resources you get depends on the API you build against.
- A connection can authorize and still return no data: each consumer's AFAS administrator must first publish the named GetConnectors (and UpdateConnectors for writes) to the App Connector. Credit notes, payments and aged debtors/creditors need one the tenant authors itself.
- AFAS is retiring classic token authentication: tokens receive automatic end-dates on 15 February 2027 and stop working on 31 August 2027, when OAuth 2.1 replaces them. An administrator can also time-limit or revoke a token at any point, which silently breaks the connection.
β οΈ
2 gotchas across 2 resources
Connector-specific behaviors and limitations to be aware of
π¦
2 supported resources
View field mappings, supported operations, and schema details