Create a plan

post

/apiplatform/management/v1/plans

Creates a plan.

Users requesting this resource must be assigned the Plan Manager role.

Request

Supported Media Types
Body ()
Root Schema : CreatePlanRequest
Match All
Show Source
Nested Schema : PlanIdentity
Type: object
Show Source
Nested Schema : PlanDef
Type: object
Show Source
Nested Schema : PlanState
Type: object
Show Source
Nested Schema : CreatePlanRequest-allOf[3]
Type: object
Show Source
Nested Schema : constraints
Type: object
Describes the Plan's overview text resource.
Show Source
  • The name of the resource, if attached as a file, the URL of the resource, if added as a link, or the overview text itself, if entered as text.
  • The method used to attach overview text to the Plan. Valid values are link, file, and text.
  • The documentation type of the overview text resource. Valid values are markdown and html.
Nested Schema : overview
Type: object
Describes the Plan's overview text resource.
Show Source
  • The name of the resource, if attached as a file, the URL of the resource, if added as a link, or the overview text itself, if entered as text.
  • The method used to attach overview text to the Plan. Valid values are link, file, and text.
  • The documentation type of the overview text resource. Valid values are markdown and html.
Nested Schema : publicationSettings
Type: object
Describes the Plan's publication settings.
Show Source
Nested Schema : constraints
Type: object
Show Source
Nested Schema : description
Type: object
Show Source
Nested Schema : icon
Type: object
Show Source
Nested Schema : rate
Type: object
Show Source
Nested Schema : invocations
Type: object
Show Source
Nested Schema : PlanPublication
Type: object
Show Source
Back to Top

Response

Supported Media Types

201 Response

The plan was created.
Body ()
Root Schema : PlanId
Type: object
Show Source

400 Response

Bad request, indicates a problem with the input parameters.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source

403 Response

Forbidden.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source

500 Response

Unexpected error.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source
Back to Top

Examples

The following example shows how to create a plan by submitting a POST request on the REST resource using cURL. For more information about cURL, see Use cURL

curl -X POST 
-u apicsadmin:password
-H "Content-Type: application/json"
-d @plan.json
"https://example.com/apiplatform/management/v1/plans"

Example of Request Body

The following shows an example of the request body in JSON format (included with the request above in a file named plan.json) , including details about the new plan.

{
"name": "MyGoldplan",
"version": "v1",
"vanityName": "Gold",
 "description": "This is my gold plan",
 "state":"ACTIVE",
 "stateComments":"ACTIVE",
 "publication":{"state":"PUBLISHED","stateComments":"Published to Developer portal" }
}

Example of Response Headers

The following shows an example of the response headers.

HTTP/1.1 201 Created 
Server: Oracle-Traffic-Director/12.2.1.0.0
Date: Tue, 06 Feb 2018 08:59:30 GMT
Content-Length: 12
Content-Type: application/json
X-oracle-dms-ecid: dd439614-7d4f-47ad-a1ea-a25a74ec9403-0000032d
X-oracle-dms-rid: 0:1
Via: 1.1 otd_opc
Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0

Example of Response Body

The following example shows the contents of the response body in JSON format, including the ID of the plan you created.

{
    "id": "109"
}
Back to Top