> ## Documentation Index
> Fetch the complete documentation index at: https://docs.extole.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create New

> Submits this business event from your backend as a person reaches it in the journey. Returns once identity resolution has completed, so the event is attributed to a known person - which suits low-volume, interactive submission from an admin or a user interface rather than bulk traffic; use Create New - Count Only for that.



## OpenAPI

````yaml /feature-specific-apis/business-events.json post /v6/events/template_tracked_business_event
openapi: 3.1.0
info:
  title: Business Events
  version: 1.0.0
  description: >-
    Operations published by Extole Business Events components. Generated from
    the component contracts on my.extole.com.
servers:
  - description: Production - Extole events host
    url: https://events.extole.io
security: []
paths:
  /v6/events/template_tracked_business_event:
    post:
      tags:
        - ACTION
      summary: Create New
      description: >-
        Submits this business event from your backend as a person reaches it in
        the journey. Returns once identity resolution has completed, so the
        event is attributed to a known person - which suits low-volume,
        interactive submission from an admin or a user interface rather than
        bulk traffic; use Create New - Count Only for that.
      operationId: create_event
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - email
              properties:
                email:
                  type: string
                  format: email
                  description: Email address of the person the event belongs to.
                partner_user_id:
                  type: string
                  description: Your own identifier for the person, when you have one.
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                required:
                  - event_id
                  - person_id
                properties:
                  event_id:
                    type: string
                    description: Unique identifier for the submitted event.
                  person_id:
                    type: string
                    description: Extole person the event resolved to.
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
              examples:
                binding_error:
                  $ref: '#/components/examples/binding_error'
                invalid_json:
                  $ref: '#/components/examples/invalid_json'
                invalid_parameter:
                  $ref: '#/components/examples/invalid_parameter'
                missing_request_body:
                  $ref: '#/components/examples/missing_request_body'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
              examples:
                access_denied:
                  $ref: '#/components/examples/access_denied'
                method_unauthorized:
                  $ref: '#/components/examples/method_unauthorized'
                missing_access_token:
                  $ref: '#/components/examples/missing_access_token'
      security:
        - HEADER: []
        - QUERY_PARAM: []
      servers:
        - description: Production - Extole events host
          url: https://events.extole.io
components:
  schemas:
    RestExceptionResponse:
      type: object
      description: Represents the API error response
      properties:
        code:
          type: string
          description: Specific error code for this error type, documented per endpoint
        http_status_code:
          type: integer
          description: >-
            HTTP status code that was returned with this error, useful if client
            get response code
        message:
          type: string
          description: User readable English description of the error
        parameters:
          type: object
          description: >-
            Attributes related to the error, varies be error code, documented
            per endpoint
          additionalProperties:
            type: object
            description: >-
              Attributes related to the error, varies be error code, documented
              per endpoint
        unique_id:
          type: string
          description: >-
            Unique id associated with this error, useful for discussions with
            Extole
      required:
        - code
        - http_status_code
        - message
        - parameters
        - unique_id
  examples:
    binding_error:
      summary: binding_error
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 400
        code: binding_error
        message: Argument is not of the expected type
        parameters: {}
    invalid_json:
      summary: invalid_json
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 400
        code: invalid_json
        message: JSON is invalid
        parameters: {}
    invalid_parameter:
      summary: invalid_parameter
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 400
        code: invalid_parameter
        message: Parameter is invalid.
        parameters: {}
    missing_request_body:
      summary: missing_request_body
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 400
        code: missing_request_body
        message: Missing request body
        parameters: {}
    access_denied:
      summary: access_denied
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 403
        code: access_denied
        message: >-
          The access_token provided is not permitted to access the specified
          resource.
        parameters: {}
    method_unauthorized:
      summary: method_unauthorized
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 403
        code: method_unauthorized
        message: Access forbidden to this endpoint
        parameters: {}
    missing_access_token:
      summary: missing_access_token
      value:
        unique_id: 00000000-0000-0000-0000-000000000000
        http_status_code: 403
        code: missing_access_token
        message: No access_token was provided with this request.
        parameters: {}
  securitySchemes:
    HEADER:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        A client access token, issued to your Extole account and used from your
        own backend. Never send a client token from a consumer device.
      x-bearer-format: bearer
    QUERY_PARAM:
      type: apiKey
      in: query
      name: access_token
      description: >-
        A client access token, issued to your Extole account and used from your
        own backend. Never send a client token from a consumer device.

````

## Related topics

- [Create New](/api-reference/feature-specific/transacted-business-event/action/create-new.md)
- [Create New - Count Only](/api-reference/feature-specific/tracked-business-event/action/create-new--count-only.md)
- [Create a user](/api-reference/users/create-a-user.md)
- [Create audience](/api-reference/audiences/create-audience.md)
- [Create a block](/api-reference/blocks/create-a-block.md)
