RCS

The Unarchive Template API enables businesses to restore previously archived WhatsApp message templates associated with a WhatsApp Business Account (WABA).

WhatsApp message templates that remain inactive for 12 months or longer are automatically archived by Meta. Once archived, these templates cannot be used to send WhatsApp template messages and are scheduled for deletion after 28 days.

This API allows businesses to restore archived templates within the permitted 28-day period, enabling them to return to their previous status and become eligible for use in WhatsApp template messaging.

The API supports restoring one or multiple templates in a single request by accepting template IDs through the hsm_ids parameter.

Before forwarding the request to Meta, the service validates the WABA ID against the authenticated company and verifies that the WABA is configured on API V2.

API Functionality

The API provides the following capabilities:

Restore one or multiple archived WhatsApp message templates.

Support bulk template restoration using the hsm_ids parameter.

Validate WABA ownership against the authenticated company.

Verify that the WABA is configured on API V2.

Forward validated requests to Meta for processing.

Handle successful, partially successful, and failed restoration requests.

Business Rules and Validations
The following business rules apply when using the Unarchive Template API:

Only archived templates can be submitted for unarchiving.

Templates can be unarchived within 28 days of archival, whether archived manually or automatically.

Templates that have been inactive for 12 months or longer are automatically archived by Meta.

Archived templates cannot be used to send WhatsApp template messages.

The WABA ID must belong to the authenticated company.

The WABA must be configured on API V2.

Multiple template IDs can be provided in a single request using the hsm_ids parameter.

Templates that exceed the 28-day restoration window are no longer eligible for unarchiving.

Request Processing Workflow
The API follows the below processing sequence:

Receives the WABA ID and template IDs (hsm_ids) from the API request.

Validates whether the WABA ID belongs to the authenticated company.

Checks whether the WABA is configured on API V2.

Validates the request parameters.

Forwards the validated request to Meta.

Processes Meta's response and returns the appropriate result to the client.