Olha

Hi @alecrobertson1 I'm not sure why it was done. But I've tried the import you mentioned and it works. Can you please share the whole code snippet?

Hi @Arsalanliaqat PR with the hotfix is ready but it breaks the default import functionality. That's why we're considering other options, and it takes time. Sorry for the inconvenience.

Hi @davidklemme, thank you for the improvement suggestion. Unfortunately, as it was mentioned above, we can't make any changes neither to Mailjet server itself nor to the documentation repo, only...

Hi @MaxLmqr did you try suggestions from above? Did it work for you? Please let us know if you have any questions, otherwise the issue will be closed in 48h.

Got it, thank you for the quick response! Just wanted to double-check before starting investigating the issue.

Hello @MaxLmqr, TypeScript fix is available in the new major [release](https://github.com/mailjet/mailjet-apiv3-nodejs/releases/tag/v6.0.0). Types naming was changed so please refer the [Readme](https://github.com/mailjet/mailjet-apiv3-nodejs#typescript) for more details.

Response type will be `LibraryResponse`. `LibraryResponse` is a generic so you need to specify what exact entity you're using. Then, you'll get all of the Contact properties: ``` const result:...

Sure, you don't need to put the type twice, just remove it in the `request` part. So it should be: ``` const result: LibraryResponse = await mailjet .get('contact', { version:...

Hello @gdeichen, did you try to use a static IP address as suggested above? Did it solve your problem?

@gdeichen thank you for the quick response. I'm closing the issue then.