generated: '2026-09-06' method: searched source: https://accountsiq.github.io/API-Wiki/guidelines.html docs: - https://accountsiq.github.io/API-Wiki/guidelines.html - https://accountsiq.github.io/API-Wiki/authentication1.html - https://www.accountsiq.com/pricing available: true self_service: false note: >- AccountsIQ publishes a real staging environment and requires development against it before production, but access is granted by AccountsIQ rather than provisioned by the developer. There is no signup form, no instant test key, and no public sandbox host — the staging endpoint URL and staging credentials are supplied on request via integration@accountsiq.com. No test values are recorded below because AccountsIQ publishes none: there are no published test card numbers, no magic identifiers and no fixture tokens for this API, and inventing any would be fabrication. modes: - name: staging description: >- The development environment. Requires a staging partner key; production keys are a different set and are explicitly refused by the staging servers and vice versa. endpoint: not published credentials: staging partner key + user key, issued by AccountsIQ - name: production description: >- Live regional deployments (eu1, eu2, uk1, us1). Requires a live production partner key, requested from AccountsIQ once the integration is built. endpoint: https://{regioncode}.accountsiq.com/system/dashboard/integration/ sandbox_company: description: >- The unit of sandboxing is a company, not a key. A developer needs either a blank demo company or a copy of a live entity. options: - name: blank demo company consent_required: false - name: copy of a live entity consent_required: true consent_note: Explicit permission from the customer is required to copy their live entity. source: https://accountsiq.github.io/API-Wiki/guidelines.html credentials_model: tokens: - name: partner token issued_by: AccountsIQ - name: user token issued_by: >- Generated by a user inside the live company; developers use it to impersonate that user. note: >- The impersonation model means a sandbox user token carries that user's permissions, so permission-scoped failures ("Read Permission Required") reproduce in staging. test_data_reset: supported: true self_service: false mechanism: >- Email integration@accountsiq.com specifying what should be cleared and for which company. There is no reset API operation and no time-simulation or test-clock facility. source: https://accountsiq.github.io/API-Wiki/guidelines.html time_simulation: supported: false note: No test clocks or date simulation are published. promotion_path: steps: - Email integration@accountsiq.com requesting a live production partner key. - Switch the generated web reference from the staging URL to the live production web service URL. - Collect each end user's own user integration key. - Let the user select their region so the endpoint host is set correctly. source: https://accountsiq.github.io/API-Wiki/guidelines.html commercial_availability: note: >- The pricing page lists a "sandbox database" as a Growth-tier feature, so sandbox access is also a commercial entitlement and not only a developer-onboarding step. source: https://www.accountsiq.com/pricing sample_surfaces: - name: ASP.NET service help page url: https://uk1.accountsiq.com/system/dashboard/integration/integration_1_1.asmx http_status: 200 description: >- The provider's guidelines page points here as "a library of XML samples of API requests and responses". The live help page enumerates all 217 Integration 1.1 operations, each with a generated SOAP 1.1/1.2 request and response envelope sample at ?op=. Anonymously readable — no credentials needed to read the samples. - name: Postman collections url: https://accountsiq.github.io/API-Wiki/postman-collection.html description: >- First-party Postman collections published per region and per version (eight files) in the provider's own GitHub repository. - name: sample C# project availability: on request from integration@accountsiq.com published: false