fix(types): make comment, created_at, fraud_type, updated_at nullable in fraud transactions

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 214
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-2d2600072500797474f0d7798c1a8b668bfbc4e0c6a8f076ca7b4cc7ad82058b.yml
-openapi_spec_hash: 7605eb6be77a3d150078916f0eb0e9ac
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-6683cf82e93cfd95e17b0386f070333486fe8e7b857b47c62e09682362d5991d.yml
+openapi_spec_hash: ce2c1f6201bb2036d05602238503eb6b
 config_hash: 5bb913c05ebeb301ec925b16e75bb251

packages/mcp-server/src/local-docs-search.ts

@@ -4127,12 +4127,12 @@ const EMBEDDED_METHODS: MethodEntry[] = [
     httpMethod: 'post',
     summary: 'Respond to Authorization Challenge',
     description:
-      "Card program's response to Authorization Challenge.\nPrograms that have Authorization Challenges configured as Out of Band receive a [card_authorization.challenge](https://docs.lithic.com/reference/post_card-authorization-challenge) webhook when an authorization attempt triggers a challenge.\nThe card program should respond using this endpoint after the cardholder completes the challenge.",
+      "Card program's response to Authorization Challenge.\nPrograms that have Authorization Challenges configured as Out of Band receive a [card_authorization.challenge](https://docs.lithic.com/reference/cardauthorizationchallengewebhook) webhook when an authorization attempt triggers a challenge.\nThe card program should respond using this endpoint after the cardholder completes the challenge.",
     stainlessPath: '(resource) card_authorizations > (method) challenge_response',
     qualified: 'client.cardAuthorizations.challengeResponse',
     params: ['event_token: string;', "response: 'APPROVE' | 'DECLINE';"],
     markdown:
-      "## challenge_response\n\n`client.cardAuthorizations.challengeResponse(event_token: string, response: 'APPROVE' | 'DECLINE'): void`\n\n**post** `/v1/card_authorizations/{event_token}/challenge_response`\n\nCard program's response to Authorization Challenge.\nPrograms that have Authorization Challenges configured as Out of Band receive a [card_authorization.challenge](https://docs.lithic.com/reference/post_card-authorization-challenge) webhook when an authorization attempt triggers a challenge.\nThe card program should respond using this endpoint after the cardholder completes the challenge.\n\n### Parameters\n\n- `event_token: string`\n\n- `response: 'APPROVE' | 'DECLINE'`\n  Whether the cardholder has approved or declined the issued challenge\n\n### Example\n\n```typescript\nimport Lithic from 'lithic';\n\nconst client = new Lithic();\n\nawait client.cardAuthorizations.challengeResponse('182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e', { response: 'APPROVE' })\n```",
+      "## challenge_response\n\n`client.cardAuthorizations.challengeResponse(event_token: string, response: 'APPROVE' | 'DECLINE'): void`\n\n**post** `/v1/card_authorizations/{event_token}/challenge_response`\n\nCard program's response to Authorization Challenge.\nPrograms that have Authorization Challenges configured as Out of Band receive a [card_authorization.challenge](https://docs.lithic.com/reference/cardauthorizationchallengewebhook) webhook when an authorization attempt triggers a challenge.\nThe card program should respond using this endpoint after the cardholder completes the challenge.\n\n### Parameters\n\n- `event_token: string`\n\n- `response: 'APPROVE' | 'DECLINE'`\n  Whether the cardholder has approved or declined the issued challenge\n\n### Example\n\n```typescript\nimport Lithic from 'lithic';\n\nconst client = new Lithic();\n\nawait client.cardAuthorizations.challengeResponse('182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e', { response: 'APPROVE' })\n```",
     perLanguage: {
       typescript: {
         method: 'client.cardAuthorizations.challengeResponse',
@@ -9168,12 +9168,12 @@ const EMBEDDED_METHODS: MethodEntry[] = [
     httpMethod: 'post',
     summary: 'Respond to a Challenge Request',
     description:
-      "Card program's response to a 3DS Challenge Request.\nChallenge Request is emitted as a webhook [three_ds_authentication.challenge](https://docs.lithic.com/reference/post_three-ds-authentication-challenge) and your Card Program needs to be configured with Out of Band (OOB) Challenges in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for more information).",
+      "Card program's response to a 3DS Challenge Request.\nChallenge Request is emitted as a webhook [three_ds_authentication.challenge](https://docs.lithic.com/reference/threedsauthenticationchallengewebhook) and your Card Program needs to be configured with Out of Band (OOB) Challenges in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for more information).",
     stainlessPath: '(resource) three_ds.decisioning > (method) challenge_response',
     qualified: 'client.threeDS.decisioning.challengeResponse',
     params: ['token: string;', "challenge_response: 'APPROVE' | 'DECLINE_BY_CUSTOMER';"],
     markdown:
-      "## challenge_response\n\n`client.threeDS.decisioning.challengeResponse(token: string, challenge_response: 'APPROVE' | 'DECLINE_BY_CUSTOMER'): void`\n\n**post** `/v1/three_ds_decisioning/challenge_response`\n\nCard program's response to a 3DS Challenge Request.\nChallenge Request is emitted as a webhook [three_ds_authentication.challenge](https://docs.lithic.com/reference/post_three-ds-authentication-challenge) and your Card Program needs to be configured with Out of Band (OOB) Challenges in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for more information).\n\n### Parameters\n\n- `token: string`\n  Globally unique identifier for 3DS Authentication that resulted in PENDING_CHALLENGE authentication result.\n\n- `challenge_response: 'APPROVE' | 'DECLINE_BY_CUSTOMER'`\n  Whether the Cardholder has approved or declined the issued Challenge\n\n### Example\n\n```typescript\nimport Lithic from 'lithic';\n\nconst client = new Lithic();\n\nawait client.threeDS.decisioning.challengeResponse({ token: '182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e', challenge_response: 'APPROVE' })\n```",
+      "## challenge_response\n\n`client.threeDS.decisioning.challengeResponse(token: string, challenge_response: 'APPROVE' | 'DECLINE_BY_CUSTOMER'): void`\n\n**post** `/v1/three_ds_decisioning/challenge_response`\n\nCard program's response to a 3DS Challenge Request.\nChallenge Request is emitted as a webhook [three_ds_authentication.challenge](https://docs.lithic.com/reference/threedsauthenticationchallengewebhook) and your Card Program needs to be configured with Out of Band (OOB) Challenges in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for more information).\n\n### Parameters\n\n- `token: string`\n  Globally unique identifier for 3DS Authentication that resulted in PENDING_CHALLENGE authentication result.\n\n- `challenge_response: 'APPROVE' | 'DECLINE_BY_CUSTOMER'`\n  Whether the Cardholder has approved or declined the issued Challenge\n\n### Example\n\n```typescript\nimport Lithic from 'lithic';\n\nconst client = new Lithic();\n\nawait client.threeDS.decisioning.challengeResponse({ token: '182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e', challenge_response: 'APPROVE' })\n```",
     perLanguage: {
       typescript: {
         method: 'client.threeDS.decisioning.challengeResponse',

src/resources/card-authorizations.ts

@@ -11,7 +11,7 @@ export class CardAuthorizations extends APIResource {
   /**
    * Card program's response to Authorization Challenge. Programs that have
    * Authorization Challenges configured as Out of Band receive a
-   * [card_authorization.challenge](https://docs.lithic.com/reference/post_card-authorization-challenge)
+   * [card_authorization.challenge](https://docs.lithic.com/reference/cardauthorizationchallengewebhook)
    * webhook when an authorization attempt triggers a challenge. The card program
    * should respond using this endpoint after the cardholder completes the challenge.
    */

src/resources/events/events.ts

@@ -207,7 +207,7 @@ export interface Event {
    *   event. Upon receiving this request, the Card Program should issue its own
    *   challenge to the cardholder. After a cardholder challenge is successfully
    *   completed, the Card Program needs to respond back to Lithic by call to
-   *   [/v1/three_ds_decisioning/challenge_response](https://docs.lithic.com/reference/post_v1-three-ds-decisioning-challenge-response).
+   *   [/v1/three_ds_decisioning/challenge_response](https://docs.lithic.com/reference/postthreedschallengeresponse).
    *   Then the cardholder must navigate back to the merchant checkout flow to
    *   complete the transaction. Some merchants will include an `app_requestor_url`
    *   for app-based purchases; Lithic recommends triggering a redirect to that URL

src/resources/fraud/transactions.ts

@@ -71,12 +71,12 @@ export interface TransactionRetrieveResponse {
   /**
    * Provides additional context or details about the fraud report.
    */
-  comment?: string;
+  comment?: string | null;
 
   /**
    * Timestamp representing when the fraud report was created.
    */
-  created_at?: string;
+  created_at?: string | null;
 
   /**
    * Specifies the type or category of fraud that the transaction is suspected or
@@ -106,12 +106,13 @@ export interface TransactionRetrieveResponse {
     | 'ACCOUNT_TAKEOVER'
     | 'CARD_COMPROMISED'
     | 'IDENTITY_THEFT'
-    | 'CARDHOLDER_MANIPULATION';
+    | 'CARDHOLDER_MANIPULATION'
+    | null;
 
   /**
    * Timestamp representing the last update to the fraud report.
    */
-  updated_at?: string;
+  updated_at?: string | null;
 }
 
 export interface TransactionReportResponse {
@@ -142,12 +143,12 @@ export interface TransactionReportResponse {
   /**
    * Provides additional context or details about the fraud report.
    */
-  comment?: string;
+  comment?: string | null;
 
   /**
    * Timestamp representing when the fraud report was created.
    */
-  created_at?: string;
+  created_at?: string | null;
 
   /**
    * Specifies the type or category of fraud that the transaction is suspected or
@@ -177,12 +178,13 @@ export interface TransactionReportResponse {
     | 'ACCOUNT_TAKEOVER'
     | 'CARD_COMPROMISED'
     | 'IDENTITY_THEFT'
-    | 'CARDHOLDER_MANIPULATION';
+    | 'CARDHOLDER_MANIPULATION'
+    | null;
 
   /**
    * Timestamp representing the last update to the fraud report.
    */
-  updated_at?: string;
+  updated_at?: string | null;
 }
 
 export interface TransactionReportParams {

src/resources/three-ds/decisioning.ts

@@ -8,7 +8,7 @@ export class Decisioning extends APIResource {
   /**
    * Card program's response to a 3DS Challenge Request. Challenge Request is emitted
    * as a webhook
-   * [three_ds_authentication.challenge](https://docs.lithic.com/reference/post_three-ds-authentication-challenge)
+   * [three_ds_authentication.challenge](https://docs.lithic.com/reference/threedsauthenticationchallengewebhook)
    * and your Card Program needs to be configured with Out of Band (OOB) Challenges
    * in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for
    * more information).