ChartHeroAI

DocsDeveloper Docs

Guide

Fetch actors

List user and API-key actors referenced by external API responses.

When to use this

Use GET /external/v1/actors to resolve actor IDs returned by external API responses. Actor records help partner systems identify ChartHero users and API keys without embedding repeated actor details in every record.

The actor list supports limit, offset, sort_order, and repeated actor_id filters. Pagination is offset-based and is not snapshot-consistent across repeated calls. See Pagination for parameter limits and unsupported-filter behavior.

Required scopes

Route Required scopes
GET /external/v1/actors encounters:read, patients:read, documents:read

The API key must be organization-scoped. Actor responses are limited to user and API-key actors in the caller organization.

Request

List available actors:

cURL
curl "https://api.charthero.ai/external/v1/actors?limit=50&offset=0&sort_order=asc" \
  -H "Authorization: Bearer <api_key>"

Fetch specific actors by repeating actor_id:

cURL
curl "https://api.charthero.ai/external/v1/actors?actor_id=11111111-1111-4111-8111-111111111111&actor_id=22222222-2222-4222-8222-222222222222" \
  -H "Authorization: Bearer <api_key>"

Response

User actor:

JSON
{
  "items": [
    {
      "actor_id": "11111111-1111-4111-8111-111111111111",
      "actor_type": "user",
      "external_ids": [
        {"source": "partner_ehr", "type": "provider_id", "value": "provider-778"}
      ],
      "display_name": "Dr. Synthetic Clinician",
      "first_name": "Synthetic",
      "last_name": "Clinician",
      "active": true
    }
  ],
  "limit": 50,
  "offset": 0,
  "total": 1
}

API-key actor:

JSON
{
  "items": [
    {
      "actor_id": "22222222-2222-4222-8222-222222222222",
      "actor_type": "api_key",
      "display_name": "Northfield sync key",
      "active": true,
      "status": "active"
    }
  ],
  "limit": 50,
  "offset": 0,
  "total": 1
}

Actor IDs are opaque ChartHero IDs. User actors use the same public name, discriminator, active-state, and provider external-identifier vocabulary as organization-adapter callback actors where those concepts overlap. Adapter launch-context callbacks may include adapter-only user context such as email, specialty, governance role, and functional roles. A user actor's external_ids lists the active identifiers ChartHero has on file for that user in your organization, such as a provider ID, using source, type, and value; it is empty when none is on file. API-key actors include status so consumers can preserve reference integrity when API keys create or update records.

Common errors

HTTP status Reason code What it means
400 unsupported_filter The request includes a query parameter that this route does not support.
401 missing_bearer, api_keys_disabled, test_prefix_not_allowed, malformed_token, invalid_key, disabled_key, revoked_key, or expired_key API-key authentication failed. Branch on the exact reason_code.
403 org_scope_only_required Organization-scoped API keys are required.
403 missing_scope The API key does not include every required scope.
403 route_not_allowed The route is not enabled.
422 invalid_query, invalid_limit, invalid_offset, or invalid_sort One or more query parameters failed validation.
ChartHeroAI

Developer documentation for ChartHero APIs, adapters, and integrations.

HIPAA-aligned safeguards

BAA available

ChartHero AI LLC