Credentialing

Create credentialing education entry

Adds an education history record to an organization-scoped Credentialing session.

POSTNeeds publication reviewLocal writeCredentialingoperationId: createCredentialingEducationhttps://dev-api.quickintell.com/api/v1/credentialing/sessions/{sessionId}/education
Needs publication reviewLocal writeProvider and payer setup

Route status

Needs publication review

The endpoint contract is visible, but QuickRCM has not approved it yet for normal production API use.

Publication status

Needs publication review

Requires product, security/compliance, tenancy, side-effect, or module-owner approval before production public API use. Also requires E2 side-effect policy before production recipes, SDK inclusion, or try-out access.

Authentication

Bearer API key declared

OpenAPI declares bearer API-key security for this operation.

Tenant context

API-key organization

API-key organization context is authoritative; request organizationId is not a public tenant selector.

Side-effect summary

Local write

May mutate QuickRCM records. It does not prove live payer, EHR, clearinghouse, payment, or communication execution.

Source artifact

docs/openapi/openapi.json

OpenAPI 3.1.0; API 1.0.0.

When to use this endpoint

Use this page as an internal baseline for the provider and payer setup contract generated for POST /api/v1/credentialing/sessions/{sessionId}/education. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Shows the generated OpenAPI shape for POST /api/v1/credentialing/sessions/{sessionId}/education, but keeps the route out of ordinary production API positioning until review is complete.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Mutating behavior still needs side-effect and retry evidence.

Not public from this page

Do not publish this endpoint as an ordinary developer API until its unresolved decisions are closed.

Headers and tenancy

Current headers and tenant authority. Target headers stay labeled as future until OpenAPI and release evidence declare them.

HeaderRequiredCurrent statusNotes
AuthorizationYesCurrentBearer <QUICKRCM_API_KEY>. OpenAPI security: bearerAuth.
Idempotency-KeyNoTarget/futureDo not claim universal header support until E3 and OpenAPI metadata exist.
X-Request-IdNoTarget/futureUse for support correlation only after approved; not declared as a standard OpenAPI header today.

Required scopes

Unclassified until E6 route metadata exists; do not infer scopes from route names.

Wrong-org behavior

Tenant-safe 404, empty list, or 403 is endpoint-specific and remains an evidence gap until E1 is closed.

Actor and audit

No public actor, audit, or correlation contract is published from OpenAPI alone.

Idempotency and retries

Retry behavior is documented conservatively because universal idempotency headers are not declared.

TopicStatusGuidance
Current idempotencyNo idempotency mechanism is declared.Do not retry blindly. Check resource, status, batch, or job state before repeating the request.
Universal headerNot declaredDo not document universal Idempotency-Key support until OpenAPI and E3 evidence declare it.
Conflict behaviorUnresolvedSame-key changed-payload, in-flight retry, fingerprint scope, and TTL behavior remain endpoint-specific evidence gaps.

Async jobs and polling

Queued work is accepted work, not proof of completed workflow execution.

TopicStatusGuidance
Immediate responseNo 202 response declaredOpenAPI does not declare HTTP 202 for this operation.
Polling and terminal statesNot indicated by OpenAPINo generic polling contract is published from this page.
Later side effectsNot provenDo not infer background execution beyond the documented response.

Files and artifacts

File-like routes need content-class, ownership, scanning, retention, and URL policy evidence before public recipes.

TopicStatusGuidance
Content classNo file/artifact class inferredOpenAPI text does not indicate file or artifact handling for this endpoint.
Ownership and storage keysNot applicable unless a file field is presentTenant ownership must be proven before retrieval or upload docs. Never expose storage keys as public identifiers.
URLs, scanning, and retentionUnresolved unless endpoint-specific evidence existsShort-lived URLs, MIME limits, checksums, scanner status, retention, expiration, and legal hold behavior are not implied by OpenAPI examples.

Publication warnings

  • This endpoint needs explicit product, security/compliance, tenancy, or side-effect approval before publication.
  • Universal Idempotency-Key header support is not declared; retry only after checking endpoint-specific state.

Evidence

EvidenceStatusCaveat
OpenAPI artifactdocs/openapi/openapi.json; OpenAPI 3.1.0; API 1.0.0.Generated baseline contract only.
Route registryNeeds publication review from documentation classification overlay.E6 route registry evidence is still required before external publication.
Example validationGenerated examples are internal baseline aids.No external publication claim; examples must pass no-PHI/no-secret/no-raw-payload/no-storage-key checks.
Last reviewedImplementation run 20260619T-docs-impl; source boardroom packet 20260619T064820Z.Refresh this evidence for release workspaces.
Release evidenceE9 required.No SDK readiness, production readiness, or expanded external docs claim from this endpoint page.

Credentialing public API.

Credentialing APIs expose organization-scoped credentialing session visibility and local workflow controls for provider credentialing packets. The public surface covers session creation and updates, provider profile fields, non-secret CAQH metadata, education, work history, licenses, professional references, liability insurance, signature file references, attestation acceptance, status updates, and safe simulated document/application workflows. The bearer API key selects the organization. Public request bodies should not be documented as tenant selectors, and every session, document, File, payer configuration, assignee, or subresource lookup is scoped to that API-key organization. List and detail reads accept `credentialing:read` or `credentialing:write`; write operations require `credentialing:write`. Several endpoints deliberately avoid external or high-risk side effects. Document upload and document processing validate ownership and return `SIMULATED_ONLY`; they do not create S3-backed file records or invoke OCR/extraction. Application submit validates readiness and returns `VALIDATED_ONLY` or `SIMULATED_ONLY`; it does not submit to payer portals or move the local session status. CAQH public responses expose metadata and `hasPassword`, not password material. Session summaries expose `documentCount` from the local document relation count; session detail returns active document metadata filtered by `deletedAt: null` and ordered newest-first.

