1
Feature request: API endpoint to import historical revisions
Source: outline/outline#11892 · opened by @mcdamo
The ZIP import works well for a once-off wiki import but it lacks the ability to import revisions.
Using the API it could be possible to import an entire wiki including all revisions. Initially I tried the existing endpoint documents.update but discovered two problems:
1. it does not have a method to set a historical date for the update (related #11416)
2. the revisions are 'debounced' by the system after import, and so end up as a single revision.
The feature I propose is a new endpoint revisions.create:
• it accepts the same API fields as documents.update
• it does not do any publish actions
• it does not run any debounce based on revision creation time
Using the API it could be possible to import an entire wiki including all revisions. Initially I tried the existing endpoint documents.update but discovered two problems:
1. it does not have a method to set a historical date for the update (related #11416)
2. the revisions are 'debounced' by the system after import, and so end up as a single revision.
The feature I propose is a new endpoint revisions.create:
• it accepts the same API fields as documents.update
• it does not do any publish actions
• it does not run any debounce based on revision creation time
No pledges yet. Be the first to back this.
Comments
Similar requests
Visualize diff between revisions
14 votes · 0 comments
Proposal: Implementing API Versioning in Outline
1 vote · 0 comments
Compare any two revisions (not just adjacent ones)
1 vote · 0 comments
Per-endpoint rate limits are too restrictive for AI agent workflows and not configurable
2 votes · 0 comments
Feature Request: Native API Documentation Viewer for Swagger/OpenAPI (Redocly-like)
1 vote · 0 comments
No comments yet.