ContributionsMost RecentMost LikesSolutionsRe: Delete an asset via API I’m having trouble using the HTTP method for deleting ACCOUNT assets because the asset_id is used in the call. That asset_id is only available in the SnapLogic List snap and not via the API. Is there another API method or path I can use to delete account assets? Re: Delete an asset via API Outstanding, thank you. I would love to see that included in the API documentation. My solution will be to query the Activity API for activities in a project/Dir, and use the HTTP DELETE method for anything in the directory before deleting the directory itself. It’s not ideal, but thankfully I was able to monitor the HTTP traffic in the Management UI and make the same kind of API calls to manage assets. Thanks again. Re: Delete an asset via API Using SnapLogic to manage SnapLogic assets is not an option for me. The activity API has to arguments: filter_asset and filter_project but there’s no example usage in the document. Which values are compatible with those filters? Delete an asset via API After retrieving a list of assets a user has created via the log API, I would like to make another API call to delete them. Is this possible using public or private APIs? Re: Suppress Welcome Email for New Users When you create a user in the UI, there’s a “Send notification emails” box. How can we “uncheck this box” when creating a user via API? Re: How to call the migrate project api? “url”: “https://elastic.snaplogic.com/api/1/rest/public/project/migrate/projects/source”, “method”: “POST” Returns: “The asset does not exist: /projects/source” “url”: “https://elastic.snaplogic.com/api/1/rest/public/project/migrate/{{OrgName}}/projects/source”, “method”: “POST” Returns: “Expecting type of asset [/{{OrgName}}/] to be Dir but was Org” It’s not clear from the documentation where/how to extract the correct values from the Manager and when I enter exact values from the activities API response it still cannot locate them. How to call the migrate project api? I’m getting errors when calling the migrate project to org, e.g. "The asset does not exist: projects/source" Does anybody have examples of successful endpoints and JSON requests? Re: Bug After Converting a Password User to SAML via Okta Thanks Surendar. I’m glad your issue was resolved. SSO is working for us, this is just a small hiccup for the few accounts who did/do have passwords. Maybe a metadata reset would solve this problem too, but I just want to underscore that SSO does work in our instance. Changing Default Sharing Settings for New Users Before I saved my pipeline into my projects folder, the default location for new pipelines and accounts/credentials was a shared folder. Can this be changed to that anything a new user creates is private by default? Bug After Converting a Password User to SAML via Okta After setting up SAML SSO using Okta for some of our users: Current and former password == Yes users get taken to the “login / password” page after click on the snaplogic tile in okta ** Workaround is to just click the tile again and it works / takes to Designer Users who have always been password == No users and SAML only go directly to the app after clicking the snaplogic tile in okta Is this a bug or a problem with my okta configuration?