# 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

## Security:

  - `OAuth2` (unknown)
    oauth2 scopes: FullAccess, ProductAdmin

## Path parameters:

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

## Request fields (application/json):

  - `ID` (string)

  - `Value` (string)

  - `ListOrder` (integer)

  - `IsOpenText` (boolean)

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

  - `PriceMarkup` (number)

  - `xp` (object)

## Response 201:

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

## Response 201 fields (application/json):

  - `ID` (string)

  - `Value` (string)

  - `ListOrder` (integer)

  - `IsOpenText` (boolean)

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

  - `PriceMarkup` (number)

  - `xp` (object)

## Response 4XX:

  - `4XX` (unknown)
    Expected errors range from 400-409. Anything in the 5XX range indicates a server issue and should be reported to support.

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

  - `StatusCode` (integer)
    Example: 404

  - `ErrorCode` (string)
    Example: NotFoundError

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

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