chore(internal): regenerate SDK with no functional changes

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 213
-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

src/lithic/resources/card_authorizations.py

@@ -54,7 +54,7 @@ def challenge_response(
 
         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.
 
@@ -120,7 +120,7 @@ async def challenge_response(
 
         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/lithic/resources/three_ds/decisioning.py

@@ -54,7 +54,7 @@ def challenge_response(
 
         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).
@@ -177,7 +177,7 @@ async def challenge_response(
 
         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).

src/lithic/types/event.py

@@ -196,7 +196,7 @@ class Event(BaseModel):
       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