Subscriber is missing emailAddress

[DVLP]

The endpoint /v1/billing/subscriptions/${subscriptionId} provides email_address, and it works fine in the old paypal-rest-sdk package, but after porting to @paypal/paypal-server-sdk the field emailAddress is missing from the subscriber model
https://github.com/paypal/PayPal-TypeScript-Server-SDK/blob/main/src/models/subscriber.ts

To reproduce

    const { result: subscription } = await subscriptionsController.getSubscription({
      id: subscriptionId
    })
    // now emailAddress is empty
    let emailAddress = subscription.subscriber.emailAddress

[Dani-Kirby]

Hey @DVLP thanks for reaching out!

When it comes to the Subscriptions API integration within our SDK the structure might be a bit different than what you are anticipating. The subscriber model contains the emailAddress field, however it is nested inside the subscriber's shippingAddress object as shown in shippingDetails.ts. This results in a different structure to parse out the field you want, something more akin to: subscription.subscriber.shippingDetails.emailAddress as this in aligned with the specifications provided by our API teams.

I hope this helps! Please let us know if you encounter other issues and we'll be happy to assist.

[DVLP]

Hi Dani, thianks for the reply. The address included inside shippingDetails is optional and not reliable. emailAddress in the root of subscriber is the one that the account belongs to and is always present. For now I had to switch to calling the rest endpoint /v1/billing/subscriptions/${subscriptionId} directly as the field email_address is not missing from subscriber root and it's been there for over a decade, but is not correctly passed by the @paypal/paypal-server-sdk wrapper when a subscription is fetched after its creation.

[Dani-Kirby]

@DVLP thanks for additional context here. For reference, our SDK is based around schema documentation provided by our API teams where it appears the structure is different than what the REST API currently reflects. I'm working with our Subscriptions team to confirm how this should behave and get the correct fixes applied should they identify this is different than what they are anticipating.

I'll be reaching out here as I have more information to share. Thanks again!

[DVLP]

Thanks fort the clarification. For now I'll keep using rest for this action.