For the complete documentation index, see llms.txt. This page is also available as Markdown.

PowerOffice Go

Configure your PowerOffice Go application and connect one company to a Consent.

Connect one PowerOffice Go company to each API.1 Consent. Your organisation supplies its PowerOffice application key in System Settings and, for Demo, the matching subscription key. Your Customer then signs in to PowerOffice and selects the company to connect.

This guide covers connection setup and Consent creation. An Accepted Consent lets you list and read customers and retrieve the connected company's identity, address, general contact details and company contacts through API.1, or call permitted PowerOffice v2 resources through Proxy.1. Company bank accounts, invoice reads and payment writes are not yet supported through the normalised API.1 endpoints. See the API reference for available operations and field mappings.

PowerOffice Go is available for Demo connections. Live Production connections are not available yet. You can start the production approval process below while testing your integration in Demo.

Before you start

You need:

  • A PowerOffice application and its Application key for the provider environment you intend to use.

  • For Demo, the Subscription key issued for that application.

  • The application privilege Customer or Customer_Full for customer reads. Proxy.1 calls need the privileges required by each PowerOffice resource.

  • A PowerOffice user with administrator access or the Settings → Organization permission for the company. See PowerOffice’s integration permissions.

  • PowerOffice connection setup enabled and configured in your Zwapgrid deployment. Confirm availability with Zwapgrid before inviting customers.

Zwapgrid manages the shared Production subscription key. For Demo, your organisation supplies its own matching application and subscription keys. Your Customer does not need to find or enter a company client key; PowerOffice returns it during onboarding. See PowerOffice's onboarding workflow for provider prerequisites.

Demo setup

  1. Register your organisation through PowerOffice's Demo registration form. The registration provides a Demo application, subscription and test company, with access to the PowerOffice Demo portal.

  2. Retain the Application key and its matching Subscription key. PowerOffice's authentication guide explains where to find the subscription key in the developer portal.

  3. Have PowerOffice whitelist the exact API.1 onboarding callback for your Demo application before connecting through the hosted Onboarding Flow. Obtain the callback URL from Zwapgrid; a Demo registration alone does not complete this step.

  4. Follow Configure System Settings below, selecting Demo (Sandbox) and entering both keys. Your PowerOffice user then selects one Demo company during onboarding.

Use separate settings for different applications. A Demo subscription key must belong to the selected application; another organisation's key or a Production key will not work.

Production setup

To connect live PowerOffice Go companies, your organisation needs its own PowerOffice-approved production application. Zwapgrid submits one access request for that application; the accounting companies that later connect do not each need an application request. Public listing by PowerOffice is a separate step from production approval.

  1. Contact Zwapgrid to start the request. We will ask for your registered company name and organisation number; the name, email and phone number of someone authorised to sign PowerOffice's terms; a primary contact if different; your preferred integration name; and a short description of how your product will use PowerOffice data. If you tested with your own PowerOffice Demo application, we will also need its application key as a testing reference.

  2. Zwapgrid prepares and submits the form. We provide the technical details, including the production callback URL and the API access needed for workflows tested in Demo. PowerOffice reviews the request and sends its developer terms to your authorised representative for digital signature.

  3. Allow time for approval. PowerOffice's published target is to have applications live within 1–2 weeks. We will let you know when your production application key is available.

  4. Set up your connection after access is confirmed. Once Zwapgrid confirms that Production connections are available for your application, create a separate Production System Setting with your production Application key, following Configure System Settings below. Zwapgrid manages the production subscription key, so you do not enter one. Once the setting is published, each of your Customers can authorise their own live PowerOffice company through the Onboarding Flow.

A successful Demo connection does not establish production approval or configuration.

Configure System Settings

  1. In the Client Portal, enable PowerOffice under Systems.

  2. Select Configure and create a setting with a descriptive name.

  3. Select the provider environment and enter the Application key. Demo (Sandbox) uses PowerOffice's test environment and also requires your Subscription key. Production uses live companies and does not ask for a subscription key. Keep separate settings for each environment.

  4. Save and publish the setting. Make it the client default where supported, or select it explicitly when creating the Consent.

For an explicit API selection, supply the published setting ID in systemsSettings:

The setting's provider environment is independent of the Consent's Development/Production classification. A Development Consent alone does not select PowerOffice Demo.

If Production is unavailable, it cannot be selected for a new configuration. Contact Zwapgrid to arrange production access. You can still configure Demo with your own matching keys. A previously saved Production setting remains visible if production access becomes unavailable, but new connections cannot complete until access is restored.

The application key and provider environment cannot change after publication. To connect through another application or environment, create a new System Setting and a new Consent. See System Settings for the setting lifecycle.

Demo subscription keys are masked after saving. Leave the field unchanged to retain the saved key. If you rotate the subscription key in PowerOffice, update it in the same setting; the replacement must still belong to that application.

Connect one company

  1. Create a Consent using the published PowerOffice setting and open its Onboarding Flow.

  2. Choose PowerOffice, read the connection instructions, and select I have permission to connect integrations for the PowerOffice company I will select.

  3. Click Connect to PowerOffice. Sign in when the PowerOffice window opens, select exactly one company, and approve access.

  4. Wait for the connection to finish and return to your application.

You do not enter an organisation number in API.1, and there is no second company picker after PowerOffice. To connect another company, create another Consent and select that company in a separate flow.

If more than one company was selected

API.1 cannot complete that Consent and shows an error with Try again. Use it to reopen PowerOffice and select only one company. While the onboarding session remains valid, you can retry the same pending Consent.

PowerOffice may already have replaced the credentials for every selected company. Discarding the returned keys does not restore the earlier connections. Retrying with company A does not recover company B: if B's previous connection stops working, create a new Consent for B, complete its onboarding separately, and update your application to use the new Consent ID.

Replacing an existing connection

Authorising the same PowerOffice application for the same company again replaces its company credentials. Earlier Consents using those credentials can stop working, sometimes after a delay. API.1 does not automatically update or repair those Consents.

Create and complete a new Consent, then update your application's Consent reference. Avoid reconnecting a company whose existing connection is still needed without planning that replacement.

For a connection problem, contact support@zwapgrid.com with the Consent ID, UTC timestamp, and correlation or request ID. Do not include subscription keys, company keys, or callback tokens.

Last updated

Was this helpful?