Visualize Plutora’s API With Swagger

Swagger provides users with interactive documentation so they can visualize and test the API of the various modules of Plutora.

The following API enhancements will soon be added:

  • POST /systems/{id}/stakeholders
  • PUT /systems/{id}/stakeholders/{userId}

Swagger can be used with or without a token:

  • Without a token: Users can view code samples.
  • With a token: Users can view code samples and also use the API.

You can also download the Plutora REST API Primer v1.4.1 and sample scripts.

Swagger aug 22 2017

To use Swagger with a token:

To enable API:

  1. Go to Settings > Customization.
  2. Click API.
  3. Click to select the Enabled checkbox.
  4. Click Generate New Client Credentials.
  5. Copy and save the client_ID and client_secret.
    API Customization with arrows

Administrators need the Enable/Disable APIs user permission to enable Plutora Test’s API and generate new API keys.

To enable the API of Plutora Test (Stryka) and generate API keys:

  1. Click Settings.
  2. Click the Integrations tab.
  3. Click API.
    Plutora Test API Sept 8 2017
  4. Click to select the Toggle to enable/disable API access checkbox. The API Status will change to Enabled.
  5. Click Generate New API Keys.
  6. Copy and save the API Client ID and API Client Secret.


If you haven’t already, download and install Google Chrome browser.

To download and install the Google Chrome Postman extension:

  1. Open Google Chrome browser.
  2. Go to
  3. Click Chrome App.
  4. Click Add to Chrome.
  5. Click Add App.
    Postman extension will appear under your Google Chrome Apps tab. Google Chrome Apps tab
    Google Chrome Apps tab arrow pointing to Postman

To use Google Chrome Postman to retrieve a token from the authorization server:

  1. Open Google Chrome browser and go to:
  2. Click Postman.
    Postman app
  3. Select Post from the Get drop down menu.
    Postman opening screen with arrow
  4. Select OAuth 2.0 from the Type drop down menu under the Authorization tab.
    Postman type drop down menu with arrow
    Plutora API does not allow No Auth. 
  5. Type the Request URL into the Enter request URL field.Enter request URL with arrow
    The Request URL for all of Plutora’s modules (including Stryka or Plutora Test) is:
    https://[Country code: us, uk, au]
    For example, US customers would type:
  6. Click the Body tab.
    Body tab with arrow
  7. Click to select the x-www-form-urlencoded radio button.
    Body tab and x-www-form-urlencoded radio button with arrow
  8. Click the Key field and type client_id.
    Key field with arrow
  9. Click the Value field and paste in the client_id generated in step 1.
    Value field with arrow
  10. Continue until you have added all the keys and values in the table below.
Key Value
client_id Paste the client_id generated from Plutora or Plutora Test (Stryka).
client_secret Paste the client_secret generated from Plutora or Plutora Test (Stryka).
grant_type Type “password”. (The actual word “password”, not your Plutora password.)
username Type the email address you use to log into Plutora or Plutora Test (Stryka).
password Type the password you use to log into Plutora or Plutora Test (Stryka).

Your screen should look like this:
Full table of values

  1. Click Send.
    After a few seconds of loading, the access token should appear.
    If using credentials from Plutora Test (Stryka) you may need to click Send a second time.

    Access token with arrows
  2. Copy and save the access token without the double quotes.

To add the token to Swagger:

  1. Open your country’s API in your browser:
  2. Type “bearer [[token]]” where [[token]] is the token you just obtained from Postman, minus the [[]].
    Bearer token location red rectangle
  3. Click Explore.

Test Swagger by bringing up a Change from its ID:

  1. Get the Change ID:
    1. Click GET /changes.
    2. Select application/json from the Response Content Type drop down menu (if it hasn’t been select already).
    3. Click Try it out!
    4. Select and copy a Change ID.
      Select and copy a Change ID
  2. Bring up the Change by its ID:
    1. Click GET /changes/{id}.
    2. Select application/json from the Response Content Type drop down menu (if it hasn’t been selected already).
    3. Paste the Change ID into Value.
      Get Changes ID Swagger
    4. Click Try it out!
      Change ID result

Test Swagger by bringing up a Defect from its ID and updating its Name and Description:

  1. Get the Defect ID:
    1. Click Defects.
      Get Defects Swagger
    2. Click POST /defects/Search.
    3. Select application/json from the Response Content Type drop down menu (if it hasn’t been selected already).
      Swagger defects search
    4. Paste the following code into filter.
      This code will bring up a page containing 25 Defects.

    5. Click Try it out!
    6. Copy a Defect ID.
  2. Change the name and description of the Defect:
    1. Click PATCH /defects/{id}.
    2. Paste the Defect ID into the id field.
      Patch defect id
    3. Paste the following code into the defectDelta field.
      This code will change the Defect’s Title to Swagger Example 111 and its Description to “This description was changed with the help of Swagger.” 

      "Name": "Swagger Example 111",
      "Description":"This description was changed with the help of Swagger."
    4. Click Try it out!

For POST /releases the following business logic applies:

  • The Implementation Date can be in the past, present, or future.
  • The Release Status must not be in an End State.
  • Project and Independent Releases, but not Enterprise Releases, can be POSTed to.

Back to the top arrow

Was this article helpful?

4 found this helpful.