v1.3.3

Full Changelog: v1.3.3.82...v1.3.3

Deprecated

• Endpoint: /instance/connectionState/{instanceName}

Added

• externalAttributes

  The externalAttributes attribute is an optional field that can be used to add custom information or metadata to the message being sent. This field is useful for attaching additional data that you want to track or associate with the message throughout the sending and receiving process without affecting the main content of the message.

  Details of the externalAttributes Attribute

  • Type: string
  • Description: This field can accept various types of values, including simple strings, booleans, numbers, JSON objects, or JSON arrays. Below are the specifications for the accepted data types:
    • [string] - A simple text string.
    • [string[boolean]] - A string representing a boolean value.
    • [string[number]] - A string representing a numeric value.
    • [string[Json[Object]]] - A string containing a JSON object.
    • [string[Json[Array]]] - A string containing a JSON array.

  Usage

  When you create a message and include the externalAttributes field, the specified values are transmitted along with the message. These values are then forwarded to the associated webhook, providing a way to "stamp" the message with additional information that can be used for tracking, auditing, or other analytical or processing purposes.

  For example, you could use externalAttributes to store a user ID, process status, or any other relevant information you want to associate with the message. When the message is processed by the target system or responded to via webhook, these external attributes are included in the payload of the response, allowing you to use them as needed in your workflow.

  Example:

  {
    "number": "123@broadcast",
    "options": {
      "externalAttributes": "<any> - optional",
      "delay": 1200,
      "presence": "composing"
    },
    "textMessage": {
      "text": "text"
    }
  }

• Endpoint:

  1. /instance/fetchInstance/:instanceName
     Response: 200

  {
    "id": number,
    "name": string,
    "description": string,
    "connectionStatus": string,
    "ownerJid": string,
    "profilePicUrl": string,
    "createdAt": dateTime,
    "updatedAt": dateTime,
    "Webhook": { ... },
    "Whatsapp": {
        "connection": {
            "state": string,
            "statusReason": number
        }
    }
  }

  2. /message/sendList/legacy/:instanceName

v1.3.2

Full Changelog: v1.3.2.79...v1.3.2

v1.3.1

What's Changed

• Fix typo in instance.guard.ts by @w3nder in #102
• Update .env.dev by @caiquezanetoni in #106
• Fix: qrcode trigger limit by @RianBrenoPolonini in #111

New Contributors

• @caiquezanetoni made their first contribution in #106
• @RianBrenoPolonini made their first contribution in #111

Full Changelog: v1.3.0...v1.3.1

v1.3.0

Dockerfile

v1.2.8

socketConfig

v1.2.7

• from query.owner to header['x-owner']: e1f9518
• saving credential in session cookies: 120ec3e
• Dockerfile: update node version: 2d5ffc0

v1.2.6

EXPIRIN_IN: default=0

v1.2.5

💥 bugfix: audio validation

v1.2.4

Merge pull request #60 from jeankassio/mimetype

Change mimetype audio Message of audio/ogg to audio/aac

v1.2.3

pull [https://github.com/code-chat-br/whatsapp-api/pull/39] adjusted