Control tests evaluate the operating effectiveness of a control. * If your project includes one testing round, each control you create has one corresponding control test. * If your project includes multiple testing rounds, each control you create has a corresponding series of control tests. > **Note —** Only control tests in Internal Control workflow projects that have an `"active"` state can be accessed using the API. Learn more about control tests.
openapi: 3.0.2
info:
title: HighBond API Reference Actions Control tests API
version: 1.1.0
description: "\nWelcome to the API documentation for HighBond.\n\n## Introduction\nThe HighBond API is the developer interface for the HighBond platform. You can use it to automate interactions with HighBond,\nbuild reporting, and integrate HighBond with other systems in your company. This introduction contains information you should\nknow before you get started.\n\nThe HighBond API is organized around <a href=\"https://en.wikipedia.org/wiki/Representational_state_transfer\" target=\"_blank\">REST</a> and is built on the\n<a href=\"https://jsonapi.org/format/\" target=\"_blank\">JSON API v1.0 specification</a>.\n\n> **Warning —**\nThis API interacts with your company's live data. It gives you the power to delete important data that your\ncompany needs. Carefully consider the consequences of your actions when using this API. If you are not sure, contact the\nperson or group who administers HighBond in your company.\n\n### Permissions\nUsers can generate and manage API tokens in their user profiles in HighBond. Because these tokens are tied to users, not companies, your permissions in the API are the same as your permissions in HighBond.\n\n> **Note —**\nYou must be a System Admin in at least one HighBond instance to access the API.\n\nIf you leave your company and your HighBond user account is deleted, your application will break. Before getting started, consider the long-term requirements of your application. You may wish to create a system account in HighBond and build your application from that, but verify that your company's security policies permit accounts that aren't tied to particular people.\n\nHighBond uses the <a href=\"https://tools.ietf.org/html/rfc6749\" target=\"_blank\">OAuth 2.0 authorization framework</a> to control access to the API.\n\n\n### Apps\nApps are components in HighBond that provide specific functionality. You can use this API to interact with data in the apps you have access to.\n\nThe apps available to you depend on the edition of HighBond (standard or premium) in use, and whether or not your company has purchased any add-on apps.\nFor more information, see <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-product-editions\" target=\"_blank\">Subscriptions, editions, and capabilities</a>.\n\n### Rate limitations\nThe API safeguards against bursts of usage to help maximize its stability. For most endpoints, you cannot make more than 6 requests per second.\n\nThe following endpoints have a stricter rate limitation of 3 requests per minute:\n\n* Groups\n* Users\n\nTreat these limits as a maximum and avoid making unnecessary requests to the API.\n\nIf you make too many requests, the API responds with a `429` \"Too many requests\" status.\n\n## Getting started\nTo start interacting with your HighBond organization via the API, you need a few things:\n\n* An authentication token from your HighBond instance\n* The correct region URL for your HighBond instance\n* Information about the HighBond instance and resource IDs you want to interact with\n\nIf you need assistance with any of these, contact a HighBond administrator at your company, or email <a href=\"mailto:support@wegalvanize.com\">support@wegalvanize.com</a>.\n\n### Authentication\nAll requests require authentication. To authenticate, use Launchpad to create a HighBond API (bearer) token for your account. The token is a string that authenticates you\nand allows you to securely access the HighBond API.\n\nFor help creating a token, see <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-access-tokens\" target=\"_blank\">Creating and managing access tokens</a>.\n\nOnce you have created your token, you can provide it in the header of your request:\n```\nAuthorization: Bearer <TOKEN>\n```\n > **Important —**\nIf you do not authenticate yourself, the API fails. The API responds to authentication failures with a `401` \"Bad credentials\" status.\n\n<security-definitions />\n\n### Token security\nHighBond uses the <a href=\"https://tools.ietf.org/html/rfc6749#section-1.3.1\" target=\"_blank\">Authorization Code workflow</a> to generate tokens.\n\nTo enable continuous access to the API, and to provide full ownership and accountability to users, Galvanize does not impose an expiration date\non the token. You can <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-access-tokens\" target=\"_blank\">delete a token in\nLaunchpad</a> when you no longer need access to the API.\n\n> **Important —**\nYour access token provides many privileges, so keep it secure and private. Galvanize recommends that you encrypt your\nmachine to securely store the token. Avoid sharing your token in publicly accessible areas such GitHub or within client-side code.\n\n### API regions\n\nThe HighBond service is provided from different regions in order to give customers options for where your data is stored, and to enable you to\ncomply with data privacy location requirements.\n\nYour request URL must include one of the following region codes, based on where your HighBond instance resides:\n\n* **United States** — `https://apis-us.diligentoneplatform.com`\n* **Canada** — `https://apis-ca.diligentoneplatform.com`\n* **Europe** — `https://apis-eu.diligentoneplatform.com`\n* **Asia** — `https://apis-ap.diligentoneplatform.com`\n* **Australia** — `https://apis-au.diligentoneplatform.com`\n* **Africa** — `https://apis-af.diligentoneplatform.com`\n* **South America** — `https://apis-sa.diligentoneplatform.com`\n* **Japan** — `https://apis-jp.diligentoneplatform.com`\n\nAdditionally, for government clients, there are two government \"regions\":\n* **Gov** (US federal) — `https://apis.diligentoneplatform-gov.com`\n* **SLED** (state, local, and education; non-federal) — `https://apis.diligentoneplatform-gov2.com`\n\n> **Important —**\nAll API requests must be made over <a href=\"https://en.wikipedia.org/wiki/HTTPS\" target=\"_blank\">HTTPS</a>. Calls over HTTP respond with the `301` \"Moved Permanently\" status.\n\n\n### HighBond instance and resource IDs\nRequests require a HighBond instance ID and the ID of the resource you are interacting with. These IDs are numeric keys that uniquely\nidentify the HighBond instance and every resource in that instance.\n\nThe easiest way to get your HighBond instance ID is to log in to HighBond and take the ID from the URL:\n```\nhttps://accounts.highbond.com/orgs/12345\n```\n\nTo obtain IDs for resources like collections, analyses, tables, and robots, you can navigate to the item you want to reference, and take the IDs from the URL.\nFor example, this URL shows a collection ID:\n```\nhttps://example-company.results.highbond.com/projects/55843\n```\n\n> **Tip —**\nThe `GET` methods in this API also return IDs that you can use to identify resources you can act on.\n\n\n## Making requests\nOnce you have all the information you need, you can start making requests in an API client of your choice.\n\n### HTTP methods\nThe API uses the appropriate HTTP method for each action:\n* `GET` — used for retrieving resources\n* `POST` — used for creating resources\n* `PUT` / `PATCH` — used for updating resources\n* `DELETE` — used for deleting resources\n\n\n### Content type\nAlways specify the `Content-Type` of your request in the header. Supported content types are:\n* JSON API\n* JSON (for backwards compatibility)\n\n```\nContent-Type: application/vnd.api+json\nContent-Type: application/json\n```\n\nA complete **Get a table** request using `curl` would look like this:\n```\ncurl -H \"Authorization: Bearer XYZ\" -H \"Content-Type: application/vnd.api+json\" https://apis-us.highbond.com/v1/orgs/11594/tables/388930\n```\n\n### Requesting the API to return only specific fields\nFor certain resources, such as control tests, you can request the API to return only specific fields using the `fields` query parameter. Sparse fieldsets are\nhelpful for limiting your responses to only the data you require.\n\n> **Note —**\nThe `type` argument must specify the resource you want to retrieve. The value of the `fields` parameter must be a comma-delimited list that specifies\nthe name of the field(s) to be returned. Avoid whitespace before or after each comma.\n```\nfields[type]=field_name1,field_name2,fieldname3\n```\n\nA complete **Get a control test** request that only returns the `assigned_user`, `control`, and `testing_round_number` fields would look like this:\n\n```\ncurl -H \"Authorization: Bearer XYZ\" -H \"Content-Type: application/vnd.api+json\" https://apis-us.highbond.com/v1/orgs/12345/control_tests/105?fields[control_tests]=assigned_user,control,testing_round_number\n```\n\n### Requesting the API to return related resources\nTo reduce the number of requests, you may use the `include` query parameter to return related resources in the response along with the requested primary resources. Such responses are called \"compound documents\".\n\nAccepted values for the `include` parameter are documented in the `Query Parameters` section of each API method.\n\n> **Note —**\nThe `include` parameter must be a comma-delimited list that specifies\nthe name of the relationship(s) or nested relationship(s) to be returned. Avoid whitespace before or after each comma.\n\nExample - requesting a relationship and a nested relationship\n```\ninclude=control,control.objective\n```\n\nA complete **Get a control test** request that returns the `control` relationship, and `control.objective` nested relationship would look like this:\n\n```\ncurl -H \"Authorization: Bearer XYZ\" -H \"Content-Type: application/vnd.api+json\" https://apis.highbond.com/v1/orgs/12345/control_tests/105?include=control,control.objective\n```\n\n\n### Blank fields\nBlank fields are included in all response schemas as `\"\"` or `null` instead of being omitted.\n\n\n### Time zones\nAll timestamps are returned in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.\n\nSome requests that create new data, such as creating a robot task's schedule, allow you to provide time zone information.\nFor API requests that allow for a timestamp to be specified, you must explicitly provide an ISO 8601 timestamp with time zone information.\n\n```\n\"starts_at\": \"2019-03-21T16:25:00.478Z\",\n\"starts_at_timezone\": \"America/Los_Angeles\",\n```\n\n\n### Rich text fields\n\nSome requests and responses contain rich text fields that include HTML tags. These are typically description fields. If you need to format text,\nthe best approach is to upload your raw data first and apply formatting later in the user interface.\n\n> **Note —**\nImages that exist in rich text fields are returned in responses, but they are not rendered. You cannot upload new images to rich text fields using the API.\n\n\n### User identifiers\nA unique identifier (UID) is an alphanumeric string that is associated with a user in HighBond. UIDs make it possible to address users,\nso that they can be accessed and interacted with using the API. Some requests that allow you to assign items to users, such as creating an objective,\nrequire you to specify a user's UID.\n\nTo obtain a user's UID:\n\n1. Sign in to <a href=\"https://accounts.highbond.com/login\" target=\"_blank\">HighBond</a>.\n2. If your company uses more than one instance in HighBond, make sure <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-switch-instances\"\ntarget=\"_blank\">the appropriate instance is active</a>.\n3. Select **Options > Users (#)**.\n4. Navigate to the appropriate user and click the user's name.\n5. In the **User Details** side panel, copy the UID to your clipboard.\nOnce you have copied the UID, you can specify it in your request.\n\n\n### Pagination\nWhen a response consists of a large number of items, the API breaks it into separate pages for performance reasons. You can control the way the API paginates your results by specifying how many items you want to have per page, and which page you want the API to return.\n\nFor example, if you request a list of controls, the request could look like this: `{protocol}://{server}/v1/orgs/{org_id}/objectives/{objective_id}/controls?page[size]=25&page[number]=Mg==`\n\nWhere:\n\n* `page[size]=25` specifies that there should be 25 items per page. Different endpoints have different default values and maximum numbers of values you can have per page.\n* `page[number]=Mg==` specifies that the API should return the second page of results (the 26th through 50th items that match the request).\n\n > **Note —**\n In most cases, page numbers must be encoded in Base64. In this example, `Mg==` is the Base64 encoded value for `2`.\n\nAdditionally, responses include the `links` parameter, which provides URLs for the `prev` and `next` attributes (or `null` values if all of the items are on one page). Those URLs include the above parameters, so you can paste them into subsequent requests if needed.\n\n\n\n## Errors\nHighBond uses standard <a href=\"https://en.wikipedia.org/wiki/List_of_HTTP_status_codes\" target=\"_blank\">HTTP response codes</a>\nto indicate the success or failure of a request. The range of a code indicates information about why it succeeded or failed:\n\n* **`2xx` range —** Success\n* **`4xx` range —** Error given the information provided\n* **`5xx` range —** Server failed to fulfil a valid request\n\nSome common errors that occur when making requests include:\n* **`400` Bad request —** When a parameter is missing (such as the `org_id` or resource `id`), when more\nthan one unique resource is specified in the request, or when a specified data type is incompatible with the endpoint\n* **`401` Bad credentials —** When there is an authentication error\n* **`403` Forbidden —** When there is an authorization problem based on your <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-managing-apps\"\ntarget=\"_blank\">role in a HighBond app</a> or <a href=\"https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=lp-assigning-subscriptions\" target=\"_blank\">subscription</a>\n* **`404` Not found —** When there is a problem on the client side due to an incorrect URL or resource deletion\n* **`415` Unsupported media type —** When the `Content-Type` specified is unsupported\n* **`422` Unprocessable entity —** When a required attribute is missing (such as the name of a resource), or when a conflict occurs\n(such as a script activation conflict)\n\n\n## Versioning\nAll API endpoints use a version number in the path. As can be seen in the examples, `/v1/` specifies version 1 of the API.\n\nOver time, the API will evolve. New API versions will be introduced and existing versions may be updated.\n\nSome API updates are considered a breaking change, requiring a new version of the API to be introduced. An example of a breaking\nchange is fields being changed or removed. By introducing a new version, API consumers can safely continue to use prior API versions.\n\nThe other type of API update is a non-breaking change. You should expect non-breaking change updates to existing API versions.\nAn example of a non-breaking change is adding a field to a response object. Non-breaking changes are additive. While they do\nchange the response body, they should not impact the API consumer.\n"
x-logo:
url: ./assets/logo.png
altText: HighBond Logo
servers:
- url: '{protocol}://{server}/v1'
variables:
protocol:
default: https
server:
default: apis-us.highbond.com
enum:
- apis-us.highbond.com
- apis-ca.highbond.com
- apis-eu.highbond.com
- apis-ap.highbond.com
- apis-au.highbond.com
- apis-af.highbond.com
- apis-sa.highbond.com
- apis-jp.highbond.com
security:
- bearerToken: []
tags:
- name: Control tests
description: 'Control tests evaluate the operating effectiveness of a control.
* If your project includes one testing round, each control you create has one corresponding control test.
* If your project includes multiple testing rounds, each control you create has a corresponding series of control tests.
> **Note —**
Only control tests in Internal Control workflow projects that have an `"active"` state can be accessed using the API.
<a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-tests-walkthroughs" target="_blank">Learn more about control tests</a>.
'
paths:
/orgs/{org_id}/control_tests:
get:
tags:
- Control tests
operationId: getControlTests
summary: Get organization control tests
description: 'Get a list of all of the control tests in an organization.
> **Note:**
By default, this endpoint only returns control tests from active projects. To fetch objects from archived projects or frameworks, do one of the following:
> * Specify the project or framework ID using `filter[project.id]`
> * Specify that you want results from archived projects using `filter[project.state]=archive`
> * Specify that you want results from frameworks using `filter[project.state]=framework`
'
parameters:
- $ref: '#/components/parameters/orgIdParam'
- $ref: '#/components/parameters/controlTestsSparseFieldsetParams'
- $ref: '#/components/parameters/pageSizeParam'
- $ref: '#/components/parameters/pageNumberEncodedParam'
- $ref: '#/components/parameters/controlTestsSortParams'
- $ref: '#/components/parameters/controlTestProjectIdFilterParams'
- $ref: '#/components/parameters/controlTestProjectNameFilterParams'
- $ref: '#/components/parameters/controlTestProjectStateFilterParams'
- $ref: '#/components/parameters/controlTestControlIDFilterParams'
- $ref: '#/components/parameters/controlTestProjectStatusFilterParams'
- $ref: '#/components/parameters/controlTestObjectiveTitleFilterParams'
- $ref: '#/components/parameters/controlTestObjectiveReferenceFilterParams'
- $ref: '#/components/parameters/controlTestControlStatusFilterParams'
- $ref: '#/components/parameters/controlTestControlTitleFilterParams'
- $ref: '#/components/parameters/controlTestControlQueryFilterParams'
- $ref: '#/components/parameters/controlTestControlOwnerFilterParams'
- $ref: '#/components/parameters/controlTestControlFrequencyFilterParams'
- $ref: '#/components/parameters/controlTestControlTypeFilterParams'
- $ref: '#/components/parameters/controlTestControlNumberFilterParams'
- $ref: '#/components/parameters/controlTestControlControlTestFirstAssigneeFilterParams'
- $ref: '#/components/parameters/controlTestControlControlTestSecondAssigneeFilterParams'
- $ref: '#/components/parameters/controlTestControlControlTestThirdAssigneeFilterParams'
- $ref: '#/components/parameters/controlTestControlControlTestFourthAssigneeFilterParams'
- $ref: '#/components/parameters/controlTestIncludeParams'
- $ref: '#/components/parameters/controlSparseFieldsetParams'
- $ref: '#/components/parameters/objectiveSparseFieldsetParams'
responses:
'200':
description: OK.
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/GetControlTestsResponse'
'400':
$ref: '#/components/responses/MissingResourceId'
'401':
$ref: '#/components/responses/BadCredentials'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'415':
$ref: '#/components/responses/NotJsonapiMediaType'
/orgs/{org_id}/control_tests/{id}:
get:
tags:
- Control tests
operationId: getControlTest
summary: Get a control test
description: Get information about a control test in a project.
parameters:
- $ref: '#/components/parameters/orgIdParam'
- $ref: '#/components/parameters/resourceIdParam'
- $ref: '#/components/parameters/controlTestSparseFieldsetParams'
- $ref: '#/components/parameters/controlTestIncludeParams'
responses:
'200':
description: OK.
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/GetControlTestResponse'
'400':
$ref: '#/components/responses/MissingResourceId'
'401':
$ref: '#/components/responses/BadCredentials'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'415':
$ref: '#/components/responses/NotJsonapiMediaType'
patch:
tags:
- Control tests
operationId: updateControlTest
summary: Update a control test
description: '> **Deprecation notice —**
Please note that `testing_conclusion` field will be deprecated. Consider using new `testing_conclusion_status` field instead.
Make changes to a control test in a project, like updating the testing results or conclusion.
<strong>Limitations</strong>:
* You cannot update the control test if it is signed off or if the objective it belongs to has been checked out using
<a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-offline-client" target="_blank">Offline Projects</a> or the
<a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-mobile" target="_blank">HighBond iPad app</a>.
* You cannot update the `testing_conclusion_status` and `testing_conclusion` field if the field is automated using an
<a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-automate-control-assessments" target="_blank">assessment driver</a>.
'
parameters:
- $ref: '#/components/parameters/orgIdParam'
- $ref: '#/components/parameters/resourceIdParam'
- $ref: '#/components/parameters/controlTestSparseFieldsetParams'
- $ref: '#/components/parameters/controlTestIncludeParams'
requestBody:
description: The data required to update a control test.
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/UpdateControlTestRequest'
responses:
'200':
description: OK.
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/GetControlTestResponse'
'400':
$ref: '#/components/responses/MissingResourceId'
'401':
$ref: '#/components/responses/BadCredentials'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'415':
$ref: '#/components/responses/NotJsonapiMediaType'
'422':
description: 'Unprocessable entity.
'
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- status: 422
source:
pointer: /data/attributes/not_applicable
code: invalid_resource
detail: can't be blank
components:
schemas:
GetControlTestsResponse:
type: object
required:
- data
- links
properties:
data:
type: array
items:
type: object
description: The data associated with the resource.
required:
- id
- type
- relationships
properties:
id:
type: string
description: The ID of the requested resource.
example: 1
type:
type: string
description: The classification of the object (`"control_tests"`).
example: control_tests
attributes:
type: object
description: The attributes associated with the resource.
properties:
assignee_name:
type: string
description: The name of the person to whom the issue was assigned.
example: Payam Moghaddam
testing_round_number:
type: integer
description: 'The specific testing round `(1-4)` that the control test belongs to. A control may have 0, 1, 2, or 4 testing rounds, depending upon the
`number_of_testing_rounds` <a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-update-project-settings" target="_blank">
defined in the project settings</a>.
The names for testing rounds are customizable and depend on the <a href="
https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-customize-terms" target="_blank">configuration of the project type</a>.
**Examples**
1 testing round =
**"Testing"** (`1`)
2 testing rounds =
**"Interim"** (`1`), **"Final"** (`2`)
4 testing rounds =
**"Q1"** (`1`), **"Q2"** (`2`), **"Q3"** (`3`), **"Q4"** (`4`)
'
example: 1
format: int64
created_at:
type: string
description: The timestamp identifying when the control test was created.
example: '2019-02-09T13:17:26Z'
format: date-time
updated_at:
type: string
description: The timestamp identifying when the control test was updated.
example: '2019-02-09T13:17:26Z'
format: date-time
actual_milestone_date:
type: string
nullable: true
description: Actual milestone date.
example: '2019-02-10'
format: date
planned_milestone_date:
type: string
nullable: true
description: Planned milestone date.
example: '2019-02-09'
format: date
not_applicable:
type: boolean
description: '`false` specifies that the control test is applicable to the testing round. `true` specifies that the control test
is not applicable to the testing round. Only applicable control tests are included in
<a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-risk-assurance" target="_blank">assurance calculations</a>.
'
example: false
sample_size:
type: integer
description: 'The total sample size, split among testing rounds. `sample_size` must be a value between `0` and `2147483647`.
Sample size is set when a
test plan is created the first time, which occurs when you create a control. The logic used to automatically set the sample size field is
based on two control attribute fields: `frequency` and `type`. For more information, see <a href="
https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-tests-walkthroughs" target="_blank">Executing procedures and testing
controls</a>.
'
example: 24
format: int64
nullable: true
testing_results:
type: string
description: 'A detailed evaluation that describes whether or not the control is operating effectively.
'
maxLength: 524288
example: <h1>Heading</h1><p>Testing results description.</p>
testing_conclusion:
type: boolean
description: 'A rating that specifies whether the control passes (`true`) or fails (`false`).
The exact values for this field (E.g. "Operating Effectively" and "Exception(s) Noted") depend on the <a href="
https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-customize-terms" target="_blank">configuration of the project type</a>.
`true` maps to the first customizable value (E.g. "Operating Effectively") and `false` maps to the second customizable value (E.g.
"Exception(s) Noted") in the project type.
'
example: true
nullable: true
testing_conclusion_status:
type: string
description: The control rating choice.
example: Operating Effectively
nullable: true
custom_attributes:
type: array
description: An array of custom attributes defined on the project type used by the project this control test is from. <a href="https://help.highbond.com/helpdocs/highbond/en-us/Default.htm#cshid=pm-project-types" target="_blank">Learn more about project types</a>. Make a PATCH request to modify the value of a custom attribute.
items:
type: object
description: A user defined custom attribute value.
properties:
id:
type: string
description: The ID of this custom attribute. Optional if term is included.
example: '42'
term:
type: string
description: The user defined term used to identify this custom attribute. Optional if id is included.
example: Custom Control Test Attribute
value:
type: array
description: The value or values (for multiselect) for this custom attribute.
example:
- Custom Select Option Text
items:
type: string
relationships:
type: object
description: The relationships associated with the resource.
required:
- control
properties:
control:
type: object
description: The attributes associated with the resource.
required:
- data
properties:
data:
type: object
description: The data associated with the resource.
required:
- id
- type
properties:
id:
type: string
description: The ID of the control.
example: '1'
type:
type: string
description: The classification of the object (`"controls"`).
example: controls
assigned_user:
type: object
nullable: true
description: 'The person assigned to the control test. Only users assigned the Professional Manager, Professional User, or Contributor Tester role in the project
can be specified. The user specified receives an email notification with a link to the control test, and has full read and write access to the control
test.
To return this field, you must specify the `fields[control_tests]=assigned_user` parameter in your request. For more information, see
<a href="#section/Making-requests">Making requests</a>.
# --- truncated at 32 KB (68 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/wegalvanize/refs/heads/main/openapi/wegalvanize-control-tests-api-openapi.yml