What does adding _data onto API calls do in Stripe?

What does adding _data onto API calls do in Stripe?

• A. Enables idempotent operations.
• B. Enables dynamic creation of nested objects.
• C. Changes API version automatically.
• D. Stores data in a separate log.

Answer: (B)

Adding _data onto Stripe API calls signals that the parameter contains a nested object (or a set of nested objects) to be created as part of the same request. This lets you dynamically create related resources on the fly within a single API call instead of having to create them in separate requests. For example, you can supply source_data to create a new payment source when creating a customer, or include subscription_data to set up a subscription immediately with specific items. The result is a cohesive operation that builds the full set of related resources in one call. Idempotency keys control safe retries and are not affected by _data. API version is determined by request headers or account settings, not by adding _data. Storing data in a separate log is handled by Stripe’s logging and auditing mechanisms, not by the _data suffix.

Adding _data onto Stripe API calls signals that the parameter contains a nested object (or a set of nested objects) to be created as part of the same request. This lets you dynamically create related resources on the fly within a single API call instead of having to create them in separate requests. For example, you can supply source_data to create a new payment source when creating a customer, or include subscription_data to set up a subscription immediately with specific items. The result is a cohesive operation that builds the full set of related resources in one call.

Idempotency keys control safe retries and are not affected by _data. API version is determined by request headers or account settings, not by adding _data. Storing data in a separate log is handled by Stripe’s logging and auditing mechanisms, not by the _data suffix.