The WhatsApp Template Management API lets you restore an archived WhatsApp template in Insider One. Use this API version when you authenticate requests with OAuth 2.0.
WhatsApp templates with no activity for 12 months move to the Archived status automatically. You have 28 days to restore an archived template before it is deleted permanently. Restoring a template through the API returns it to the status it had before archiving. You do not need to create it again.
This page covers the endpoint, the required scope, the status after the restore, and the errors you can handle in your integration.
Restore requests use the existing
wa-temp-managescope. No new scope is required.
Endpoint and Headers
POST https://gw.useinsider.com/api/wa/v2/templates/42/unarchive
Header | Required | Description |
|---|---|---|
Authorization | Yes | Your OAuth 2.0 token in the format |
Path Parameter
Parameter | Type | Required | Description |
|---|---|---|---|
id | Integer | Yes | The Insider One template ID. It is the same ID that the List, Get, Edit, and Delete endpoints use. |
Body Parameters
This endpoint does not need a request body. You can send an empty body or {}.
You can restore only templates in ARCHIVED status. You have 28 days after archiving to restore a template. After this period, Meta rejects the restore request, and Insider One returns the Meta error as it is.
To restore a template from the InOne panel, refer to WhatsApp Template’s Quality Rating.
Status After Restore
The template returns to the status it had before it was archived, for example PAUSED. Insider One uses APPROVED only when the earlier status is unknown.
To check the status of the restored template, refer to Get WhatsApp Template Details with OAuth 2.0.
Sample Request
curl --location --request POST 'https://gw.useinsider.com/api/wa/v2/templates/42/unarchive' \
--header 'Authorization: Bearer your-oauth2-token'Sample Response
A successful request returns the following JSON response. The message field confirms that Insider One restored the template.
200 OK
{
"message": "template unarchived"
}Sample Error Responses
Every failure returns a JSON body with a message field. The gateway sets the 401 and 403 responses before the request reaches the template service.
Status | Case | Message | What to do |
|---|---|---|---|
400 | The ID in the path is not a valid template ID. | template id is invalid | Use the template ID that the List endpoint returns. |
401 | The client credentials are invalid, or the bearer token is missing, expired, or malformed. | Set by the gateway | Generate a new token with valid credentials. |
403 | The token does not include the wa-temp-manage scope. | Set by the gateway | Add the scope to your credential, then generate a new token. |
404 | The template does not exist for your account. | template not found | Check the template ID. |
422 | The template is not in ARCHIVED status. | template is not archived | Check the template status with the Get endpoint. Only ARCHIVED templates can be restored. |
422 | The template was never created on Meta. | template has no Meta template id | Contact the Insider One team. |
502 | Meta did not restore the template. | template was not unarchived by Meta | Check the template status with the Get endpoint, then retry if it is still ARCHIVED. |
Set by Meta | Meta rejects the restore, for example after the 28-day restore window. | Meta’s message, returned as it is | Review the Meta message and the template status. |
Limitations
The rate limit is 10 requests per second per account.