2.4.0

What's Changed

• Upgrade to 7.11.0 by @UkuLoskit in #22
• 2.4.0 fixes by @UkuLoskit in #23

Full Changelog: 2.3.0...2.4.0

2.3.0

What's Changed

• Release 2.3.0 by @UkuLoskit in #21

New Contributors

• @UkuLoskit made their first contribution in #21

Full Changelog: 2.2.0...2.3.0

2.2.0

What's Changed

• Release version 2.2.0 by @KWojakiew in #19

New Contributors

• @KWojakiew made their first contribution in #19

Full Changelog: 2.1.0...2.2.0

2.1.0

What's Changed

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

Full Changelog: 2.0.0...2.1.0

2.0.0

What's Changed

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

Full Changelog: 1.5.0...2.0.0

1.5.0

What's Changed

• Add error 401 to Omnimessage API

Full Changelog: 1.4.2...1.5.0

1.4.2

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.1

https://pypi.org/project/messente-api/1.4.1

Generated code with https://www.npmjs.com/package/@openapitools/openapi-generator-cli/v/2.1.17's python-legacy v5.0.0 generator:

• Docs changed

• ApiException subclasses were added:

  

• Models' to_dict changed:

  

1.4.0

https://pypi.org/project/messente-api/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://pypi.org/project/messente-api/1.3.1

Bug Fix

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