Create template — estimate

Price the request without executing it. Same body as POST /v1/messaging/whatsapp/templates.

post/v1/messaging/whatsapp/templates/estimate

Request

Base URL: https://apihub.co.il
URL: https://apihub.co.il/v1/messaging/whatsapp/templates/estimate
Auth: HTTP bearer

Request body

namestring required

Template name (lowercase, letters/numbers/underscores, must start with a letter)

category'AUTHENTICATION' | 'MARKETING' | 'UTILITY' required

Template category

languagestring required

Template language code (e.g., en_US)

accountIdstring required

WhatsApp account ID

parameter_format'POSITIONAL' | 'NAMED' | 'positional' | 'named'

Variable style: POSITIONAL ({{1}}, the default) or NAMED ({{customer_name}}). Named templates provide examples via body_text_named_params / header_text_named_params. Inferred as NAMED when omitted but a named-params example is present.

library_template_namestring

Name of a pre-built template from Meta's template library (e.g., "appointment_reminder", "auto_pay_reminder_1", "address_update"). When provided, the template is pre-approved by Meta with no review wait. Omit components when using this field.

message_send_ttl_secondsinteger

Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 (create only) keeps the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).

library_template_body_inputsobject

Optional body customizations for library templates. Available options depend on the template (e.g., add_contact_number, add_learn_more_link, add_security_recommendation, add_track_package_link, code_expiration_minutes).

Response

Estimate

operationstring

estimated_creditsnumber

credits_to_reservenumber

estimated_usageobject

notestring nullable

sufficientboolean

Changes

No recorded changes to this operation across all 2 revisions of this API.