AxisCare API

Does AxisCare have a public API?

Yes. AxisCare documents an API and any agency can create a token under Admin, API token, on the condition that the agency supplies its own development team; AxisCare builds no integrations itself. Integuru generates a production-ready HTTP API from the agency's own login for the screens that team would otherwise script, with 17 verified actions across client profiles, ADLs, the Client 101 form, the wallet, leads and caregiver records, each write previewable with dry_run.

If the official API covers your workflow, use it. Integuru fits the vendor that supports several home care platforms, wants the same login-based model and response handling across all of them, and needs the form-driven screens that agencies actually live in. Calls are direct HTTP requests, authenticated, using your own credentials, with login and any second factor handled for you.

What you can do with the AxisCare API

A caregiver recruiting platform places a new hire with an agency, and by the next morning the agency wants that caregiver in AxisCare with a profile, a driver's license on file, a CPR certification with its expiry, and the matching attributes set so the scheduler can see them. On the client side, a lead that signed becomes a client with a Client 101 form and a card in the wallet. The actions cover both sides, and every write can be previewed first.

Find people

• find_person resolves a full_name (exact, case-insensitive) or an external_id to a Client or Lead, optionally constrained by entity_type.

Read and update the client

• read_profile and update_profile work on a numeric client_id; live saves use the array form of changes with a baseline_value_hash per field so a stale value is never overwritten.
• read_adls and update_adls read and merge ADL changes keyed by adl_key; keys you omit are preserved.
• read_client_101, create_client_101 and update_client_101 handle the Client 101 form: read returns field identifiers, create opens a new instance against the locked template, and update writes a fields map with a second approve_live_write gate and an optional form_version conflict check.
• promote_lead converts a lead_id to a client, revalidating against expected_name and aborting with a conflict status on a mismatch.

Read and update the wallet

• read_wallet returns a client's payment methods, filterable by payment_method_id. update_wallet edits the billing fields of one method; raw card fields and the Default and AutoPay flags are rejected. add_wallet_payment previews a new cc, debit or ach method and never accepts card secrets; on the verified account a live add is disabled (HTTP 501).

Onboard and maintain caregivers

• upsert_caregiver creates or updates a caregiver from first_name and last_name with contact details, address, date_of_birth, driver's license fields, hourly_pay_rate with an effective date, preferred_weekly_hours, up to two emergency_contacts, availability_blocks and matching_attributes. Phone numbers are normalised, and ssn is normalised and never logged.
• upsert_caregiver_certification creates or updates a credential by certification_type_id or certification_type_name, with status, expiration_date (required when expired) and a note. read_caregiver_compliance reads the Compliance area, list_caregiver_attributes returns the agency's attribute list, and upload_caregiver_document files a file_base64 under filename with an optional expire_date.

Who uses this

Caregiver recruiting and credentialing platforms push a placed hire through upsert_caregiver, upsert_caregiver_certification and upload_caregiver_document, then confirm with read_caregiver_compliance before the first shift. Intake and CRM tools promote a signed lead, fill the Client 101 form from the assessment, and read the wallet so billing starts on day one. Vendors that also support the ClearCare and Wellsky integrations, or care managers on the CareTree page, get AxisCare in the same pipeline with the same auth model. The healthcare industry page covers home care alongside the rest of the stack.

Setup notes

Integuru authenticates against your agency's numbered subdomain of axiscare.com with an AxisCare user. Client and caregiver identifiers are numeric (digits only as strings, or integers where noted). Writes default to dry_run: true except upsert_caregiver and upload_caregiver_document; review the returned payload, then repeat with dry_run: false (and approve_live_write: true on update_client_101). Three actions, add_wallet_payment, update_wallet and promote_lead, are scoped to single records on the reference account and return 403 for other ids; treat them as verified request shapes and ask for them to be widened. Dates are YYYY-MM-DD and are converted to AxisCare's mm/dd/yyyy internally; correlation_marker and idempotency_key are echoed back for your own audit trail and never sent to AxisCare.

Get started

Install the CLI and connect your AxisCare login:

npm install -g integuru

Or sign in at app.integuru.com, add AxisCare, and run find_person from the dashboard. Scheduling, shifts, visit verification and invoicing, and general-purpose versions of the locked wallet and lead actions, are built on request through the Managed Service.