SPSiteManager API Endpoint not creating requested site

[ogeam]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Power Automate workflow

Describe the bug / error

We are maintaining a Power Automate workflow for creating a new SharePoint site. We recently had a scenario where a request was submitted for the creation of a SharePoint site, and the SPSiteManager/Create endpoint (https://tenantname.sharepoint.com/_api/SPSiteManager/Create) returned a success response. However, the site was not created. See below for the request body and response

Request Body:
{ "request": { "Title": "Post Luxembourg-Wallix Assessment", "Url": "https://tenantname.sharepoint.com/sites/Post Luxembourg-Wallix Assessment", "Description": "Site used to work collaboratively and store all documents, deliverables related to the assessment", "Owner": "Owner's email address", "Lcid": 1033, "WebTemplate": "STS#3", "SiteDesignId": "53e46c84-923a-406f-86ff-1fdc9dc67ae4", "ShareByEmailEnabled": true } }

Response Body:
{ "d": { "Create": { "__metadata": { "type": "Microsoft.SharePoint.Portal.SPSiteCreationResponse" }, "SiteId": "", "SiteStatus": 3, "SiteUrl": "" } } }

Steps to reproduce

Expected behavior

Create site with SiteStatus code value of '2'

[Ashlesha-MSFT]

Hello @ogeam,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@ogeam ,
We are currently unable to reproduce the issue when attempting to create a POST action in the workflow using the following endpoint:
** https://tenantname.sharepoint.com/_api/SPSiteManager/Create.**

It appears that the URL is not valid. We have also tried replacing the tenantname placeholder with the actual tenant name, but we still encountered the same issue. Could you please assist us with the correct steps or provide further guidance to reproduce the problem?

[ogeam]

Thanks for getting back. Yes, I substituted our tenant name for "tenantname" in the SharePoint URL for privacy reasons.
Is there any way I can share the flow ID with you privately?