v1

latestOpenAPI 3.0.22026-07-13111437.5 KB
provisioning

Adds a new Portfolio

Adds a new Portfolio to be provisioned, including Task Orders and Operators. Once provisioned, Operators can log in to the CSP and begin using provisioned resources and services, funded by the provided Task Order(s). Note that invitations should be sent to all Operator email addresses included in the request. See #/info/description and #/components/schemas for details of these constructs.

post/portfolios

Request body

idstring required

Represents the unqiue ID of the Portfolio created by the vendor. In order to enable the ATAT UI to construct links back to the provisioned environment, this should be the same ID generated internally for the vendor's Portfolio-equivalent construct.

namestring required

Example request

{
  "id": "csp-portfolio-id-123",
  "name": "Sample Portfolio name",
  "task_orders": [
    {
      "id": "csp-task-order-id-123",
      "task_order_number": "HQ003421F0024",
      "clins": [
        {
          "pop_start_date": "2021-07-22",
          "pop_end_date": "2026-07-21"
        }
      ],
      "pop_start_date": "2021-07-15",
      "pop_end_date": "2026-07-14"
    }
  ]
}

Response

Portfolio response object

idstring required

Represents the unqiue ID of the Portfolio created by the vendor. In order to enable the ATAT UI to construct links back to the provisioned environment, this should be the same ID generated internally for the vendor's Portfolio-equivalent construct.

namestring required

Example response

{
  "id": "csp-portfolio-id-123",
  "name": "Sample Portfolio name",
  "task_orders": [
    {
      "id": "csp-task-order-id-123",
      "task_order_number": "HQ003421F0024",
      "clins": [
        {
          "pop_start_date": "2021-07-22",
          "pop_end_date": "2026-07-21"
        }
      ],
      "pop_start_date": "2021-07-15",
      "pop_end_date": "2026-07-14"
    }
  ]
}
All 11 operations