2.5.0

What's Changed

• release version 2.5.0 by @KWojakiew in #26

Full Changelog: 2.4.2...2.5.0

2.4.2

What's Changed

• release version 2.4.2 by @KWojakiew in #23
• update NPM API key by @KWojakiew in #24
• switch to github actions for publishing by @KWojakiew in #25

Full Changelog: 2.4.1...2.4.2

2.4.1

What's Changed

• release version 2.4.1 by @KWojakiew in #19
• update npm api key by @KWojakiew in #20
• update NPM api key by @KWojakiew in #21
• update travis deployment by @KWojakiew in #22

Full Changelog: 2.4.0...2.4.1

2.4.0

What's Changed

• Release version 2.4.0 by @KWojakiew in #18

Full Changelog: 2.2.0...2.4.0

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.