Nexra
All connectors
Implemented
Healthcare systems

One Touch Health

UK and Ireland: read One Touch Health home-care areas, carers, service users (clients) and status, position and transport lookups through the Connect API. Read only.

Bring carers, service users and areas from One Touch into finance, payroll and reporting flows without copying personal contact or clinical details.

Build a flow with One Touch HealthProvider API documentation

Source actions

7

Destination actions

0

Data types

7

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

areas
  • List areas
    Source

    Areas (branches or patches) visible to the API user.

    areas.list
carer positions
  • List carer positions
    Source

    Carer position (role) lookup values.

    carer_positions.list
carer statuses
  • List carer statuses
    Source

    Carer status lookup values.

    carer_statuses.list
carer transport types
  • List carer transport types
    Source

    Carer transport type lookup values.

    carer_transport_types.list
carers
  • List carers
    Source

    Care workers with display name, status, area, location and external reference.

    carers.list
client statuses
  • List client statuses
    Source

    Client (service user) status lookup values.

    client_statuses.list
clients
  • List clients (service users)
    Source

    Service users with display name, status and external reference.

    clients.list

Authentication

Dedicated One Touch API user (username and password)

Plans and access

One Touch Health customers with the Connect API enabled. One Touch issues API users on request. Reads are limited to the areas visible to the API user. One Touch keeps one live token per API user, so the Nexra connection must use its own dedicated API user.

Test environment

One Touch does not publish a sandbox; ask One Touch for a test API user on a non-production tenant.

Rate limits

One Touch documents about 8 requests per second. Nexra spaces requests to at most 4 per second per API user and retries HTTP 429 and 503 with backoff.

Pagination

Carers and clients use Laravel page numbers (current_page and last_page) with a server-set page size; lookups and areas return one list.

Provider events

One Touch does not document webhooks on the Connect API. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Read only. Nexra never calls One Touch create, update, delete, leave, schedule, diagnosis, allergy, note, contact, tag, batch or lockdown endpoints.
  • Use a dedicated One Touch API user for this connection. One Touch keeps one live token per user and a new login invalidates the previous token, so sharing the user with another system (or another Nexra connection with different settings) makes them log each other out.
  • Tokens last about 15 to 20 minutes and cannot be refreshed. Nexra logs in on first use, reuses the token for at most 10 minutes, logs in again once after HTTP 401, and serialises logins per API user so it never logs in concurrently. Sessions are shared within one Nexra API instance; separate instances each hold their own session, so run One Touch flows from one instance or expect occasional re-logins.
  • Not available on Connect C2 and not implemented: visits and rotas, timesheets, invoicing (/invoicing returns HTTP 404 on C2), leave reasons and leave records, and carer qualifications. No documented Connect read path exists for them, and Nexra does not probe guessed paths.
  • Locations (/general/locations) are not offered: the path returned HTTP 422 without parameters and its contract is unverified. Tags are deliberately not read.
  • Carer and client records keep only IDs, display name, status, area, location and external references. Address, date of birth, phone, email, NI or PPS number, photo, tags and other personal or clinical fields are dropped and never mapped.
  • There is no updatedSince filter on the Connect API; carers and clients are full reads.
  • One Touch does not publish an official public API reference. Paths and shapes come from the Integrate.io One Touch source documentation and BuildAI's live Connect C2 verification (areas, carers, clients and the four lookups).
  • Only regional hosts of the form api-xx.onetouchhealth.net are accepted, over HTTPS.

Developer reference

  1. Create the OneTouch Health credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose One Touch Health, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
OneTouch Health docsAPI referenceOneTouch Health docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/onetouch-health and the Connections API.