WhatsApp Business Profile API

Prerequisites

These endpoints require your account to already have WhatsApp connected (Meta Cloud API, CRM, or Pinbot). Your account type and connection details are already configured on our side — you don't need to send anything extra to specify which provider you're on; just call the endpoint and it's handled automatically.

If your account isn't connected, or isn't one of the supported types, requests fail with a 422 — see Error Responses below.

Authentication

Required on all endpoints below. Send a JWT as a Bearer token:

Authorization: Bearer <jwt_token>

{{base_url}} = https://wa20.nuke.co.in/v6/api

1. Get Business Profile

Fetches your current live WhatsApp Business profile details directly from the provider (Meta / Pinbot).

Endpoint

GET {{base_url}}/account/business-profile

Headers

Header	Value
`Authorization`	`Bearer <jwt_token>`

Example Request

curl --location '{{base_url}}/account/business-profile' \
--header 'Authorization: Bearer {{bearer_token}}'

Example Response — 200 OK

{
  "message": "Business profile fetched",
  "data": {
    "about": "Hello there! I am using WhatsApp.",
    "address": "123 Business Road",
    "description": "Official WhatsApp Business Account",
    "email": "[email protected]",
    "profile_picture_url": "https://scontent.whatsapp.net/...",
    "websites": ["https://www.business.com"],
    "vertical": "RETAIL"
  }
}

Response Fields

Field	Description
`message`	Confirmation message.
`data.about`	The "About" status text on your profile.
`data.address`	Business address.
`data.description`	Business description.
`data.email`	Business contact email.
`data.profile_picture_url`	URL of the current profile photo.
`data.websites`	Array of business website URLs.
`data.vertical`	Business category/vertical (as set with your provider).

2. Update Profile Photo

Uploads and applies a new photo to your live WhatsApp Business profile.

Endpoint

POST {{base_url}}/account/business-profile/photo

Headers

Header	Value
`Authorization`	`Bearer <jwt_token>`
`Content-Type`	`multipart/form-data` (set automatically by your HTTP client)

Body (form-data)

Field	Type	Required	Description
`channel`	text	No	Channel identifier accepted with the request.
`file`	file	Yes	The image file to set as your profile photo.

Example Request

curl --location '{{base_url}}/account/business-profile/photo' \
--header 'Authorization: Bearer {{bearer_token}}' \
--form 'channel="whatsapp"' \
--form 'file=@"/path/to/photo.jpg"'

Example Response — 200 OK

{
  "message": "Profile photo updated successfully",
  "data": {
    "success": true
  }
}

The exact shape of data mirrors whatever the underlying provider (Meta / Pinbot) returns for the apply step — treat it as provider passthrough rather than a fixed schema.

How It Works

Under the hood, the photo is uploaded and applied in three steps against your connected WhatsApp account. If any step fails, the specific error is surfaced in the response — you don't need to do anything differently in Postman, just send the request as shown above.

3. Update Business Profile

Updates one or more fields on your live WhatsApp Business profile. Only the fields you send are updated.

Endpoint

PUT {{base_url}}/account/business-profile

Headers

Header	Value
`Content-Type`	`application/json`
`Authorization`	`Bearer <jwt_token>`

Body Parameters

Parameter	Type	Required	Description
`about`	string	No	The "About" status text.
`address`	string	No	Business address.
`description`	string	No	Business description.
`email`	string	No	Business contact email.
`vertical`	string	No	Business category/vertical.
`websites`	array of strings	No	Business website URL(s).
`channel`	string	No	Channel identifier accepted with the request.

Note: at least one profile field (about, address, description, email, vertical, or websites) should be sent — sending none will still call the provider but with nothing to change beyond the required messaging_product value.

Example Request

{
  "about": "Hello there! I am using WhatsApp.",
  "description": "Official WhatsApp Business Account",
  "address": "123 Business Road",
  "email": "[email protected]",
  "websites": ["https://www.business.com"]
}

curl --location --request PUT '{{base_url}}/account/business-profile' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {{bearer_token}}' \
--data '{
    "about": "Hello there! I am using WhatsApp.",
    "description": "Official WhatsApp Business Account",
    "address": "123 Business Road",
    "email": "[email protected]",
    "websites": ["https://www.business.com"]
}'

Example Response — 200 OK

{
  "message": "Business profile updated successfully",
  "data": {
    "success": true
  }
}

Error Responses

These apply across all three endpoints unless noted otherwise:

Status	Message	Endpoint(s)	Reason
`404`	`WhatsApp account not found in wati table`	Get / Update Business Profile	Your account doesn't have a WhatsApp connection set up yet.
`404`	`No WhatsApp account configured for this user`	Update Profile Photo	Your account doesn't have a WhatsApp connection set up yet.
`422`	`WhatsApp credentials are not configured`	All three	Your WhatsApp connection is missing required credentials — contact support to fix your account setup.
`422`	`Business profile is only supported for Meta Cloud API, CRM and Pinbot accounts`	All three	Your account's connected provider doesn't support this feature.
`422`	`Could not resolve phone_number_id from account URL`	All three	Your account's WhatsApp connection isn't configured correctly — contact support.
`422`	`Pinbot account is missing its Business Manager ID (bmid)`	All three	Your account setup is incomplete — contact support.
`4xx` / `422`	Provider-specific error message	All three	The upstream WhatsApp provider rejected the request — the message explains why.

Notes

These endpoints act directly on your live, already-connected WhatsApp Business account — changes here take effect immediately, unlike the Profile Request API which submits a request for approval.
The channel field accepted on Update Profile Photo and Update Business Profile is recorded with the request; you don't need to configure anything else to tell us which provider you're on — that's already set up on your account.
If a request fails partway through Update Profile Photo, retry the same request — it's safe to call again.