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

# Submit a named event asynchronously

> Submits a specific named consumer event asynchronously. The event name is supplied in the URL path and the body is an open data map. No per-request rate limit. Returns `event_id` only; person identification occurs asynchronously.



## OpenAPI

````yaml /api-reference/integration-server-to-extole.json post /v6/async-events/{event_name}
openapi: 3.0.1
info:
  description: >-
    Server-to-Extole integration endpoints: event submission, person lookup,
    zone rendering, token management, and reward retrieval for backend services
    authenticating with client credentials.
  title: Integration API - Server to Extole
  version: '1.0'
servers:
  - description: Production
    url: https://api.extole.io
security:
  - HEADER: []
  - QUERY: []
  - COOKIE: []
tags:
  - name: Authentication
  - name: Batch Jobs
  - name: Events
  - name: Files
  - name: Persons
  - name: Reward Suppliers
  - name: Rewards
  - name: SFTP Servers
  - name: Zone Rendering
paths:
  /v6/async-events/{event_name}:
    post:
      tags:
        - Events
      summary: Submit a named event asynchronously
      description: >-
        Submits a specific named consumer event asynchronously. The event name
        is supplied in the URL path and the body is an open data map. No
        per-request rate limit. Returns `event_id` only; person identification
        occurs asynchronously.
      operationId: submitNamedEventAsync
      parameters:
        - in: path
          name: event_name
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            example:
              email: user@example.com
              event_time: '2024-01-15T12:00:00Z'
              partner_user_id: usr_8392047156
              person_id: 7465313346145957000
            schema:
              $ref: '#/components/schemas/EventSubmissionData'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EventDispatcherAsyncResponse'
          description: >-
            Event accepted and queued for asynchronous processing. Returns the
            assigned `event_id`. Person identification completes after the
            response is returned.
        '400':
          content:
            application/json:
              examples:
                event_blocked:
                  $ref: '#/components/examples/event_blocked'
                invalid_event_time_format:
                  $ref: '#/components/examples/invalid_event_time_format'
                missing_event_name:
                  $ref: '#/components/examples/missing_event_name'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: >-
            Bad request. The named examples below cover this operation's
            specific validation errors. Other 400 causes include malformed JSON,
            an invalid `Time-Zone` header, and an empty request body - inspect
            the response `code` field for the specific error.
        '401':
          content:
            application/json:
              examples:
                method_unauthorized:
                  $ref: '#/components/examples/method_unauthorized'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: Unauthorized
        '402':
          content:
            application/json:
              examples:
                payment_required:
                  $ref: '#/components/examples/payment_required'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: Payment Required
        '403':
          content:
            application/json:
              examples:
                access_denied:
                  $ref: '#/components/examples/access_denied'
                method_unauthorized:
                  $ref: '#/components/examples/method_unauthorized'
                missing_access_token:
                  $ref: '#/components/examples/missing_access_token'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: Forbidden
        '415':
          content:
            application/json:
              examples:
                unsupported_media_type:
                  $ref: '#/components/examples/unsupported_media_type'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: Unsupported Media Type
        '429':
          content:
            application/json:
              examples:
                too_many_requests:
                  $ref: '#/components/examples/too_many_requests'
              schema:
                $ref: '#/components/schemas/RestExceptionResponse'
          description: Too Many Requests
      servers:
        - description: Production
          url: https://events.extole.io
components:
  schemas:
    EventSubmissionData:
      additionalProperties: true
      description: >-
        Open map of fields submitted with an event. May include keys beyond
        those listed here. `email` is the primary identity key and the only
        field that enables profile merging. `partner_user_id` is a secondary
        lookup key and is not guaranteed unique.
      example:
        email: user@example.com
        event_time: '2024-01-15T12:00:00Z'
        partner_user_id: usr_8392047156
        person_id: 7465313346145957000
      nullable: true
      properties:
        email:
          description: >-
            Primary identity key. The only data-map field that enables profile
            merging when submitted.
          example: user@example.com
          format: email
          type: string
        event_time:
          description: >-
            ISO 8601 timestamp of when the event occurred. Optional; defaults to
            the time the request is received. Use for backdated events. On
            wrapped request bodies this is an alternative to the top-level
            `event_time` field.
          example: '2024-01-15T12:00:00Z'
          format: date-time
          type: string
        partner_user_id:
          description: >-
            Secondary lookup key for an existing profile. Not guaranteed unique
            across your program.
          example: usr_8392047156
          type: string
        person_id:
          description: >-
            Extole person identifier. Numeric. Submit to target an existing
            profile instead of resolving by email or partner user id.
          example: 7465313346145957000
          format: int64
          type: integer
      type: object
    EventDispatcherAsyncResponse:
      properties:
        event_id:
          description: >-
            Unique identifier for the queued event. Person identification occurs
            asynchronously after the request returns.
          type: string
      required:
        - event_id
      type: object
    RestExceptionResponse:
      description: Represents the API error response
      properties:
        code:
          description: Specific error code for this error type, documented per endpoint
          type: string
        http_status_code:
          description: >-
            HTTP status code that was returned with this error, useful if client
            get response code
          format: int32
          type: integer
        message:
          description: User readable English description of the error
          type: string
        parameters:
          additionalProperties:
            description: >-
              Attributes related to the error, varies be error code, documented
              per endpoint
            type: object
          description: >-
            Attributes related to the error, varies be error code, documented
            per endpoint
          type: object
        unique_id:
          description: >-
            Unique id associated with this error, useful for discussions with
            Extole
          type: string
      required:
        - code
        - http_status_code
        - message
        - parameters
        - unique_id
      type: object
  examples:
    event_blocked:
      summary: event_blocked
      value:
        code: event_blocked
        http_status_code: 400
        message: Blocked due to client specific rules to ignore spurious events
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    invalid_event_time_format:
      summary: invalid_event_time_format
      value:
        code: invalid_event_time_format
        http_status_code: 400
        message: 'Invalid event time format. Expected: ISO8601 format'
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    missing_event_name:
      summary: missing_event_name
      value:
        code: missing_event_name
        http_status_code: 400
        message: Event name is required.
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    method_unauthorized:
      summary: method_unauthorized
      value:
        code: method_unauthorized
        http_status_code: 401
        message: Unauthorized access to this endpoint
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    payment_required:
      summary: payment_required
      value:
        code: payment_required
        http_status_code: 402
        message: The access_token provided is associated with an unpaid account.
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    access_denied:
      summary: access_denied
      value:
        code: access_denied
        http_status_code: 403
        message: >-
          The access_token provided is not permitted to access the specified
          resource.
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    missing_access_token:
      summary: missing_access_token
      value:
        code: missing_access_token
        http_status_code: 403
        message: No access_token was provided with this request.
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    unsupported_media_type:
      summary: unsupported_media_type
      value:
        code: unsupported_media_type
        http_status_code: 415
        message: Request had an unsupported or no media type
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
    too_many_requests:
      summary: too_many_requests
      value:
        code: too_many_requests
        http_status_code: 429
        message: >-
          The server is unable to process your request at the moment, please
          retry later.
        parameters: {}
        unique_id: 00000000-0000-0000-0000-000000000000
  securitySchemes:
    HEADER:
      in: header
      name: Authorization
      type: apiKey
      x-bearer-format: bearer
    QUERY:
      in: query
      name: access_token
      type: apiKey
    COOKIE:
      in: cookie
      name: extole_token
      type: apiKey

````