@spaceinvoices/js-sdk 9.0.0 → 9.0.2

package/dist/generated/expenses/expenses.d.cts

@@ -335,11 +335,13 @@ export type backfillExpenseRecognitionResponse = (backfillExpenseRecognitionResp
 export declare const getBackfillExpenseRecognitionUrl: () => string;
 export declare const backfillExpenseRecognition: (expenseRecognitionBackfill: ExpenseRecognitionBackfill, options?: RequestInit) => Promise<backfillExpenseRecognitionResponse>;
 /**
- * Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
+ * Automatic expense recognition supports PDFs up to 8 pages. Split a larger PDF into smaller documents before trying again.
+
+Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
 
 Returns **202 Accepted** with the job, expense, and file identifiers. Recognition is asynchronous in live mode; poll `GET /expenses/recognitions/{id}` for status. Terminal success is `ready_for_review` or `needs_attention`; terminal failure is `failed`, with safe `error_code` and `error_message` fields.
 
-Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review.
+Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review. Critical identity, required-field, confidence, document-type, and questionable financial warnings also require review and prevent unsafe automatic application.
 
 Payment suggestions from OCR are advisory only and never mark the expense paid or create payments. Failed provider attempts record zero customer usage. Automatic provider attempts and a permitted customer retry share the same job; billable customer usage is recorded once only after a successful terminal result.
 
@@ -358,6 +360,10 @@ export type createExpenseRecognitionResponse401 = {
     data: Error;
     status: 401;
 };
+export type createExpenseRecognitionResponse402 = {
+    data: Error;
+    status: 402;
+};
 export type createExpenseRecognitionResponse403 = {
     data: Error;
     status: 403;
@@ -366,6 +372,10 @@ export type createExpenseRecognitionResponse404 = {
     data: Error;
     status: 404;
 };
+export type createExpenseRecognitionResponse409 = {
+    data: Error;
+    status: 409;
+};
 export type createExpenseRecognitionResponse422 = {
     data: ValidationError;
     status: 422;
@@ -374,10 +384,14 @@ export type createExpenseRecognitionResponse500 = {
     data: Error;
     status: 500;
 };
+export type createExpenseRecognitionResponse503 = {
+    data: Error;
+    status: 503;
+};
 export type createExpenseRecognitionResponseSuccess = (createExpenseRecognitionResponse202) & {
     headers: Headers;
 };
-export type createExpenseRecognitionResponseError = (createExpenseRecognitionResponse400 | createExpenseRecognitionResponse401 | createExpenseRecognitionResponse403 | createExpenseRecognitionResponse404 | createExpenseRecognitionResponse422 | createExpenseRecognitionResponse500) & {
+export type createExpenseRecognitionResponseError = (createExpenseRecognitionResponse400 | createExpenseRecognitionResponse401 | createExpenseRecognitionResponse402 | createExpenseRecognitionResponse403 | createExpenseRecognitionResponse404 | createExpenseRecognitionResponse409 | createExpenseRecognitionResponse422 | createExpenseRecognitionResponse500 | createExpenseRecognitionResponse503) & {
     headers: Headers;
 };
 export type createExpenseRecognitionResponse = (createExpenseRecognitionResponseSuccess | createExpenseRecognitionResponseError);
@@ -432,6 +446,10 @@ export type retryExpenseRecognitionResponse401 = {
     data: Error;
     status: 401;
 };
+export type retryExpenseRecognitionResponse402 = {
+    data: Error;
+    status: 402;
+};
 export type retryExpenseRecognitionResponse403 = {
     data: Error;
     status: 403;
@@ -440,6 +458,10 @@ export type retryExpenseRecognitionResponse404 = {
     data: Error;
     status: 404;
 };
+export type retryExpenseRecognitionResponse409 = {
+    data: Error;
+    status: 409;
+};
 export type retryExpenseRecognitionResponse422 = {
     data: ValidationError;
     status: 422;
@@ -448,10 +470,14 @@ export type retryExpenseRecognitionResponse500 = {
     data: Error;
     status: 500;
 };
+export type retryExpenseRecognitionResponse503 = {
+    data: Error;
+    status: 503;
+};
 export type retryExpenseRecognitionResponseSuccess = (retryExpenseRecognitionResponse202) & {
     headers: Headers;
 };
-export type retryExpenseRecognitionResponseError = (retryExpenseRecognitionResponse400 | retryExpenseRecognitionResponse401 | retryExpenseRecognitionResponse403 | retryExpenseRecognitionResponse404 | retryExpenseRecognitionResponse422 | retryExpenseRecognitionResponse500) & {
+export type retryExpenseRecognitionResponseError = (retryExpenseRecognitionResponse400 | retryExpenseRecognitionResponse401 | retryExpenseRecognitionResponse402 | retryExpenseRecognitionResponse403 | retryExpenseRecognitionResponse404 | retryExpenseRecognitionResponse409 | retryExpenseRecognitionResponse422 | retryExpenseRecognitionResponse500 | retryExpenseRecognitionResponse503) & {
     headers: Headers;
 };
 export type retryExpenseRecognitionResponse = (retryExpenseRecognitionResponseSuccess | retryExpenseRecognitionResponseError);

package/dist/generated/expenses/expenses.d.ts

@@ -335,11 +335,13 @@ export type backfillExpenseRecognitionResponse = (backfillExpenseRecognitionResp
 export declare const getBackfillExpenseRecognitionUrl: () => string;
 export declare const backfillExpenseRecognition: (expenseRecognitionBackfill: ExpenseRecognitionBackfill, options?: RequestInit) => Promise<backfillExpenseRecognitionResponse>;
 /**
- * Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
+ * Automatic expense recognition supports PDFs up to 8 pages. Split a larger PDF into smaller documents before trying again.
+
+Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
 
 Returns **202 Accepted** with the job, expense, and file identifiers. Recognition is asynchronous in live mode; poll `GET /expenses/recognitions/{id}` for status. Terminal success is `ready_for_review` or `needs_attention`; terminal failure is `failed`, with safe `error_code` and `error_message` fields.
 
-Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review.
+Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review. Critical identity, required-field, confidence, document-type, and questionable financial warnings also require review and prevent unsafe automatic application.
 
 Payment suggestions from OCR are advisory only and never mark the expense paid or create payments. Failed provider attempts record zero customer usage. Automatic provider attempts and a permitted customer retry share the same job; billable customer usage is recorded once only after a successful terminal result.
 
@@ -358,6 +360,10 @@ export type createExpenseRecognitionResponse401 = {
     data: Error;
     status: 401;
 };
+export type createExpenseRecognitionResponse402 = {
+    data: Error;
+    status: 402;
+};
 export type createExpenseRecognitionResponse403 = {
     data: Error;
     status: 403;
@@ -366,6 +372,10 @@ export type createExpenseRecognitionResponse404 = {
     data: Error;
     status: 404;
 };
+export type createExpenseRecognitionResponse409 = {
+    data: Error;
+    status: 409;
+};
 export type createExpenseRecognitionResponse422 = {
     data: ValidationError;
     status: 422;
@@ -374,10 +384,14 @@ export type createExpenseRecognitionResponse500 = {
     data: Error;
     status: 500;
 };
+export type createExpenseRecognitionResponse503 = {
+    data: Error;
+    status: 503;
+};
 export type createExpenseRecognitionResponseSuccess = (createExpenseRecognitionResponse202) & {
     headers: Headers;
 };
-export type createExpenseRecognitionResponseError = (createExpenseRecognitionResponse400 | createExpenseRecognitionResponse401 | createExpenseRecognitionResponse403 | createExpenseRecognitionResponse404 | createExpenseRecognitionResponse422 | createExpenseRecognitionResponse500) & {
+export type createExpenseRecognitionResponseError = (createExpenseRecognitionResponse400 | createExpenseRecognitionResponse401 | createExpenseRecognitionResponse402 | createExpenseRecognitionResponse403 | createExpenseRecognitionResponse404 | createExpenseRecognitionResponse409 | createExpenseRecognitionResponse422 | createExpenseRecognitionResponse500 | createExpenseRecognitionResponse503) & {
     headers: Headers;
 };
 export type createExpenseRecognitionResponse = (createExpenseRecognitionResponseSuccess | createExpenseRecognitionResponseError);
@@ -432,6 +446,10 @@ export type retryExpenseRecognitionResponse401 = {
     data: Error;
     status: 401;
 };
+export type retryExpenseRecognitionResponse402 = {
+    data: Error;
+    status: 402;
+};
 export type retryExpenseRecognitionResponse403 = {
     data: Error;
     status: 403;
@@ -440,6 +458,10 @@ export type retryExpenseRecognitionResponse404 = {
     data: Error;
     status: 404;
 };
+export type retryExpenseRecognitionResponse409 = {
+    data: Error;
+    status: 409;
+};
 export type retryExpenseRecognitionResponse422 = {
     data: ValidationError;
     status: 422;
@@ -448,10 +470,14 @@ export type retryExpenseRecognitionResponse500 = {
     data: Error;
     status: 500;
 };
+export type retryExpenseRecognitionResponse503 = {
+    data: Error;
+    status: 503;
+};
 export type retryExpenseRecognitionResponseSuccess = (retryExpenseRecognitionResponse202) & {
     headers: Headers;
 };
-export type retryExpenseRecognitionResponseError = (retryExpenseRecognitionResponse400 | retryExpenseRecognitionResponse401 | retryExpenseRecognitionResponse403 | retryExpenseRecognitionResponse404 | retryExpenseRecognitionResponse422 | retryExpenseRecognitionResponse500) & {
+export type retryExpenseRecognitionResponseError = (retryExpenseRecognitionResponse400 | retryExpenseRecognitionResponse401 | retryExpenseRecognitionResponse402 | retryExpenseRecognitionResponse403 | retryExpenseRecognitionResponse404 | retryExpenseRecognitionResponse409 | retryExpenseRecognitionResponse422 | retryExpenseRecognitionResponse500 | retryExpenseRecognitionResponse503) & {
     headers: Headers;
 };
 export type retryExpenseRecognitionResponse = (retryExpenseRecognitionResponseSuccess | retryExpenseRecognitionResponseError);

package/dist/generated-zod/expenses/expenses.d.cts

@@ -951,11 +951,13 @@ export declare const BackfillExpenseRecognitionResponse: zod.ZodObject<{
     next_cursor: zod.ZodNullable<zod.ZodString>;
 }, zod.z.core.$strip>;
 /**
- * Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
+ * Automatic expense recognition supports PDFs up to 8 pages. Split a larger PDF into smaller documents before trying again.
+
+Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
 
 Returns **202 Accepted** with the job, expense, and file identifiers. Recognition is asynchronous in live mode; poll `GET /expenses/recognitions/{id}` for status. Terminal success is `ready_for_review` or `needs_attention`; terminal failure is `failed`, with safe `error_code` and `error_message` fields.
 
-Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review.
+Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review. Critical identity, required-field, confidence, document-type, and questionable financial warnings also require review and prevent unsafe automatic application.
 
 Payment suggestions from OCR are advisory only and never mark the expense paid or create payments. Failed provider attempts record zero customer usage. Automatic provider attempts and a permitted customer retry share the same job; billable customer usage is recorded once only after a successful terminal result.
 

package/dist/generated-zod/expenses/expenses.d.ts

@@ -951,11 +951,13 @@ export declare const BackfillExpenseRecognitionResponse: zod.ZodObject<{
     next_cursor: zod.ZodNullable<zod.ZodString>;
 }, zod.z.core.$strip>;
 /**
- * Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
+ * Automatic expense recognition supports PDFs up to 8 pages. Split a larger PDF into smaller documents before trying again.
+
+Accepts one supplier invoice (PDF, JPEG, PNG, or WebP), creates an invoice-only draft expense with `creation_source=ocr`, and enqueues an async recognition job. For sandbox entities, no provider is called and no usage is charged: the submitted file is not stored and is replaced by a clearly marked deterministic demo invoice; the response exposes `simulation_mode=sandbox_demo`.
 
 Returns **202 Accepted** with the job, expense, and file identifiers. Recognition is asynchronous in live mode; poll `GET /expenses/recognitions/{id}` for status. Terminal success is `ready_for_review` or `needs_attention`; terminal failure is `failed`, with safe `error_code` and `error_message` fields.
 
-Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review.
+Parsed document and line amounts are checked against the standard expense calculation before applying extraction. A disagreement keeps the draft unchanged and stores the extraction with `needs_attention` for review. Critical identity, required-field, confidence, document-type, and questionable financial warnings also require review and prevent unsafe automatic application.
 
 Payment suggestions from OCR are advisory only and never mark the expense paid or create payments. Failed provider attempts record zero customer usage. Automatic provider attempts and a permitted customer retry share the same job; billable customer usage is recorded once only after a successful terminal result.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spaceinvoices/js-sdk",
-  "version": "9.0.0",
+  "version": "9.0.2",
   "description": "Official JavaScript/TypeScript SDK for the Space Invoices API",
   "author": "Space Invoices <support@spaceinvoices.com>",
   "license": "MIT",