EndUserMessagingSocial / Client / update_whatsapp_flow

update_whatsapp_flow

EndUserMessagingSocial.Client.update_whatsapp_flow(**kwargs)

Updates the metadata of a WhatsApp Flow, such as its name or categories. This does not update the Flow JSON definition. Use UpdateWhatsAppFlowAssets to update the Flow JSON.

See also: AWS API Documentation

Request Syntax

response = client.update_whatsapp_flow(
    id='string',
    flowId='string',
    flowName='string',
    categories=[
        'SIGN_UP'|'SIGN_IN'|'APPOINTMENT_BOOKING'|'LEAD_GENERATION'|'SHOPPING'|'CONTACT_US'|'CUSTOMER_SUPPORT'|'SURVEY'|'OTHER',
    ],
    endpointUri='string',
    metaAppId='string'
)
Parameters:

  • id (string) –

    [REQUIRED]

    The ID of the WhatsApp Business Account associated with this Flow.

  • flowId (string) –

    [REQUIRED]

    The unique identifier of the Flow to update.

  • flowName (string) – The updated name for the Flow.

  • categories (list) –

    The updated categories for the Flow.

    • (string) –

      The category that classifies the business purpose of a WhatsApp Flow.

  • endpointUri (string) – Optional HTTPS endpoint for a dynamic Flow, registered with Meta as the Flow’s endpoint_uri and called by Meta directly. When omitted, the Flow’s endpoint is unchanged.

  • metaAppId (string) – Optional Meta app ID to attach to the Flow. Meta signs data-exchange requests with the attached app’s secret, so attaching your own app is what enables X-Hub-Signature-256 and flow_token_signature verification at your endpoint. Meta requires the app to be owned by the same business that owns the WABA. Attaching your own app is one-way: the service’s app cannot be re-attached afterwards. When omitted, the attached app is unchanged. (Set via update because Meta ignores application_id at creation time.)

Return type:

dict

Returns:

Response Syntax

{}

Response Structure

  • (dict) –

Exceptions