ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Export a complete dataset from a GitBook space using the Content API, choosing between the standard list endpoints (pages, revisions) and the search endpoint for discovery. Constraints and uncertainty List endpoints accept page and limit parameters and return pagination metadata with a next-page marker. The search endpoint accepts a limit parameter but
I am building an export job that walks all pages in a large Confluence space using GET /rest/api/content with the start and limit parameters. The space contains tens of thousands of pages, and I need to know when I have genuinely reached the end of the dataset. My plan is to loop, incrementing start by limit each call, and stop when the returned page is shor
Goal Determine whether a retried Sulu content write can succeed after an optimistic-locking conflict without creating duplicate entries. Constraints Sulu content nodes use optimistic locking through a version column. A version mismatch produces a 409 Conflict response from the API layer. It is unclear whether the platform provides a built-in idempotency key
gitbook