POST /v1/issuing/personalization_designs/{personalization_design}

Updates a card personalization object.

Servers

https://api.stripe.com/

Path parameters

Name	Type	Required	Description
`personalization_design`	String	Yes

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/x-www-form-urlencoded"

Request body fields

Name	Type	Required	Description
`transfer_lookup_key`	Boolean	No	If set to true, will atomically remove the lookup key from the existing personalization design, and assign it to this personalization design.
`name`		No	Friendly display name. Providing an empty string will set the field to null.
`expand[]`	Array	No	Specifies which fields in the response should be expanded.
`preferences`	Object	No	Information on whether this personalization design is used to create cards when one is not specified.
`preferences.is_default`	Boolean	Yes
`metadata`	Object	No	Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.
`carrier_text`		No	Hash containing carrier text, for use with physical bundles that support carrier text.
`lookup_key`		No	A lookup key used to retrieve personalization designs dynamically from a static string. This may be up to 200 characters.
`physical_bundle`	String	No	The physical bundle object belonging to this personalization design.
`card_logo`		No	The file for the card logo, for use with physical bundles that support card logos. Must have a `purpose` value of `issuing_logo`.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.