@abyss-project/tools 2.11.0 → 2.12.0

package/src/api/extraction.application.api.ts

@@ -1,79 +0,0 @@
-// ──────────────────────────────────────────────
-// AbyssExtract APPLICATION extract API — POST
-// /extract/application/:applicationId/extract. Mirrors
-// apps/api/src/api/controllers/extraction-extract-application.controller.ts
-// EXACTLY — the application counterpart of extraction.api.ts's `extractSync`,
-// for inter-service callers (e.g. AbyssBanking) authenticating with a project
-// API key instead of a personal/org session.
-//
-// Reuses extraction.api.ts's `buildExtractMultipart` (the same global
-// `FormData` + `Blob` multipart body as the personal client) and every
-// request/response TYPE verbatim (`IExtractBody`, `IExtractSyncResponse`) —
-// never redefined here. There is NO scope query param: unlike the
-// personal/org route's `?organization_id=`, an application caller's scope is
-// entirely its `:applicationId` URL segment, resolved server-side by
-// ApplicationMiddleware (round-trips to abyss-main).
-//
-// `authHeaderApplication` is kept LOCAL and unexported, same convention as the
-// personal client's own `authHeader` — it sends `API_KEY_APPLICATION_HEADER`
-// (`abyss-api-key-application`) instead of the personal `abyss-api-key`.
-//
-// The endpoint is SYNCHRONOUS (the machine caller gets the extraction inline —
-// no queue), so the return is always the `IExtractSyncResponse` shape.
-// ──────────────────────────────────────────────
-
-import { AbyssToolsCore, API_KEY_APPLICATION_HEADER } from '..';
-import type { IExtractBody } from '../types';
-import type { IExtractSyncResponse } from '../types';
-import { buildExtractMultipart, ExtractCallOptions } from './extraction.api';
-
-function authHeaderApplication(applicationApiKey?: string): Record<string, string> {
-  return applicationApiKey ? { [API_KEY_APPLICATION_HEADER]: applicationApiKey } : {};
-}
-
-/**
- * `POST /extract/application/:applicationId/extract` — run one synchronous
- * extraction OWNED by `applicationId` and BILLED to its resolved owning
- * organization. The route accepts only a multipart PDF upload: send
- * `body.pdf`, with `body.mode` `auto` or `hint`; `body.plan` (inline, single
- * pass, no OCR, no template pass) and `body.improvementConsent` travel as
- * multipart fields. The route refuses `storage_file_id`, `plan_preset_id`,
- * `template_id` and `template` with a 4xx. A body without `pdf` is sent as
- * JSON and never runs an extraction: the memory watchdog may answer 503 before
- * the route reads the body; past it, the route answers a 4xx — the
- * `storage_file_id` refusal when the body carries one, otherwise "Provide file
- * (multipart pdf)". `options` forwards a Stripe-style
- * `Idempotency-Key` header (24h replay window) when set.
- */
-export const runExtractionApplication = async (
-  applicationId: string,
-  body: IExtractBody,
-  options: ExtractCallOptions = {},
-  applicationApiKey?: string,
-): Promise<IExtractSyncResponse> => {
-  const extraHeaders: Record<string, string> = {};
-  if (options.idempotencyKey) {
-    extraHeaders['Idempotency-Key'] = options.idempotencyKey;
-  }
-  const url = `extract/application/${applicationId}/extract`;
-
-  if (body.pdf) {
-    const form = buildExtractMultipart(body);
-    return (
-      await AbyssToolsCore.axios.post<IExtractSyncResponse>(url, form, {
-        headers: { ...authHeaderApplication(applicationApiKey), ...extraHeaders },
-        maxBodyLength: Infinity,
-        maxContentLength: Infinity,
-      })
-    ).data;
-  }
-
-  // Strip `pdf` from the JSON body (only used for the multipart upload above).
-  const jsonBody: Omit<IExtractBody, 'pdf'> = { ...body };
-  delete (jsonBody as { pdf?: unknown }).pdf;
-  return (
-    await AbyssToolsCore.axios.post<IExtractSyncResponse>(url, jsonBody, {
-      headers: { ...authHeaderApplication(applicationApiKey), ...extraHeaders },
-    })
-  ).data;
-};