Updates a simulation using its ID.
For scenario simulations, you can optionally include a config.entities object in the request body with entity IDs to populate
simulated webhook payloads with real data. The API key making the request needs read permissions:
For example, when updating a subscription renewal scenario simulation with an API key that has a subscription.read permission but not a transaction.read permission,
the request succeeds and the subscription data will be used in simulated payloads, but the related transaction data won’t be used in payloads and falls back to a static example.
If you don’t provide a config.entities object, simulated webhook payloads are populated with static examples.
If successful, your response includes a copy of the updated simulation entity.
Requests are authenticated with API keys. Provide your API key as a Bearer token in the Authorization header.
API keys are assigned permissions, granting them access to entities and operations.
Each endpoint may require one or more permissions, defined with the x-permissions extension.
Values for include parameters may require specific permissions as defined in the x-enum-permissions extension.
See all available permissions in the permission schema or documentation.
Get an API key and select the permissions you need from the Paddle dashboard under Paddle > Developer Tools > Authentication.
Paddle ID of the simulation entity to work with.
"ntfsim_01gt261ms8ew72a0vnm5p5ne2q"
Single event simulations play a single event.
Paddle ID of the notification setting where this simulation is sent, prefixed with ntfset_.
"ntfset_01gt21c5pdx9q1e4mh1xrsjjn6"
Name of this simulation.
Whether this entity can be used in Paddle.
active, archived Single event sent for this simulation, in the format entity.event_type.
address.created, address.imported, address.updated, adjustment.created, adjustment.updated, api_key.created, api_key.expired, api_key.expiring, api_key.revoked, api_key.updated, business.created, business.imported, business.updated, customer.created, customer.imported, customer.updated, discount.created, discount.imported, discount.updated, payment_method.saved, payment_method.deleted, payout.created, payout.paid, price.created, price.imported, price.updated, product.created, product.imported, product.updated, report.created, report.updated, subscription.activated, subscription.canceled, subscription.created, subscription.imported, subscription.past_due, subscription.paused, subscription.resumed, subscription.trialing, subscription.updated, transaction.billed, transaction.canceled, transaction.completed, transaction.created, transaction.paid, transaction.past_due, transaction.payment_failed, transaction.ready, transaction.revised, transaction.updated Simulation payload. Pass a JSON object that matches the schema for an event type to simulate a custom payload. Set to null to clear and populate with a demo example.