Developers

AiDGENT API documentation

NOA document processing, schedule helpers, eligibility, referrals, daterange audits, and screening endpoints—structured sections with copy-ready examples.

Base URL

https://aidgent-api.accelingsoftware.com

Authentication

Secured routes expect one of the following headers (use whichever your gateway or client is configured to send):

HeaderDescription
Ocp-Apim-Subscription-KeyAzure API Management subscription key (typical in production).
X-API-Key-For-BackendBackend API key when calling the service directly or when your edge forwards this header.

NOA processing

API 1.0.1. The NOA API accepts one or more PDFs or images and returns structured authorizations. Some workloads run asynchronously; use the job status and callback options when you need background completion. For schedule lines, use the schedule helper endpoints in this API.

POST /noa/parse

Upload one or more PDFs to parse into structured authorization data. Supports synchronous and asynchronous processing. Schedule lines are built with the /schedules endpoints, not from this parse call.

Query parameters

NameTypeRequiredDefaultDescription
callback_urlstringNonullURL for async completion. If set, processing runs asynchronously.

Processing modes

Synchronous (default). When no callback_url is provided, the API processes documents and returns results in the response.

Asynchronous. When callback_url is provided, the API returns a job ID immediately and processes in the background. Results are POSTed to your callback when complete.

Response formats

{
  "results": [
    {
      "filename": "document.pdf",
      "status": "success",
      "document_type": "united_v1",
      "authorization_number": "AUTH123456",
      "provider": { },
      "patient": { },
      "services": [ ]
    }
  ],
  "status": "completed"
}

Asynchronous acceptance:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "pending",
  "message": "Documents queued for processing",
  "callback_url": "https://your-callback-endpoint.com/webhook"
}

GET /noa/parse/status/{job_id}

Poll the status of an asynchronous parsing job.

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "processing",
  "progress": 45,
  "created_at": "2025-01-15T10:00:00Z",
  "updated_at": "2025-01-15T10:02:30Z",
  "result": null,
  "error": null,
  "metadata": {
    "file_count": 2
  }
}

Job statuses

StatusMeaning
pendingJob created, waiting to start
processingJob is currently running
completedJob finished successfully
failedJob failed with an error

Callback payload

When asynchronous processing completes, your callback URL receives a POST with one of the following payloads.

Success:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "completed",
  "timestamp": "2025-01-15T10:30:00Z",
  "result": {
    "results": [
      {
        "filename": "document.pdf",
        "status": "success",
        "document_type": "united_v1",
        "authorization_number": "AUTH123456",
        "provider": { },
        "patient": { },
        "services": [ ]
      }
    ]
  },
  "error": null
}

Error:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "failed",
  "timestamp": "2025-01-15T10:30:00Z",
  "result": null,
  "error": "Document classification failed - insufficient confidence"
}

Code examples

Synchronous parse

curl --location 'https://aidgent-api.accelingsoftware.com/noa/parse' \
--header 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY' \
--form 'files=@"/c/path/to/first.pdf"' \
--form 'files=@"/c/path/to/second.pdf"'

Asynchronous parse (submit + optional status poll in Node)

curl --location 'https://aidgent-api.accelingsoftware.com/noa/parse?callback_url=https://your-app.com/webhook' \
--header 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY' \
--form 'files=@"/c/path/to/first.pdf"' \
--form 'files=@"/c/path/to/second.pdf"'

Check job status

curl --location 'https://aidgent-api.accelingsoftware.com/noa/parse/status/JOB_ID' \
--header 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY'

Schedule helper endpoints

Use these JSON schedule helpers on the same base URL and API key as NOA. Each route is a POST under /schedules:

  • /schedules/fixed_monthly — build month-block lines from auth constraints
  • /schedules/total — total units / hours for a range
  • /schedules/multi_month — multi-month grid
  • /schedules/cost — cost projection from hours and rate

Example parsed document

Successful parses return structured fields for services, schedules, and demographics. The shape varies by payer template.

Show example JSON (truncated placeholders)
{
  "document_type": "medicaid_v2",
  "authorization_number": null,
  "notice_date": "06/30/2025",
  "provider": null,
  "patient": {
    "name": "John Doe",
    "address": "789 Pine St\nAnytown, USA 54321",
    "phone": null,
    "rid": "112233445566",
    "ssn": null,
    "dob": "02/02/1970"
  },
  "care_manager": {
    "name": "Smith, Jane",
    "email": "jane.smith@exampleprovider.org"
  },
  "services": [
    {
      "service_name": "Attendant Care",
      "funding_source": "Health and Wellness",
      "line_items": [
        {
          "billing_code": "S5125",
          "modifiers": ["U7", "UA"],
          "start_date": "07/01/2025",
          "stop_date": "07/31/2025",
          "service_description": null,
          "unit_size": "[UNIT_SIZE]",
          "unit_rate": "[UNIT_RATE]",
          "num_units": "32",
          "current_cost": "[CURRENT_COST]"
        }
      ]
    }
  ]
}