Is it an acceptable pattern to use the mbox cookie session value as sessionID parameter for the Target REST API calls? https://developers.adobetarget.com/api/delivery-api/  

Does the current version of the Node SDK only make mbox calls asynchronously?  

How long does the Node SDK promise take to time out?   Like if I'm using this method: const offerAttributes = await targetClient.getAttributes(["attribute"]);  

I was able to fix this by setting the "bodyHidingEnabled" config option to false https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/functions-overview/targetgobalsettings.html?lang=en 

Is there a way to get the activity name of a server side A/B test using the getAttributes method in the Java server side SDK?

I'm following the guide located here: https://experienceleague.adobe.com/docs/id-service/using/implementation/ecid-a4t-target.html?lang=en However when I call visitor.generatePayload I get the following error: TypeError: visitor.generatePayload is not a function    at app.get (C:\aa\NodeMaster\index...

What exactly do you mean by "Implement visitor id correctly"?   My understanding is that the Visitor ID service can only function on the front end (client side), i.e. the browser.  That being the case, how is the Delivery API supposed to have access to the required artifacts (sessionID, ECID, etc.) ...

So what is the recommended pattern on how to access/persist the sessionID on a pure server side solution?  Is this even possible? Is the VisitorID service (JavaScript) required to fetch information required for user persistence/bucketing (sessionID, ECID, etc.)?  If so it seems that the Delivery API...

Thanks! So in this context would "session" be referring to browser session, or Adobe session (or some other session)?

What exactly is the sessionID parameter in the Delivery API request call? https://clientCode.tt.omtrdc.net/rest/v1/delivery?client=clientCode`&sessionId=d359234570e04f14e1faeeba02d6ab9914e\ -H 'Content-Type: application/json' \