@kard-financial/sdk 16.1.1 → 16.1.2

package/dist/cjs/BaseClient.js

@@ -43,8 +43,8 @@ function normalizeClientOptions(options) {
     const headers = (0, headers_js_1.mergeHeaders)({
         "X-Fern-Language": "JavaScript",
         "X-Fern-SDK-Name": "@kard-financial/sdk",
-        "X-Fern-SDK-Version": "16.1.1",
-        "User-Agent": "@kard-financial/sdk/16.1.1",
+        "X-Fern-SDK-Version": "16.1.2",
+        "User-Agent": "@kard-financial/sdk/16.1.2",
         "X-Fern-Runtime": core.RUNTIME.type,
         "X-Fern-Runtime-Version": core.RUNTIME.version,
     }, options === null || options === void 0 ? void 0 : options.headers);

package/dist/cjs/api/resources/transactions/client/Client.d.ts

@@ -238,7 +238,7 @@ export declare class TransactionsClient {
      * to storage. Each URL is valid for 15 minutes. Use the returned URL to upload the file via an HTTP PUT request with the
      * binary file content as the body. If a URL expires before the upload completes, you must request a new one.
      * Files can be uploaded as plain JSONL or as a gzip-compressed file.
-     * Only `coreTransaction` type is supported for bulk file uploads.
+     * Supports both `incomingTransactionsFile` for daily transaction ingestion and `historicalTransactionsFile` for historical transaction ingestion. See the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide for details on the historical flow.
      * <b>Required scopes:</b> `transaction:write`
      *
      * @param {KardApi.OrganizationId} organizationId
@@ -264,6 +264,16 @@ export declare class TransactionsClient {
      *                 }
      *             }]
      *     })
+     *
+     * @example
+     *     await client.transactions.createBulkTransactionsUploadUrl("organization-123", {
+     *         data: [{
+     *                 type: "historicalTransactionsFile",
+     *                 attributes: {
+     *                     filename: "historical_transactions_2024-10-15.jsonl"
+     *                 }
+     *             }]
+     *     })
      */
     createBulkTransactionsUploadUrl(organizationId: KardApi.OrganizationId, request: KardApi.CreateFileUploadRequestBody, requestOptions?: TransactionsClient.RequestOptions): core.HttpResponsePromise<KardApi.CreateFileUploadUrlResponse>;
     private __createBulkTransactionsUploadUrl;

package/dist/cjs/api/resources/transactions/client/Client.js

@@ -421,7 +421,7 @@ class TransactionsClient {
      * to storage. Each URL is valid for 15 minutes. Use the returned URL to upload the file via an HTTP PUT request with the
      * binary file content as the body. If a URL expires before the upload completes, you must request a new one.
      * Files can be uploaded as plain JSONL or as a gzip-compressed file.
-     * Only `coreTransaction` type is supported for bulk file uploads.
+     * Supports both `incomingTransactionsFile` for daily transaction ingestion and `historicalTransactionsFile` for historical transaction ingestion. See the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide for details on the historical flow.
      * <b>Required scopes:</b> `transaction:write`
      *
      * @param {KardApi.OrganizationId} organizationId
@@ -447,6 +447,16 @@ class TransactionsClient {
      *                 }
      *             }]
      *     })
