Skip to content

Stripe: Create a test clock

Stripe testHelpers.postTestHelpersTestClocks: arguments, response, policy and SDK examples.

← Test helpers operations · Get started

Operation stripe.posttesthelperstestclocks

Provider route: POST /v1/test_helpers/test_clocks. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/stripe with npm, or alter-sdk-stripe with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { StripeIntegration } from "@alter-ai/stripe";
async function execute(input: Parameters<StripeIntegration["testHelpers"]["postTestHelpersTestClocks"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new StripeIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.testHelpers.postTestHelpersTestClocks(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_stripe import StripeIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = StripeIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.test_helpers.post_test_helpers_test_clocks(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
headersobjectOptionalAdditional keys: not allowed
headers.Idempotency-KeystringOptionalMinimum length: 1
Maximum length: 255
bodyobjectRequired within parentAdditional keys: not allowed
body.customerstringOptionalExisting customer this test clock will be attached to. Once attached, customers can’t be removed from a test clock.
Maximum length: 5000
body.expandarrayOptionalSpecifies which fields in the response should be expanded.
body.expand[]stringEach itemMaximum length: 5000
body.frozen_timeintegerRequired within parentThe initial frozen time for this test clock.
Format: unix-time
body.namestringOptionalThe name for this test clock.
Maximum length: 300

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Create a test clock — response body

Referenced models: Create a test clock — response body

Create a test clock — response body
FieldTypePresenceDescription and constraints
$objectRootA test clock enables deterministic control over objects in testmode. With a test clock, you can create
objects at a frozen time in the past or future, and advance to a specific future time to observe webhooks and state changes. After the clock advances,
you can either validate the current state of your scenario (and test your assumptions), change the current state of your scenario (and test more complex scenarios), or keep advancing forward in time.
createdJSONRequired within parent
created (anyOf 1)integerAlternativeTime at which the object was created. Measured in seconds since the Unix epoch.
Format: unix-time
created (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
deletes_afterJSONRequired within parent
deletes_after (anyOf 1)integerAlternativeTime at which this clock is scheduled to auto delete.
Format: unix-time
deletes_after (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
frozen_timeJSONRequired within parent
frozen_time (anyOf 1)integerAlternativeTime at which all objects belonging to this clock are frozen.
Format: unix-time
frozen_time (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
idstringRequired within parentUnique identifier for the object.
Maximum length: 5000
livemodebooleanRequired within parentIf the object exists in live mode, the value is `true`. If the object exists in test mode, the value is `false`.
nameJSONOptional
name (anyOf 1)stringAlternativeThe custom name supplied at creation.
Maximum length: 5000
name (anyOf 2)nullAlternative
objectstringRequired within parentString representing the object's type. Objects of the same type share the same value.
Known values: test_helpers.test_clock
statusstringRequired within parentThe status of the Test Clock.
Known values: advancing, internal_failure, ready
status_detailsModelRequired within parentExpand Create a test clock — response body — status details

Referenced models: Create a test clock — response body — status details

Create a test clock — response body — status details
FieldTypePresenceDescription and constraints
$objectRoot
advancingModelOptionalExpand Create a test clock — response body — status details advancing

Referenced models: Create a test clock — response body — status details advancing

Create a test clock — response body — status details advancing
FieldTypePresenceDescription and constraints
$objectRoot
target_frozen_timeJSONRequired within parent
target_frozen_time (anyOf 1)integerAlternativeThe `frozen_time` that the Test Clock is advancing towards.
Format: unix-time
target_frozen_time (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$

SDK function policy ID: stripe.posttesthelperstestclocks. Catalog operation: PostTestHelpersTestClocks. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Pinned headers: {"Stripe-Version": "2026-09-30.endive"}

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.