# Create a spec option

A Spec can have multiple Options-- for example, if the spec is called 'Color', the options might be 'Blue', 'Red', and 'Green'.

Endpoint: POST /specs/{specID}/options
Version: 1.0.457.36910
Security: OAuth2

## Path parameters:

  - `specID` (string, required)
    ID of the spec.

## Request fields (application/json):

  - `Value` (string, required)

  - `ID` (string)

  - `ListOrder` (integer)
    Example: 1

  - `IsOpenText` (boolean)

  - `PriceMarkupType` (string)
    Enum: "NoMarkup", "AmountPerQuantity", "AmountTotal", "Percentage"

  - `PriceMarkup` (number)

  - `xp` (object)
    Example: {}

## Response 201 fields (application/json):

  - `ID` (string)

  - `Value` (string)

  - `ListOrder` (integer)
    Example: 1

  - `IsOpenText` (boolean)

  - `PriceMarkupType` (string)
    Enum: same as `PriceMarkupType` (4 values)

  - `PriceMarkup` (number)

  - `xp` (object)
    Example: {}

## Response 4XX fields (application/json):

  - `StatusCode` (integer)
    Example: "404"

  - `ErrorCode` (string)
    Example: "NotFoundError"

  - `Message` (string)
    Example: "Object not found"

  - `Data` (object)
    Example: {"ObjectType":"","ObjectID":""}