• Get Review Board
  • What's New
  • Products
  • Review Board Code review, image review, and document review
  • Documentation
  • Release Notes
  • Power Pack Enterprise integrations, reports, and enhanced document review
  • Try for 60 Days
  • Purchase
  • RBCommons Review Board as a Service, hosted by us
  • Pricing
  • RBTools Command line tools and Python API for Review Board
  • Documentation
  • Release Notes
  • Review Bot Automated code review, connecting tools you already use
  • Documentation
  • Release Notes
  • RB Gateway Manage Git and Mercurial repositories in your network
  • Documentation
  • Release Notes
  • Learn and Explore
  • What is Code Review?
  • Documentation
  • Frequently Asked Questions
  • Support Options
  • Third-Party Integrations
  • Demo
  • Review Board RBTools Power Pack Review Bot Djblets RB Gateway
    1. RBTools 0.7
    2. Version 5.x
    3. Version 4.x
    4. Version 3.x
    5. Version 2.0
    6. Version 1.0
    7. Version 0.7
    8. Version 0.6
    9. Version 0.5
    10. rbt
    11. Commands
    12. api-get
  • Home
  • rbt
  • Configuration
  • Repository Configuration
  • Per-User Configuration
  • Team Foundation Server Configuration
  • Commands
  • api-get
  • attach
  • clear-cache
  • close
  • diff
  • land
  • list-repo-types
  • login
  • logout
  • patch
  • post
  • publish
  • setup-repo
  • stamp
  • status
  • RBTools Python API
  • Overview of the Python API Client
  • Tutorial
  • Resource-Specific Functionality
  • Glossary
  • General Index
  • Release Notes
  • This documentation covers RBTools 0.7. You can select a version above or view the latest documentation.

    api-get¶

    rbt api-get will request the API resource found at the provided <path> and display it as JSON.

    Paths will be appended to the root of the API to generate a URL. For example, the /review-requests/123/ path would result in a request to http://example.com/api/review-requests/123/.

    The path may also be replaced by a full URL. If rbt api-get detects the path begins with http:// or https://, it will treat the path itself as the request URL.

    Query arguments may also be specified for the request. Each query argument takes the form of --<query-arg>=<value>. For example:

    $ # Make a request to http://example.com/api/review-requests/?counts-only=1
    $ rbt api-get /review-requests/ --counts-only=1
    

    Usage¶

    $ rbt api-get [options] <path> [--<query-arg>=<value> ...]
    

    Options¶

    --pretty¶

    Pretty prints the resulting API payload.

    The default can be set in API_GET_PRETTY_PRINT in .reviewboardrc.

    -d, --debug¶

    Displays debug output.

    This information can be valuable when debugging problems running the command.

    The default can be set in DEBUG in .reviewboardrc.

    Review Board Server Options¶

    Options necessary to communicate and authenticate with a Review Board server.

    --server <url>¶

    Specifies the Review Board server to use.

    The default can be set in REVIEWBOARD_URL in .reviewboardrc.

    --username <username>¶

    The user name to be supplied to the Review Board server.

    The default can be set in USERNAME in .reviewboardrc.

    --password <password>¶

    The password to be supplied to the Review Board server.

    The default can be set in PASSWORD in .reviewboardrc.

    --ext-auth-cookies <ext auth cookies>¶

    Use an external cookie store with pre-fetched authentication data. This is useful with servers that require extra web authentication to access Review Board, e.g. on single sign-on enabled sites.

    The default can be set in EXT_AUTH_COOKIES in .reviewboardrc.

    New in version 0.7.5.

    --api-token <token>¶

    The API token to use for authentication, instead of using a username and password.

    The default can be set in API_TOKEN in .reviewboardrc.

    New in version 0.7.

    --disable-proxy¶

    Prevents requests from going through a proxy server.

    The default can be set in ENABLE_PROXY in .reviewboardrc.

    --disable-ssl-verification¶

    Disable SSL certificate verification. This is useful with servers that have self-signed certificates.

    The default can be set in DISABLE_SSL_VERIFICATION in .reviewboardrc.

    New in version 0.7.3.

    --disable-cookie-storage¶

    Use an in-memory cookie store instead of writing them to a file. No credentials will be saved or loaded.

    The default can be set in SAVE_COOKIES in .reviewboardrc.

    New in version 0.7.3.

    --disable-cache¶

    Disable the HTTP cache completely. This will result in slower requests.

    The default can be set in DISABLE_CACHE in .reviewboardrc.

    New in version 0.7.3.

    --disable-cache-storage¶

    Disable storing the API cache on the filesystem, instead keeping it in memory temporarily.

    The default can be set in IN_MEMORY_CACHE in .reviewboardrc.

    New in version 0.7.3.

    --cache-location <file>¶

    The file to use for the API cache database.

    The default can be set in CACHE_LOCATION in .reviewboardrc.

    New in version 0.7.3.

    Keep up with the latest Review Board releases, security updates, and helpful information.

    About
    News
    Demo
    RBCommons Hosting
    Integrations
    Happy Users
    Support Options
    Documentation
    FAQ
    User Manual
    RBTools
    Administration Guide
    Power Pack
    Release Notes
    Downloads
    Review Board
    RBTools
    Djblets
    Power Pack
    Package Store
    PGP Signatures
    Contributing
    Bug Tracker
    Submit Patches
    Development Setup
    Wiki
    Follow Us
    Mailing Lists
    Reddit
    Twitter
    Mastodon
    Facebook
    YouTube

    Copyright © 2006-2025 Beanbag, Inc. All rights reserved.

    Terms of Service — Privacy Policy — AI Ethics Policy — Branding

    On this page

    • [Top]
    • Usage
    • Options
      • Review Board Server Options