What this endpoint does

Use case
Use this endpoint when assembling a provider credentialing packet that needs medical school, residency, fellowship, or other education history entries.
Before calling
Authenticate with `credentialing:write`. Confirm the session exists in the API-key organization.

Request and response behavior

Request guidance
Send the education fields that apply to the provider record. Date strings are parsed by the handler; invalid dates return 400. Do not send transcripts, diplomas, or binary files here.
  • This endpoint stores structured education metadata only.
  • Use separate document workflows for supporting files.
  • The request body has no public organization selector.
Response semantics
A 201 response returns `data.record` for the newly created local education entry with `sessionId`, `sortOrder`, timestamps, and supplied fields. The `data.record` object is a passthrough public subresource record: it always includes normalized `id`, `sessionId`, `sortOrder`, `deletedAt`, `createdAt`, and `updatedAt`, plus the accepted fields for that subresource.
  • `data.record` is local subresource state.
  • `sortOrder` is server-assigned workflow ordering metadata.
  • No external verification is performed.

Errors and retries

400 can indicate invalid dates or field limits. 404 means the session was not found in the authenticated organization. If a retry could duplicate an education row, list or inspect the session before retrying.
  • Do not retry unknown create outcomes without checking for duplicates.
  • 404 can mean wrong-tenant session.

Template boundary before examples

The route class, authentication state, tenancy rule, side-effect mode, idempotency status, async behavior, file policy, warnings, links, and evidence above are part of the endpoint contract. Treat generated examples below as internal baseline aids until release evidence closes.

Path parameters

NameLocationRequiredTypeDescriptionValidation and safety notes
sessionIdpathYesstringQuickRCM Credentialing session identifier in the path. It must belong to the organization selected by the bearer API key; wrong-tenant IDs resolve as authorization/not-found failures.Minimum length: 1. Tenant context is selected by the API key; do not treat this as a public tenant selector.

Query parameters

This endpoint does not define query parameters.

OpenAPI-declared header parameters

Standard platform header guidance appears in the governance panel. This table only lists operation-specific headers declared in OpenAPI.

This endpoint does not define operation-specific header parameters.

Request body

JSON fields from the generated OpenAPI schema with pilot enrichment applied where available. Nested object fields are shown with dotted paths.

NameLocationRequiredTypeDescriptionValidation and safety notes
educationTypebodyNostringEducation category or training type for the credentialing packet. Nullable and capped at 255 characters.Maximum length: 255. Sensitive credential or storage-adjacent value; use placeholders only.
degreebodyNostringDegree or credential label for the education entry. Nullable and capped at 255 characters.Maximum length: 255. Sensitive credential or storage-adjacent value; use placeholders only.
institutionNamebodyNostringInstitution name for the education entry. Nullable and capped at 255 characters.Maximum length: 255.
startDatebodyNostringStart date string for the education period. Null clears the value; invalid date strings return 400.Minimum length: 1.
endDatebodyNostringEnd date string for the education period. Use null for open or unknown dates when appropriate; invalid date strings return 400.Minimum length: 1.

Generated request example

Generated examples are baseline contract aids only. They are not external publication evidence and must not include real PHI, credentials, raw vendor payloads, raw EDI, transcripts, storage keys, or signed URLs.

{
  "educationType": "example-educationtype",
  "degree": "example-degree",
  "institutionName": "Example credentialing_education",
  "startDate": "2026-06-08",
  "endDate": "2026-06-08"
}

Successful responses

Generated response examples show the baseline OpenAPI contract. Tenant identifier echo, PHI redaction, pagination, money, date/time, and enum semantics remain endpoint-specific publication checks.

201
Education entry created.
Generated from the OpenAPI response schema.
{
  "success": true,
  "data": {
    "record": {
      "id": "00000000-0000-4000-8000-000000000001",
      "sessionId": "00000000-0000-4000-8000-000000000001",
      "sortOrder": 1,
      "deletedAt": "2026-06-08T10:15:30Z",
      "createdAt": "2026-06-08T10:15:30Z",
      "updatedAt": "2026-06-08T10:15:30Z"
    }
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001"
  }
}

Error responses

Errors must remain sanitized. Do not include raw payer, EHR, SFTP, SMTP, Stripe, LLM/OCR, browser automation, file, transcript, EDI, worker, or vendor payloads.

400
Invalid request.
Handle this response as normal integration control flow.
{
  "error": "Request validation failed",
  "statusCode": 400
}
401
Authentication required or invalid credentials.
Handle this response as normal integration control flow.
{
  "error": "Authentication required",
  "statusCode": 401
}
403
The requested organization does not match the authenticated caller.
Handle this response as normal integration control flow.
{
  "error": "Forbidden",
  "statusCode": 403
}
404
Credentialing session not found in the authenticated organization.
Handle this response as normal integration control flow.
{
  "error": "Resource not found",
  "statusCode": 404
}
429
API key rate limit exceeded.
Handle this response as normal integration control flow.
{
  "error": "Rate limit exceeded",
  "statusCode": 429
}
500
Internal server error.
Handle this response as normal integration control flow.
{
  "error": "Internal server error",
  "statusCode": 500
}

Adjacent endpoints

Nearby generated endpoints in the same OpenAPI tag. Route class and side-effect labels still apply per endpoint.