2.2.0

What's Changed

• release version 2.2.0 by @KWojakiew in #16

New Contributors

• @KWojakiew made their first contribution in #16

Full Changelog: 2.1.0...2.2.0

2.1.0

What's Changed

• Release version 2.1.0 by @krystian-wojakiewicz in #15

Full Changelog: 2.0.0...2.1.0

2.0.0

What's Changed

• Release version 2.0.0 by @krystian-wojakiewicz in #14

Full Changelog: 1.5.0...2.0.0

1.5.0

What's Changed

• Add error 401 to Omnimessage API

Full Changelog: 1.4.1...1.5.0

1.4.1

What's Changed

• Add parameter ttl to Omnichannel API message sending request. This allows the users to specify the validity period of a message in the unit of seconds (as opposed to minutes for the validity field). Preserves backward compatibility with validity.

1.4.0

https://www.npmjs.com/package/messente_api/v/1.4.0

Add an optional priority field to Omnichannel API message sending request. This field sets the priority of the message. Messages are processed starting with in highest priority queue first and lowest priority queue last. This for example allows to prioritize OTP messages over marketing traffic.

The new field has three possible values:

• low,
• regular,
• high.

1.3.1

https://www.npmjs.com/package/messente_api/v/1.3.1

Bug Fix

[contacts] Make sure scheduled deletion date field is only in responses, not in requests

1.3.0

#7:

https://www.npmjs.com/package/messente_api/v/1.3.0

Added Functionality

• [phonebook-api][contacts] Add scheduled deletion date to response
  • The date (in ISO 8601 format, YYYY-MM-DD) on which the contact is going to be deleted because it has not belonged to a group for 30 days
• [statistics-api] Allow fetching Telegram statistics

Bug Fixes

• [omnichannel-api] Declare error item source nullable
• [omnichannel-api] Make cancelling a message return an empty object

v1.2.0

• Add Number Lookup API
• Add Statistics API

https://www.npmjs.com/package/messente_api/v/1.2.0

v1.1.0

Enable sending Telegram messages