Bandwidth::Message.get doesn't work with V2 api

[fliptaboada]

Currently there's no way of using Bandwidth::Message.get with the V2 api and there's no such method on Bandwidth::V2::Message.
The authentication is also different, it uses the same credentials as the dashboard/iris client, so it's very confusing, I had to create another client and call it directly to make it work.

Will this library continue to be supported/improved for V2 or should everyone move to the new ruby-sdk?

[jmulford-bw]

Hi @fliptaboada,

You are correct, this package does not have get messages for the V2 API. The ruby-sdk package will eventually have the get messages functionality for the V2 API, but we are waiting for an API change that will make pagination much easier via the SDK before releasing that. If you want that sooner (as in you don't really need pagination), we can do an early release.

If you're fully migrated to V2, you can use your dashboard/iris credentials on all of the V2 messaging API. Hopefully that could alleviate the credential confusion (I agree it's very confusing)

Our future plan is to not maintain this package long term, but we are more than happy to continue accepting open source contributions and fix major vulnerabilities

[fliptaboada]

Thanks for the super fast response @jmulford-bw !

You are correct, this package does not have get messages for the V2 API. The ruby-sdk package will eventually have the get messages functionality for the V2 API, but we are waiting for an API change that will make pagination much easier via the SDK before releasing that. If you want that sooner (as in you don't really need pagination), we can do an early release.

That makes sense.
The way I did is working for now and I'm only fetching single messages, so there's no need for an early release from you guys.

If you're fully migrated to V2, you can use your dashboard/iris credentials on all of the V2 messaging API. Hopefully that could alleviate the credential confusion (I agree it's very confusing)

Using the same credentials will indeed make things easier to understand.

Our future plan is to not maintain this package long term, but we are more than happy to continue accepting open source contributions and fix major vulnerabilities

I think it would be good to add some warning on the README then, mentioning the other sdk.
We just started integrating with Bandwidth and we ended up using this one, we only found about the other later on.

[jmulford-bw]

Sounds good, thank you for the feedback!