Are APIs available to create & populate Microsoft Loop pages?

Question

Are APIs available to create & populate Microsoft Loop pages?

Vineet P 0

Hi Microsoft team,

Our company is moving from Quip to Microsoft Loop. I’m building an internal utility to help colleagues migrate one or more Quip documents into native, editable Loop pages.

Quip provides APIs for extracting content. Does Microsoft currently offer a supported public or preview API to:

Create pages in a selected Loop workspace?
Populate pages with headings, formatted text, tables, images and links?
Read page content to verify the migration?

Editable snapshots are sufficient, we don’t need to preserve spreadsheet formulas or revision history.

If these capabilities aren’t available, is there a supported import approach or a roadmap for Loop content APIs? Links to documentation or preview access would be appreciated.

Thanks!

0 comments

2 answers

Your answer

Answer 1

Dear @Vineet,

I hope you’re having a good day

Building an internal migration utility is a great idea, though you are going to hit a hard roadblock with Microsoft Loop right now. Currently, Microsoft does not offer any public or preview APIs (including via Microsoft Graph) to create Loop pages, inject content like headings and tables, or read page blocks back for verification.

The reason comes down to how Loop stores data under the hood. Loop workspaces live inside SharePoint Embedded containers as proprietary .loop files. While IT admins can manage those containers at a basic storage level using PowerShell, the internal format of a .loop file isn't publicly documented or accessible for programmatic editing.

Because automated Loop imports aren't possible yet, most teams migrating from platforms like Quip end up choosing one of two paths:

If you must use Loop: You will have to rely on manual copy-and-pasting for your active documents. Loop actually handles pasting formatted text, links, and basic tables from the clipboard quite cleanly, so it works well for smaller sets of active docs, even though it can't be automated.
If API automation is a strict requirement: Consider migrating your Quip content into SharePoint Pages or OneNote instead. Both have mature, well-supported Microsoft Graph APIs that let you programmatically build pages with rich text, tables, and links allowing you to actually build the migration tool you have in mind.

Microsoft hasn't shared a public timeline for Loop content APIs yet, though enterprise teams ask for it frequently. To keep an eye on any upcoming developer releases, you can filter for Microsoft Loop on the Microsoft 365 Roadmap, or add your vote for API support on the Microsoft Feedback Portal to help get it on the product team's radar.

Hopefully, this saves you some time digging through the Graph documentation!

Warm regards,

If the answer is helpful, please select "Yes, accept answer". If you have any questions or new updates, please feel free to comment below.

Answer 2

Microsoft does not currently document a supported public or preview API for creating a native page in a selected Loop workspace or writing structured Loop page content; Microsoft Graph supports limited export of existing Loop files, not page authoring.

Capability status

Requirement	Current supported capability
Create a workspace or page	No documented public Loop workspace/page creation API
Add headings, rich text, tables, images, or links	No documented public API for writing Loop’s native content model
Read content for migration verification	Existing `.loop` files can be exported through Microsoft Graph as HTML or PDF, subject to access and size requirements
Import Quip documents as native pages	No documented bulk-import or document-to-native-Loop-page conversion
Upload source documents to a workspace	Supported for Word, PowerPoint, Excel, and PDF, but they remain files linked in the workspace rather than becoming native Loop pages
Developer preview	The announced private preview concerns building custom Loop components, not workspace/page CRUD

Loop workspace content is stored in SharePoint Embedded containers, but that storage implementation does not make ordinary SharePoint site, list, or page APIs into supported Loop authoring APIs. Shared workspace membership is also managed through the workspace’s SharePoint Embedded container. ^1^

Do not substitute the Graph OneNote Create page API or SharePoint list APIs: those create OneNote pages or SharePoint list items, not native Loop pages.

What can be automated: export of existing content

Microsoft Graph can convert an existing .loop drive item to:

html
pdf

The conversion endpoint has a 2 MB maximum source-file size. For content in SharePoint Embedded, the application also needs FileStorageContainer.Selected and the necessary container-type permission, in addition to the applicable Graph permissions. ^2^

For example, after obtaining an authorized drive and item ID:

GET https://graph.microsoft.com/v1.0/drives/{drive-id}/items/{item-id}/content?format=html
Authorization: Bearer {access-token}

This is useful for verifying or exporting an already-created page. It does not provide the reverse operation: posting HTML to create or update a Loop page. Microsoft’s compliance documentation describes Graph API export for third-party, migration, and eDiscovery tooling, along with guest application permissions for Loop workspace containers. ^3^

A migration tool would also need an authorized way to identify each existing drive item. There is no documented Loop API for enumerating Loop workspaces and their page hierarchy as Loop resources, so the export endpoint alone does not provide a complete migration API.

Supported fallback for the migration

The supported file-upload workflow is:

Convert each Quip document to Word or PDF.
Open the destination workspace in Loop.
Select Create new → Upload a file.
Select the Word, PowerPoint, Excel, or PDF file.

The uploaded file appears beside pages and links in workspace navigation. It is stored in the uploader’s OneDrive for Business under My files → Loop → Workspace Uploads. This does not convert its contents into a native Loop page. ^4^

Therefore, if native editable Loop pages are mandatory, the currently supported route is manual page creation and content transfer in the Loop UI. Uploading documents can preserve the source material and workspace organization, but it does not meet the native-page requirement.

Before piloting the migration, the tenant administrator should also confirm that Create Loop workspaces in Loop is enabled for the intended users; that policy governs creation of shared Loop workspaces and their SharePoint Embedded containers. ^5^

Preview and roadmap

Microsoft announced a private preview for developing Adaptive Card–based Loop components. That preview is not a general API for creating workspaces, pages, or arbitrary native page content. ^6^

No published roadmap or preview-access program in the available Microsoft material confirms broader Loop page/content CRUD APIs. A Microsoft Q&A request for programmatic workspace, page, component, and export access remains a feature request rather than API documentation. ^7^

For planning purposes, treat native Loop-page migration automation as unavailable until Microsoft publishes a Loop-specific API contract. Submit the scenario through Microsoft 365 feedback and monitor the Microsoft 365 Roadmap; avoid browser automation or direct manipulation of .loop internals because neither is a documented authoring interface.

References