Wafeq

At a Glance

Difficulty

⚡MODERATEAPI Key Authentication — Consumer Enables the API and Creates the Key in Their Own Workspace

Authentication

API KeyAPI key auth via an Authorization: Api-Key header — not OAuth. One key per Wafeq workspace, scoped to that workspace alone.

Webhooks

Virtual webhooks — created/updated events across 11 resource families (invoices, bills, credit notes, customers, suppliers, payments & more).

Partnership Required

No

Apideck Credentials

Not available(Key-based auth: each consumer generates their own API key, so there is no shared Apideck credential.)

Costs

No developer-side fee for API access, at any volume. Your consumer's own Wafeq subscription is the only cost, and it varies by country.

Sandbox Availability

Not available(No separate sandbox for API-key integrations; the same credential shape serves testing and production.)

Account Type Required

A Wafeq workspace on at least the Starter plan, with the Public API switched on for that workspace.

Consumer Access Level

A user who can reach Settings → Developer in the workspace — that is where the API is switched on and the key is created.

Rate Limits

Wafeq does not publish rate limits. A 429 Too many requests response signals throttling; retry with back-off, reusing the same idempotency key.

Responsibility matrix

Environments

Single environment

Testing and production share one credential shape, because an API-key integration has no dedicated Wafeq test host. To test: use a Wafeq free trial workspace, which has full API access before any payment; use your own workspace; or request Apideck temporary shared test credentials at https://help.apideck.com/en/articles/7774658.

Caution

Whichever you pick, the workspace holds real books. Be careful writing to a workspace anybody depends on, and prefer a trial workspace over a live one while you are still iterating.