+     *
+     * @example
+     *     await client.transactions.createBulkTransactionsUploadUrl("organization-123", {
+     *         data: [{
+     *                 type: "historicalTransactionsFile",
+     *                 attributes: {
+     *                     filename: "historical_transactions_2024-10-15.jsonl"
+     *                 }
+     *             }]
+     *     })
      */
     createBulkTransactionsUploadUrl(organizationId, request, requestOptions) {
         return core.HttpResponsePromise.fromPromise(this.__createBulkTransactionsUploadUrl(organizationId, request, requestOptions));

package/dist/cjs/api/resources/transactions/types/FileUploadType.d.ts

@@ -1,4 +1,4 @@
-/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for back-filled or retroactive transaction data that covers a past time period. */
+/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for historical transaction ingestion. */
 export declare const FileUploadType: {
     readonly IncomingTransactionsFile: "incomingTransactionsFile";
     readonly HistoricalTransactionsFile: "historicalTransactionsFile";

package/dist/cjs/api/resources/transactions/types/FileUploadType.js

@@ -2,7 +2,7 @@
 // This file was auto-generated by Fern from our API Definition.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.FileUploadType = void 0;
-/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for back-filled or retroactive transaction data that covers a past time period. */
+/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for historical transaction ingestion. */
 exports.FileUploadType = {
     IncomingTransactionsFile: "incomingTransactionsFile",
     HistoricalTransactionsFile: "historicalTransactionsFile",

package/dist/cjs/api/resources/users/resources/uploads/client/Client.d.ts

@@ -11,6 +11,10 @@ export declare class UploadsClient {
     protected readonly _options: NormalizedClientOptionsWithAuth<UploadsClient.Options>;
     constructor(options?: UploadsClient.Options);
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload
      * Part](/api/uploads/create-upload-part) endpoint, historical transactions can be sent in batches for further processing.
      * <b>Required scopes:</b> `transaction:write`
@@ -35,6 +39,10 @@ export declare class UploadsClient {
     create(organizationId: KardApi.OrganizationId, userId: string, request: KardApi.users.CreateUploadRequestObject, requestOptions?: UploadsClient.RequestOptions): core.HttpResponsePromise<KardApi.users.CreateUploadResponseObject>;
     private __create;
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint using the upload ID provided in the [Create Upload](/api/uploads/create-upload) endpoint to add parts to your upload. Currently, this endpoint supports adding historical transactions.
      * <b>Required scopes:</b> `transaction:write`
      * <b>Note:</b> `Maximum of 500 transactions can be uploaded per request`.
@@ -93,6 +101,10 @@ export declare class UploadsClient {
     createPart(organizationId: KardApi.OrganizationId, userId: string, uploadId: string, request: KardApi.users.CreateUploadPartRequestObject, requestOptions?: UploadsClient.RequestOptions): core.HttpResponsePromise<KardApi.users.CreateUploadPartResponseObject>;
     private __createPart;
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to update your upload session. Currently, you can signal completing a historical transactions upload.
      * <b>Required scopes:</b> `transaction:write`
      *

package/dist/cjs/api/resources/users/resources/uploads/client/Client.js

@@ -56,6 +56,10 @@ class UploadsClient {
         this._options = (0, BaseClient_js_1.normalizeClientOptionsWithAuth)(options);
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload
      * Part](/api/uploads/create-upload-part) endpoint, historical transactions can be sent in batches for further processing.
      * <b>Required scopes:</b> `transaction:write`
@@ -125,6 +129,10 @@ class UploadsClient {
         });
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint using the upload ID provided in the [Create Upload](/api/uploads/create-upload) endpoint to add parts to your upload. Currently, this endpoint supports adding historical transactions.
      * <b>Required scopes:</b> `transaction:write`
      * <b>Note:</b> `Maximum of 500 transactions can be uploaded per request`.
@@ -230,6 +238,10 @@ class UploadsClient {
         });
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to update your upload session. Currently, you can signal completing a historical transactions upload.
      * <b>Required scopes:</b> `transaction:write`
      *

package/dist/cjs/version.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "16.1.1";
+export declare const SDK_VERSION = "16.1.2";

package/dist/cjs/version.js

@@ -1,4 +1,4 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SDK_VERSION = void 0;
-exports.SDK_VERSION = "16.1.1";
+exports.SDK_VERSION = "16.1.2";

package/dist/esm/BaseClient.mjs

@@ -6,8 +6,8 @@ export function normalizeClientOptions(options) {
     const headers = mergeHeaders({
         "X-Fern-Language": "JavaScript",
         "X-Fern-SDK-Name": "@kard-financial/sdk",
-        "X-Fern-SDK-Version": "16.1.1",
-        "User-Agent": "@kard-financial/sdk/16.1.1",
+        "X-Fern-SDK-Version": "16.1.2",
+        "User-Agent": "@kard-financial/sdk/16.1.2",
         "X-Fern-Runtime": core.RUNTIME.type,
         "X-Fern-Runtime-Version": core.RUNTIME.version,
     }, options === null || options === void 0 ? void 0 : options.headers);

package/dist/esm/api/resources/transactions/client/Client.d.mts

@@ -238,7 +238,7 @@ export declare class TransactionsClient {
      * to storage. Each URL is valid for 15 minutes. Use the returned URL to upload the file via an HTTP PUT request with the
      * binary file content as the body. If a URL expires before the upload completes, you must request a new one.
      * Files can be uploaded as plain JSONL or as a gzip-compressed file.
-     * Only `coreTransaction` type is supported for bulk file uploads.
+     * Supports both `incomingTransactionsFile` for daily transaction ingestion and `historicalTransactionsFile` for historical transaction ingestion. See the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide for details on the historical flow.
      * <b>Required scopes:</b> `transaction:write`
      *
      * @param {KardApi.OrganizationId} organizationId
@@ -264,6 +264,16 @@ export declare class TransactionsClient {
      *                 }
      *             }]
      *     })
+     *
+     * @example
+     *     await client.transactions.createBulkTransactionsUploadUrl("organization-123", {
+     *         data: [{
+     *                 type: "historicalTransactionsFile",
+     *                 attributes: {
+     *                     filename: "historical_transactions_2024-10-15.jsonl"
+     *                 }
+     *             }]
+     *     })
      */
     createBulkTransactionsUploadUrl(organizationId: KardApi.OrganizationId, request: KardApi.CreateFileUploadRequestBody, requestOptions?: TransactionsClient.RequestOptions): core.HttpResponsePromise<KardApi.CreateFileUploadUrlResponse>;
     private __createBulkTransactionsUploadUrl;

package/dist/esm/api/resources/transactions/client/Client.mjs

@@ -385,7 +385,7 @@ export class TransactionsClient {
      * to storage. Each URL is valid for 15 minutes. Use the returned URL to upload the file via an HTTP PUT request with the
      * binary file content as the body. If a URL expires before the upload completes, you must request a new one.
      * Files can be uploaded as plain JSONL or as a gzip-compressed file.
-     * Only `coreTransaction` type is supported for bulk file uploads.
+     * Supports both `incomingTransactionsFile` for daily transaction ingestion and `historicalTransactionsFile` for historical transaction ingestion. See the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide for details on the historical flow.
      * <b>Required scopes:</b> `transaction:write`
      *
      * @param {KardApi.OrganizationId} organizationId
@@ -411,6 +411,16 @@ export class TransactionsClient {
      *                 }
      *             }]
      *     })
