MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Shops",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "338": {
                "pageid": 338,
                "ns": 0,
                "title": "Reports",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Reports are a submission type added in [[Updating: to 2.0.0|2.0.0]] that accepts user content and bug reports into a queue. They can be viewed and processed in the admin panel by users with the '''Manage Reports''' power.\n\n==Submission==\nReports can be submitted from the report submission page. A link to this is also available on the bug report index for logged-in users, and \"report content\" buttons are present on pages with user-submitted content.\n\nA report requires:\n\n*'''URL/Title'''\n**Either a link to offending content (content report) or a short summary of the bug (bug report)\n*'''Is/Is Not Bug Report (Toggle)'''\n**Whether or not the report is for a bug. If this is on, an additional field for specifying the type of bug appears.\n*'''Error Type (if bug report)'''\n**The type of error being reported. By default, the options are: 500 error, 404 error, text error, exploit, or other error.\n*'''Comments'''\n**Optional. This space can be used to describe/describe in further detail the nature of the report. Line breaks will be preserved, but HTML will not be rendered.\n\n===Submission===\nReports submitted to the queue cannot be edited by the user. The report will have its own page containing all submitted information. A report's visibility depends on its nature; content reports will not be visible to any users besides the submitter and users with the Manage Reports power. Bug reports, however, are listed publicly in the bug report index (to prevent duplicate reports). If an exploit has been reported, however, the report will be hidden until the report is closed (and the issue presumably addressed).\n\n==Report Queue==\nUsers with the '''Manage Reports''' power can view the queue, assign themselves to reports, respond as appropriate, and close reports.\n\nThe report queue consists of lists of submissions filtered by status, ordered by newest first. Pending reports can be acted upon, while closed reports are for reference only.\n\nClicking the edit button takes the user to the report review page, where they can assign, comment on, or close the report depending on its status.\n\n===Assigning Reports===\nNewly submitted reports are \"unassigned\"; that is, there is no user assigned to handling them. Any user with the Manage Reports power can assign an unassigned report to themself. This removes the report from the main queue and places it into a special user-specific queue section that displays only the assigned reports for the currently logged-in user, the status of which is reflected on the admin index. Permissioned users may still view all current assigned reports via the queue.\n\n===Processing===\nOpen reports can be commented on by staff and user(s). This can be used to communicate with user(s) in order to facilitate addressing the subject of the report.\n\nOnce the subject of a report is resolved, it can be closed with staff notes as to any pertinent details, such as action taken. Once a report is closed, users will not be able to view comments on the report, though they will remain visible to staff, so any details that should be preserved from comments should be included in the staff notes.\n\n==Bug Report Index==\nA site's bug reports are listed publicly in its bug report index. This list shows the title of the report, when it was submitted, and its status. This list may be searched by URL or title. Logged-in users may view the details of non-exploit bug reports; exploit reports, however, are hidden until they are closed to prevent abuse.\n\n*\n\n[[Category:Documentation]]"
                    }
                ]
            },
            "330": {
                "pageid": 330,
                "ns": 0,
                "title": "Sales",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Sales are a form of text post that can be used to alert all users to on-site sales, i.e. of adoptables, added in [[Updating: to 2.0.0|2.0.0]]. They can be edited in the admin panel by users with the '''Edit Text Pages''' power.\n\n=Usage=\nSales posts can be created in the admin panel and viewed on the sales page. The sales page lists sales posts ordered by newest first. When a new post is made, all users will gain an alert at the top of every page notifying them of the new post. This alert disappears when the sales page is viewed.\n\nSales posts can be scheduled to post at certain times. Note that this posting is handled via crontab scheduling, and therefore may not be entirely accurate to the minute.\n\n=Editing=\nSales posts have the following properties:\n\n*'''Title'''\n**The title of the sales post.\n*'''Post Time'''\n**Optional. Schedules the post to be posted after a certain date/time. If not set, the sales post will be posted immediately.\n*'''Post Content''' (accepts HTML)\n**The content of the news post itself. HTML is allowed. The [[File Manager]] can be used to upload images to be inserted into sales posts if desired.\n*'''Is Open'''\n**Whether the sales post is labeled (in the title) as \"Open\" or \"Closed\". This is entirely cosmetic. If Comments Open At is set and in the future, and the post is set as open, the the sales post will be labeled \"Preview\" instead of \"Open\".\n*'''Comments Open At'''\n**Optional. A time at which comments on the post become visible to users. If this is set, comments on the post will be hidden from users without editing permissions until the set time. Users with permissions, meanwhile, can see comments and may perform any needed set-up for a sale.\n\n===Characters===\n[[Characters]] can also be attached to sales posts, allowing for easy formatting and display of per-character sale information. Characters attached to sales have the following properties:\n\n*'''Character Code'''\n**The code of the character being attached. On entering this, the rest of the fields will appear.\n*'''Sale Type & Associated Information'''\n**The type of sale/conditions under which the character is available.\n**Different fields appear depending on which sale type is selected, e.g. price for a flatsale.\n*'''Notes'''\n**Optional. Any brief notes about the character that are useful to display.\n*'''Link'''\n**Optional. A link to where the character may be bought, bid on, etc.\n*'''Is Open'''\n**Whether or not the individual character is open. Characters can be set closed independent of the sales post if it is open, but if the overall sales post is set closed, all characters attached are displayed as closed.\n\nSales posts with attached characters are divided into separate sections (header, followed by character(s), followed by the standard body of the sales post). Each attached character is displayed in its own section, with sale type and info alongside info about the character, such as species and rarity. In the interest of archival, the character's first available/visible image is used in the event that a character receives design update(s) after being sold. If there is only one character associated with a sales post, the full image rather than thumbnail is displayed as well as the character's traits.\n\n*\n\n*\n\n=See Also=\n\n*[[News]]\n*[[Site Pages]]\n*[[Characters]]\n\n[[Category:Documentation]]"
                    }
                ]
            }
        }
    }
}