# Creation of discussion posts

Allows the creation of multiple discussion posts at once. The limit of items per request is defined to 100.


Discussions can be created for: products, articles, and pages. Requires "discussion" module to be active.


Request is processing all the items. If there are some errors in item definitions, only these items are skipped and summarized in response errors. Valid items are processed even if some error items are skipped.


If at least one item is processed successfully, the response code is 201. If all the items contain errors, the response code is 400. If basic validation of items fails, the response code is 422 and the request is not processed.

Endpoint: POST /api/discussions-posts
Version: 1.0.0
Security: shoptetAccessToken, shoptetPrivateApiToken

## Header parameters:

  - `Content-Type` (string, required)

## Request fields (application/json):

  - `data` (array, required)

  - `data.parentId` (integer,null)
    Discussion post parent identifier.

  - `data.productGuid` (any)
    Discussion post product identifier.

  - `data.articleId` (integer,null)
    Discussion post article identifier.

  - `data.pageId` (integer,null)
    Discussion post page identifier.

  - `data.customerGuid` (any)
    Discussion post customer identifier.

  - `data.name` (string,null)
    Name of the author.

  - `data.email` (string, required)
    Email of the author.

  - `data.title` (string,null)
    Title of the post.

  - `data.content` (string, required)
    Content of the post.

  - `data.creationDate` (string,null)
    Date and time of the post creation. If not provided, current date and time is used.

  - `data.authorized` (boolean, required)
    Flag whether the post is authorized (visible on the web).

## Response 201 fields (application/json):

  - `data` (object,null)

  - `errors` (array,null)

  - `errors.errorCode` (string, required)
    Short text error identification

  - `errors.message` (string, required)
    Descriptive error message

  - `errors.instance` (string, required)
    Identification of the entity referenced

  - `metadata` (object)

  - `metadata.requestId` (string, required)
    Request identifier. Useful for logging/reporting purposes.

## Response 400 fields (application/json):

  - `data` (object,null)

  - `errors` (array,null)

  - `errors.errorCode` (string, required)
    Short text error identification

  - `errors.message` (string, required)
    Descriptive error message

  - `errors.instance` (string, required)
    Identification of the entity referenced

  - `metadata` (object)

  - `metadata.requestId` (string, required)
    Request identifier. Useful for logging/reporting purposes.

## Response 403 fields (application/json):

  - `data` (object,null)

  - `errors` (array,null)

  - `errors.errorCode` (string, required)
    Short text error identification

  - `errors.message` (string, required)
    Descriptive error message

  - `errors.instance` (string, required)
    Identification of the entity referenced

  - `metadata` (object)

  - `metadata.requestId` (string, required)
    Request identifier. Useful for logging/reporting purposes.

## Response 422 fields (application/json):

  - `data` (object,null)

  - `errors` (array,null)

  - `errors.errorCode` (string, required)
    Short text error identification

  - `errors.message` (string, required)
    Descriptive error message

  - `errors.instance` (string, required)
    Identification of the entity referenced

  - `metadata` (object)

  - `metadata.requestId` (string, required)
    Request identifier. Useful for logging/reporting purposes.