+     *
+     * @example
+     *     await client.transactions.createBulkTransactionsUploadUrl("organization-123", {
+     *         data: [{
+     *                 type: "historicalTransactionsFile",
+     *                 attributes: {
+     *                     filename: "historical_transactions_2024-10-15.jsonl"
+     *                 }
+     *             }]
+     *     })
      */
     createBulkTransactionsUploadUrl(organizationId, request, requestOptions) {
         return core.HttpResponsePromise.fromPromise(this.__createBulkTransactionsUploadUrl(organizationId, request, requestOptions));

package/dist/esm/api/resources/transactions/types/FileUploadType.d.mts

@@ -1,4 +1,4 @@
-/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for back-filled or retroactive transaction data that covers a past time period. */
+/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for historical transaction ingestion. */
 export declare const FileUploadType: {
     readonly IncomingTransactionsFile: "incomingTransactionsFile";
     readonly HistoricalTransactionsFile: "historicalTransactionsFile";

package/dist/esm/api/resources/transactions/types/FileUploadType.mjs

@@ -1,5 +1,5 @@
 // This file was auto-generated by Fern from our API Definition.
-/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for back-filled or retroactive transaction data that covers a past time period. */
+/** Specifies the category of transaction file being uploaded. Use `incomingTransactionsFile` for new, real-time transactions that need to be processed and matched as they arrive. Use `historicalTransactionsFile` for historical transaction ingestion. */
 export const FileUploadType = {
     IncomingTransactionsFile: "incomingTransactionsFile",
     HistoricalTransactionsFile: "historicalTransactionsFile",

package/dist/esm/api/resources/users/resources/uploads/client/Client.d.mts

@@ -11,6 +11,10 @@ export declare class UploadsClient {
     protected readonly _options: NormalizedClientOptionsWithAuth<UploadsClient.Options>;
     constructor(options?: UploadsClient.Options);
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload
      * Part](/api/uploads/create-upload-part) endpoint, historical transactions can be sent in batches for further processing.
      * <b>Required scopes:</b> `transaction:write`
@@ -35,6 +39,10 @@ export declare class UploadsClient {
     create(organizationId: KardApi.OrganizationId, userId: string, request: KardApi.users.CreateUploadRequestObject, requestOptions?: UploadsClient.RequestOptions): core.HttpResponsePromise<KardApi.users.CreateUploadResponseObject>;
     private __create;
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint using the upload ID provided in the [Create Upload](/api/uploads/create-upload) endpoint to add parts to your upload. Currently, this endpoint supports adding historical transactions.
      * <b>Required scopes:</b> `transaction:write`
      * <b>Note:</b> `Maximum of 500 transactions can be uploaded per request`.
@@ -93,6 +101,10 @@ export declare class UploadsClient {
     createPart(organizationId: KardApi.OrganizationId, userId: string, uploadId: string, request: KardApi.users.CreateUploadPartRequestObject, requestOptions?: UploadsClient.RequestOptions): core.HttpResponsePromise<KardApi.users.CreateUploadPartResponseObject>;
     private __createPart;
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to update your upload session. Currently, you can signal completing a historical transactions upload.
      * <b>Required scopes:</b> `transaction:write`
      *

package/dist/esm/api/resources/users/resources/uploads/client/Client.mjs

@@ -20,6 +20,10 @@ export class UploadsClient {
         this._options = normalizeClientOptionsWithAuth(options);
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload
      * Part](/api/uploads/create-upload-part) endpoint, historical transactions can be sent in batches for further processing.
      * <b>Required scopes:</b> `transaction:write`
@@ -89,6 +93,10 @@ export class UploadsClient {
         });
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint using the upload ID provided in the [Create Upload](/api/uploads/create-upload) endpoint to add parts to your upload. Currently, this endpoint supports adding historical transactions.
      * <b>Required scopes:</b> `transaction:write`
      * <b>Note:</b> `Maximum of 500 transactions can be uploaded per request`.
@@ -194,6 +202,10 @@ export class UploadsClient {
         });
     }
     /**
+     * @deprecated
+     *
+     * <b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+     *
      * Call this endpoint to update your upload session. Currently, you can signal completing a historical transactions upload.
      * <b>Required scopes:</b> `transaction:write`
      *

package/dist/esm/version.d.mts

@@ -1 +1 @@
-export declare const SDK_VERSION = "16.1.1";
+export declare const SDK_VERSION = "16.1.2";

package/dist/esm/version.mjs

@@ -1 +1 @@
-export const SDK_VERSION = "16.1.1";
+export const SDK_VERSION = "16.1.2";

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@kard-financial/sdk",
-    "version": "16.1.1",
+    "version": "16.1.2",
     "private": false,
     "repository": {
         "type": "git",

package/reference.md

@@ -1556,7 +1556,7 @@ Generates up to 10 presigned PUT URLs for uploading JSONL transaction files (up
 to storage. Each URL is valid for 15 minutes. Use the returned URL to upload the file via an HTTP PUT request with the
 binary file content as the body. If a URL expires before the upload completes, you must request a new one.
 Files can be uploaded as plain JSONL or as a gzip-compressed file.
-Only `coreTransaction` type is supported for bulk file uploads.
+Supports both `incomingTransactionsFile` for daily transaction ingestion and `historicalTransactionsFile` for historical transaction ingestion. See the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide for details on the historical flow.
 <b>Required scopes:</b> `transaction:write`
 </dd>
 </dl>
@@ -2679,7 +2679,9 @@ await client.users.rewards.locations("organization-123", "user-123", {
 <dl>
 <dd>
 
-Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload 
+<b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+
+Call this endpoint to create an upload session and retrieve an upload ID. Using the upload ID in the [Add Upload
 Part](/api/uploads/create-upload-part) endpoint, historical transactions can be sent in batches for further processing.
 <b>Required scopes:</b> `transaction:write`
 </dd>
@@ -2765,6 +2767,8 @@ await client.users.uploads.create("organization-123", "user-123", {
 <dl>
 <dd>
 
+<b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+
 Call this endpoint using the upload ID provided in the [Create Upload](/api/uploads/create-upload) endpoint to add parts to your upload. Currently, this endpoint supports adding historical transactions.
 <b>Required scopes:</b> `transaction:write`
 <b>Note:</b> `Maximum of 500 transactions can be uploaded per request`.
@@ -2891,6 +2895,8 @@ await client.users.uploads.createPart("organization-123", "user-123", "upload-12
 <dl>
 <dd>
 
+<b>Deprecated.</b> This endpoint is deprecated in favor of the [Create Bulk Transactions Upload URL](/2024-10-01/api/transactions/create-bulk-transactions-upload-url) endpoint. New integrations should use the bulk flow outlined in the [Historical Transaction Uploads](/2024-10-01/api/integration-guides/historical-transaction-uploads) integration guide.
+
 Call this endpoint to update your upload session. Currently, you can signal completing a historical transactions upload.
 <b>Required scopes:</b> `transaction:write`
 </dd>