Integration guide

Connecting Reconexa to Cliniko

Reconexa is connected to your clinic through a guided onboarding session. Here is what to prepare, what we will configure together, and how you stay in control.

Before the session

  1. Create a dedicated Cliniko user

    Create a user such as Reconexa Integration and assign the Receptionist security role. This gives Reconexa access to the patient details, invoices, and payment actions the integration needs without granting administrator access.

    Using a dedicated user keeps Reconexa activity clearly identifiable in your Cliniko records.

  2. Generate an API key for that user

    Sign in as the dedicated user and open My info. Under API keys, enable Allow yourself to create and use API keys, then update the user. Select Manage API keys, add a key named Reconexa, and copy it when it appears. Cliniko only shows a new key once.

    See Cliniko's API key guide for the current Cliniko screens.

  3. Confirm your Cliniko region

    Confirm that your Cliniko account uses the au1 region. Reconexa will verify this with you during setup.

  4. Have your mailbox details ready

    Have the details ready for the email account that receives your remittance advices (Gmail or Microsoft 365).

During the session

The Reconexa team connects your mailbox, Cliniko, and Xero; checks that remittance emails are being captured; and tests proposed matches against your Cliniko invoices. We then walk your team through the review and approval workflow using recent remittances from your clinic.

Sensitive credentials stored by Reconexa are encrypted at rest.

Ongoing use and disconnecting

Your team reviews proposed matches in Reconexa. A payment is not recorded in Cliniko, and a pushed invoice is not created in Xero, until a user approves the relevant action.

To disconnect Reconexa, contact hello@reconexa.ai. To stop Cliniko access immediately from your side, archive the Reconexa API key and make the dedicated Cliniko user inactive. Archiving the key stops API access; making the user inactive stops login access.