Afas
One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.
npx -y skills add apideck-libraries/api-skills --skill afasAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
AFAS Software integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in AFAS Software. Routes through Apideck with serviceId "afas".
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.5 KB, as published. Nobody here has run it
AFAS Software (via Apideck)
Access AFAS Software through Apideck's HRIS unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant AFAS Software plumbing.
Beta connector. AFAS Software is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
afas - Unified API: HRIS
- Auth type: apiKey
- Status: beta
- Apideck setup guide: Connection guide
- Gotchas: page
- AFAS Software docs: https://www.afas.nl
- Homepage: https://www.afas.nl/
When to use this skill
Activate this skill when the user explicitly wants to work with AFAS Software — for example, "sync employees in AFAS Software" or "list time-off requests in AFAS Software". This skill teaches the agent:
- Which Apideck unified API covers AFAS Software (HRIS)
- The correct
serviceIdto pass on every call (afas) - AFAS Software-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List employees in AFAS Software
const { data } = await apideck.hris.employees.list({
serviceId: "afas",
});
Portable across 58 HRIS connectors
The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from AFAS Software to another HRIS connector is a one-string change — no rewrite, no new SDK.
// Today — AFAS Software
await apideck.hris.employees.list({ serviceId: "afas" });
// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "workday" });
This is the compounding advantage of using Apideck over integrating AFAS Software directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Authentication
- Type: API Key
- Managed by: Apideck Vault — the user pastes their AFAS Software API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
- Rotation: if the user rotates their key, they re-enter it in Vault. No code changes needed.
Setup guide: Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for AFAS Software — see https://developers.apideck.com/connectors/afas/docs/consumer+connection. Use that as the authoritative source when walking users through connection setup.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Verifying coverage
Not every HRIS operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/afas' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the HRIS unified API, use Apideck's Proxy to call AFAS Software directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on AFAS Software's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: afas" \
-H "x-apideck-downstream-url: <target endpoint on AFAS Software>" \
-H "x-apideck-downstream-method: GET"
See AFAS Software's API docs for available endpoints.
Sibling connectors
Other HRIS connectors that share this unified API surface (same method signatures, just change serviceId):
bamboohr, workday, deel (beta), hibob, personio, adp-ihcm (beta), adp-workforce-now (beta), paychex (beta), and 49 more.
See also
- Apideck connection guide for AFAS Software
- HRIS OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- AFAS Software official docs