Skip to content

Integrations

Work in the portal, or never leave your case management.

InjuryHub is a full portal for your team, and a connector for the software you already use. After a one-time setup it can run in the background as middleware: your system enrolls the client, we issue the card, and every update flows back to the case.

Connected documents and data flowing between systems

Choose how you work

Two ways to run InjuryHub.

In the portal

Your team signs in and does everything in InjuryHub: enroll clients, track fills, request records and reductions, refer for telehealth. No IT project needed.

  • Ready the day your account is set up
  • Roles and permissions for every team member
  • Nothing to install

As middleware

Your case-management system talks to InjuryHub directly. Enrollment, card status, fills and requests sync automatically, and your team keeps working where they already are.

  • Enroll from your own intake screens
  • Updates pushed back to the case
  • Use the portal only when you want to

What connects

Built to plug into your stack.

REST API

Enroll clients, run a duplicate check, read card status, re-issue a card, and pull claimants, prescription history and service requests. Documented with an OpenAPI specification.

OAuth 2.0

Server-to-server sign-in with short-lived signed tokens and scopes, so each connection gets exactly the access it needs.

Webhooks

Get notified when a client is enrolled, a card is sent or viewed, or a case stage changes. Every event is signed and carries IDs and status only, never medical details.

MCP server

Let your firm's AI assistants and agents look up clients, card status and fills through the Model Context Protocol, with the same scopes and permissions as the API.

Your CRM and intake

Two-way sync with the system where your cases live, so a client created there gets a pharmacy card automatically.

In practice

What middleware looks like day to day.

  1. Step 1

    Intake in your system

    Your team signs up a new client in your case-management software, as they do today.

  2. Step 2

    Enrollment via the API

    Your system sends the enrollment to InjuryHub, after a duplicate check.

  3. Step 3

    Card on the client's phone

    The pharmacy card is created and texted to your client within moments.

  4. Step 4

    Updates back to the case

    Webhooks tell your system the card was sent and viewed, and when the stage changes.

  5. Step 5

    Fills and requests in your system

    Prescription history and request status are available to pull into the case file at any time.

For developers

A clean, predictable API.

Every endpoint is scoped to your firm and returns consistent JSON. Here is an enrollment, for example.

POST /api/v1/partner/enrollments
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "first_name": "Jordan",
  "last_name": "Example",
  "date_of_birth": "1990-01-01",
  "mobile_phone": "+15555550100",
  "date_of_injury": "2026-01-15"
}

Full OpenAPI specification and test credentials are available to integration partners.

Built for HIPAA

Secure by design, not by policy.

Your data only

Each firm sees only its own records, enforced by the database itself.

Scoped access

Tokens carry only the permissions a connection needs and expire quickly.

Signed events

Webhooks are signed, so your system can verify every message came from us.

Minimum necessary

Events carry IDs and status, never medical details.

Compatibility

Works with the software you already use.

If your case-management, intake or CRM system can call a REST API or receive a webhook, it can work with InjuryHub. We help your team or your vendor with the setup, and we provide a test environment so you can try every call before going live.

See it on your own cases.

A 15-minute walkthrough, tailored to how your firm works.