feat(js-api-client): allow passing extra headers in the fetch function

CrystallizeAPI · Jan 6, 2025 · e5ba781 · e5ba781
1 parent 50b4711
commit e5ba781
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 2 deletions.
diff --git a/components/js-api-client/package.json b/components/js-api-client/package.json
@@ -1,7 +1,7 @@
 {
     "name": "@crystallize/js-api-client",
     "license": "MIT",
-    "version": "4.0.0",
+    "version": "4.1.0",
     "type": "module",
     "author": "Crystallize <hello@crystallize.com> (https://crystallize.com)",
     "contributors": [

diff --git a/components/js-api-client/src/core/client.ts b/components/js-api-client/src/core/client.ts
@@ -41,6 +41,7 @@ type ProfilingOptions = {
 export type CreateClientOptions = {
     useHttp2?: boolean;
     profiling?: ProfilingOptions;
+    extraHeaders?: RequestInit['headers'];
     shopApiToken?: {
         doNotFetch?: boolean;
         scopes?: string[];
@@ -183,7 +184,19 @@ function createApiCaller(
     options?: CreateClientOptions,
 ): ApiCaller<any> {
     return function callApi<T>(query: string, variables?: VariablesType): Promise<T> {
-        return post<T>(grab, uri, configuration, query, variables, undefined, options);
+        return post<T>(
+            grab,
+            uri,
+            configuration,
+            query,
+            variables,
+            options?.extraHeaders
+                ? {
+                      headers: options.extraHeaders,
+                  }
+                : undefined,
+            options,
+        );
     };
 }