List all drafts.
curl -i -X GET \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts?page_size=0&page_token=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "drafts": [ { … } ], "next_page_token": "string", "show_deleted": true }
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
curl -i -X POST \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts?draft_id=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"creator_team": "string",
"broker_team": "string",
"assignee_team": "string",
"input": {},
"annotations": {
"property1": "string",
"property2": "string"
}
}'
OK
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
{ "name": "string", "uid": "string", "creator_team": "string", "broker_team": "string", "assignee_team": "string", "input": {}, "create_time": "2019-08-24T14:15:22Z", "update_time": "2019-08-24T14:15:22Z", "delete_time": "2019-08-24T14:15:22Z", "etag": "string", "annotations": { "property1": "string", "property2": "string" } }
curl -i -X GET \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts/{draft}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
OK
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
{ "name": "string", "uid": "string", "creator_team": "string", "broker_team": "string", "assignee_team": "string", "input": {}, "create_time": "2019-08-24T14:15:22Z", "update_time": "2019-08-24T14:15:22Z", "delete_time": "2019-08-24T14:15:22Z", "etag": "string", "annotations": { "property1": "string", "property2": "string" } }
curl -i -X DELETE \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts/{draft}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
curl -i -X PATCH \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts/{draft}?allow_missing=true&update_mask=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"creator_team": "string",
"broker_team": "string",
"assignee_team": "string",
"input": {},
"annotations": {
"property1": "string",
"property2": "string"
}
}'
OK
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
{ "name": "string", "uid": "string", "creator_team": "string", "broker_team": "string", "assignee_team": "string", "input": {}, "create_time": "2019-08-24T14:15:22Z", "update_time": "2019-08-24T14:15:22Z", "delete_time": "2019-08-24T14:15:22Z", "etag": "string", "annotations": { "property1": "string", "property2": "string" } }
Required. The resource name of the draft to publish.
Format: scenarios/{scenario}/drafts/{draft}
curl -i -X POST \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts/{draft}:publish?etag=string&name=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json'
{ "rfi": { "name": "string", "uid": "string", "creator_team": "string", "broker_team": "string", "current_assignee_team": "string", "initial_assignee_team": "string", "input": {}, "create_time": "2019-08-24T14:15:22Z", "update_time": "2019-08-24T14:15:22Z", "expire_time": "2019-08-24T14:15:22Z", "state": "STATE_UNSPECIFIED", "questions": { … }, "display_metadata": { … }, "annotations": { … }, "etag": "string" } }
Required. The resource name of the deleted draft.
Format: scenarios/{scenario}/drafts/{draft}
curl -i -X POST \
'https://rfi.bndry.xyz/_mock/apis/openapi/request/v1alpha/scenarios/{scenario}/drafts/{draft}:undelete' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"etag": "string"
}'
OK
The resource name of the team that will create or initiate the RFI.
Format: teams/{team}
The resource name of the team that will facilitate or coordinate the RFI process.
Format: teams/{team}
The resource name of the team that will become the initial assignee of the RFI.
Format: teams/{team}
Input data that will be used to create the RFI.
This field should contain JSON that matches the scenario's input schema.
Unstructured key-value pairs that can be used to store and retrieve arbitrary metadata related to the draft.
Annotations are intended for client-side usage. They are not used by the server except for size or character set validation as defined in AIP-148
{ "name": "string", "uid": "string", "creator_team": "string", "broker_team": "string", "assignee_team": "string", "input": {}, "create_time": "2019-08-24T14:15:22Z", "update_time": "2019-08-24T14:15:22Z", "delete_time": "2019-08-24T14:15:22Z", "etag": "string", "annotations": { "property1": "string", "property2": "string" } }