Acrobat API user and user assets

[Ruben2852501452o3]

I've been playing with the acrobat API, to create PDF's, but so far I haven't found away to:
1. Check if the user has Adobe account: the idea is to check if the current user is logged in to their account, if so, get the user's info, such as name and email.

2. Once we have the user's info, then upload a PDF to their account, now this PDF is generated based on user's interaction.

3. Once the PDF has been uploaded, get the url for review or share url.

So far I can only create PDF's, and the created PDF is uploaded to the API credentials users, not the actual user that is interacting with the app.

We want to upload the PDF to the actual user's acrobat account and then get the shared URL from that account, but I think that is something that Acrobat API can't do so far...

On the other hand, when using the acrobat viewer I need the "comment" section to be available for any PDF, but what I'm getting is an error regarding CSP(Content-Security-Policy: The page’s settings blocked), script and style are getting blocked.

When using the SDK viewer, does the comments remain in place for all users or do they go away?

We need to keep the comments so that anyone with the right access can see them...

[Raymond Camden]

1) Our APIs don't do that.

2) Nope, see abovve.

3) See above.

If there are APIs to work with Acrobat's online storage, than that would allow for what you want, but it's not an area covered by our APIs.

Embed+Comments: No, comments you add will ONLY be in that user's web page. You can, however, use JavaScript to override the Save event and store the bits locally to your server, but you would need to have server-side code ready to handle that.

[Ruben2852501452o3]

Hello @Raymond Camden, thank you for the answer.

So what you are saying is that the created PDF can not be uploaded to the user's account via API(acrobat.adobe.com).

Regarding the embed+comments, I think I figure it out, the viewer interacts will render the PDF and based on it's configuration and preferences it will or not show the comments, but the comments and/or notations has to be saved on my end of the app, only means more work for me, which is the longest way for the functionality of my app.

Basically the idea is to generate a PDF on our end and upload it to the user's account(acrobat.adonbe.com) with share permission on and retrieve the share URL.

[Raymond Camden]

Correct, we have nothing to do with a user's Adobe account or storage.