Skip to main content
POST
/
instances
/
{instanceId}
/
token
/
{token}
/
send-sticker
Send sticker
curl --request POST \
  --url https://api.z-api.io/instances/{instanceId}/token/{token}/send-sticker \
  --header 'Client-Token: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "phone": "<string>",
  "sticker": "<string>"
}
'

​
Overview

Method responsible for sending stickers to your chats. You can work with stickers in 2 ways:
  • By Link: if you have the sticker hosted somewhere on the internet, just send the link;
  • By Base64: if you want to send the sticker in Base64 format.
If you choose Base64, before the binary you need to add the following expression: data:image/png;base64, followed by your Base64 code.You can verify if the Base64 is correct by pasting it into your browser’s address bar.

​
Attributes

​
instanceId
string
required
Your instance ID. Available in the Z-API panel under Instances.
​
token
string
required
Your Z-API instance token.

​
Required

​
phone
string
required
Recipient’s phone number (or group ID for group messages) in DDI DDD NUMBER format. E.g.: 551199999999
​
sticker
string
required
Sticker link or Base64

​
Optional

​
messageId
string
Attribute used to reply to a chat message, just add the messageId of the message you want to reply to
​
delayMessage
number
Delay added to the message. You can choose between a range of 1 to 15 sec, meaning how many seconds it will wait before sending the next message. (E.g.: “delayMessage”: 5). The default delay if not provided is 1 to 3 sec
​
stickerAuthor
string
Sticker author name

​
Request Body

By link: 
{
  "phone": "5511999999999",
  "sticker": "https://example.com/sticker.png"
}
By Base64: 
{
  "phone": "5511999999999",
  "sticker": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAyAAAAMgCAIAAABUEpE..."
}

​
Response

​
200

{
  "zaapId": "3999984263738042930CD6ECDE9VDWSA",
  "messageId": "D241XXXX732339502B68",
  "id": "D241XXXX732339502B68"
}

​
405

Make sure you are correctly sending the method specification, that is, verify that you sent POST or GET as specified at the beginning of this topic.

​
415

If you receive a 415 error, make sure to add the “Content-Type” header to your request, which in most cases is “application/json”.