leadboxer-com User Datasets API

openapi: 3.2.0
info:
  title: Leadboxer User Datasets API
  description: '# LeadBoxer API Documentation


    Here you can find the technical documentation needed for using the LeadBoxer API, including the option to generate requests and review the outcomes.


    ## Getting Started


    To get started, please have a look at these pages that include introductions, use-cases, and additional information for the LeadBoxer API: LeadBoxer API Documentation


    These documents are intended for LeadBoxer CUSTOMERS that have a valid API license & Key. Please contact us before using the LeadBoxer API.


    ## Warning


    Please be aware that any actions you perform through this reference testing functionality will involve operations with your production data. To test your applications against some sandbox data, we recommend creating a new, separate LeadBoxer account for sandboxing purposes.


    This API is under active maintenance, and we are constantly adding new functionality to this version.


    [**All requests to the API must be made over SSL (https, not http).**]'
  termsOfService: https://www.leadboxer.com/resources/terms
  contact:
    name: Wart Fransen
    url: wart@leadboxer.com
    email: hello@leadboxer.com
  license:
    name: ''
    url: https://www.leadboxer.com/resources/privacy
  version: 0.0.1
servers:
- url: https://api.leadboxer.com
  description: Production Server
security:
- ApiKeyAuth: []
tags:
- name: UserDatasets
  description: Manage access to your datasets. Associate/dissociate datasets with users etc.
paths:
  /v1/user-datasets:
    get:
      tags:
      - UserDatasets
      summary: Fetch User Datasets
      description: Retrieves the datasets associated with a user for the given account. This provides details about the user's datasets under their account.
      operationId: getUserDatasets_1
      parameters:
      - name: accountId
        in: query
        description: The unique identifier for the user's account.
        required: true
        schema:
          type: string
      - name: email
        in: query
        description: The email address of the user for whom datasets are being fetched.
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/GetAllResponseAccountUserDatasetDTO'
        '400':
          description: 'Bad Request: The request is invalid or malformed (missing/incorrect parameters).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1BadRequestResponse'
        '402':
          description: 'Payment Required: The client has exceeded credit limits.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
        '403':
          description: 'Forbidden: The authenticated user does not have permission to access this resource.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1PermissionDenied'
        '404':
          description: 'Not Found: The requested resource does not exist.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1NotFoundResponse'
        '409':
          description: 'Conflict: The request could not be completed due to a resource state conflict.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1ConflictResponse'
        '429':
          description: 'Too Many Requests: Rate limit exceeded. The client has sent too many requests in a given time period'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RateLimitErrorResponse'
        '500':
          description: 'Interval Server Error: An unexpected error occurred on the server.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
    post:
      tags:
      - UserDatasets
      summary: Add User Dataset
      description: Associates a user with a dataset. This operation allows the user to access and work with the specified dataset.
      operationId: addUserDataset
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AddUserDataset'
        required: true
      responses:
        '204':
          description: User successfully associated with given dataset. No content returned.
        '400':
          description: 'Bad Request: The request is invalid or malformed (missing/incorrect parameters).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1BadRequestResponse'
        '402':
          description: 'Payment Required: The client has exceeded credit limits.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
        '403':
          description: 'Forbidden: The authenticated user does not have permission to access this resource.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1PermissionDenied'
        '404':
          description: 'Not Found: The requested resource does not exist.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1NotFoundResponse'
        '409':
          description: 'Conflict: The request could not be completed due to a resource state conflict.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1ConflictResponse'
        '429':
          description: 'Too Many Requests: Rate limit exceeded. The client has sent too many requests in a given time period'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RateLimitErrorResponse'
        '500':
          description: 'Interval Server Error: An unexpected error occurred on the server.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
    delete:
      tags:
      - UserDatasets
      summary: Remove User Dataset
      description: Disassociates a user from a dataset. This operation will prevent the user from accessing the specified dataset.
      operationId: removeUserDataset
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RemoveUserDataset'
        required: true
      responses:
        '204':
          description: No Content
        '400':
          description: 'Bad Request: The request is invalid or malformed (missing/incorrect parameters).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1BadRequestResponse'
        '402':
          description: 'Payment Required: The client has exceeded credit limits.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
        '403':
          description: 'Forbidden: The authenticated user does not have permission to access this resource.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1PermissionDenied'
        '404':
          description: 'Not Found: The requested resource does not exist.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1NotFoundResponse'
        '409':
          description: 'Conflict: The request could not be completed due to a resource state conflict.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1ConflictResponse'
        '429':
          description: 'Too Many Requests: Rate limit exceeded. The client has sent too many requests in a given time period'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RateLimitErrorResponse'
        '500':
          description: 'Interval Server Error: An unexpected error occurred on the server.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1InternalServerError'
components:
  schemas:
    V1PermissionDenied:
      type: object
      properties:
        type:
          type: string
          description: A URI reference that identifies the problem type
        title:
          type: string
          description: A short, human-readable summary of the problem type
        status:
          type: integer
          description: The HTTP status code
          format: int32
          example: 403
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence of the problem
        instance:
          type: string
          description: A URI reference that identifies the specific occurrence of the problem
    GetAllResponseAccountUserDatasetDTO:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/AccountUserDatasetDTO'
        metaData:
          type: object
    V1InternalServerError:
      type: object
      properties:
        type:
          type: string
          description: A URI reference that identifies the problem type
        title:
          type: string
          description: A short, human-readable summary of the problem type
          example: Internal Server Error
        status:
          type: integer
          description: The HTTP status code
          format: int32
          example: 500
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence of the problem
          example: An unexpected error occurred. Please contact support.
        instance:
          type: string
          description: A URI reference that identifies the specific occurrence of the problem
    AddUserDataset:
      required:
      - datasetId
      - timezone
      - userId
      type: object
      properties:
        userId:
          type: integer
          format: int64
        datasetId:
          type: string
        timezone:
          type: string
        sendEmail:
          type: boolean
    RateLimitErrorResponse:
      type: object
      properties:
        timestamp:
          type: integer
          format: int64
          example: 1765611454230
        status:
          type: integer
          format: int32
          example: 429
        error:
          type: string
          example: Too Many Requests
        message:
          type: string
          example: Rate limit exceeded. Please try again later.
        retryAfter:
          type: integer
          format: int32
          example: 58
        limit:
          type: integer
          format: int32
          example: 2
        remaining:
          type: integer
          format: int32
          example: 0
      description: Rate limit exceeded error response
    AccountUserDTO:
      type: object
      properties:
        userId:
          type: integer
          format: int64
        email:
          type: string
        firstName:
          type: string
        lastName:
          type: string
        role:
          type: string
        lastLogin:
          type: string
          format: date-time
        unixTimeEndActiveDate:
          type: integer
          format: int64
        client:
          $ref: '#/components/schemas/ClientDTO'
        uiRole:
          type: integer
          format: int64
    V1BadRequestResponse:
      type: object
      properties:
        type:
          type: string
          description: A URI reference that identifies the problem type
          example: https://developers.leadboxer.com/docs/validation-error
        title:
          type: string
          description: A short, human-readable summary of the problem type
          example: The request is malformed or contains invalid data
        status:
          type: integer
          description: The HTTP status code
          format: int32
          example: 400
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence of the problem
          example: email must be a well-formed email address
        instance:
          type: string
          description: A URI reference that identifies the specific occurrence of the problem
          example: /v1/users/{userId}/name?email=johndoe.com
        errors:
          type: array
          description: Array of field-level validation errors
          items:
            $ref: '#/components/schemas/ValidationError'
    V1ConflictResponse:
      type: object
      properties:
        type:
          type: string
          description: A URI reference that identifies the problem type
        title:
          type: string
          description: A short, human-readable summary of the problem type
          example: Resource already exist
        status:
          type: integer
          description: The HTTP status code
          format: int32
          example: 409
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence of the problem
          example: 'User with email: john.doe@examplecompany.com already exist'
        instance:
          type: string
          description: A URI reference that identifies the specific occurrence of the problem
          example: /v1/users/?email=john.doe@examplecompany.com
    RemoveUserDataset:
      required:
      - datasetId
      - userId
      type: object
      properties:
        userId:
          type: integer
          format: int64
        datasetId:
          type: string
    V1NotFoundResponse:
      type: object
      properties:
        type:
          type: string
          description: A URI reference that identifies the problem type
        title:
          type: string
          description: A short, human-readable summary of the problem type
        status:
          type: integer
          description: The HTTP status code
          format: int32
          example: 404
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence of the problem
        instance:
          type: string
          description: A URI reference that identifies the specific occurrence of the problem
    ClientDTO:
      type: object
      properties:
        clientId:
          type: integer
          format: int64
        clientName:
          type: string
        smartlistId:
          type: integer
          format: int32
        createdTimestamp:
          type: string
          format: date-time
        modifiedTimestamp:
          type: string
          format: date-time
        users:
          type: array
          items:
            $ref: '#/components/schemas/BaseUserDTO'
    BaseUserDTO:
      type: object
      properties:
        userId:
          type: integer
          format: int64
        firstName:
          type: string
        lastName:
          type: string
        email:
          type: string
    UserDatasetDTO:
      type: object
      properties:
        datasetId:
          type: string
        humanName:
          type: string
        timezone:
          type: string
        formTracking:
          type: boolean
        formInputAttribute:
          type: string
        allowIpMasking:
          type: boolean
        apiKey:
          type: string
        accessToken:
          type: string
        createdTimestamp:
          type: string
          format: date-time
    ValidationError:
      type: object
      properties:
        field:
          type: string
          description: The name of the field that failed validation
          example: email
        message:
          type: string
          description: Human-readable error message for this specific field
          example: must be a well-formed email address
      description: Array of field-level validation errors
    AccountUserDatasetDTO:
      type: object
      properties:
        user:
          $ref: '#/components/schemas/AccountUserDTO'
        site:
          $ref: '#/components/schemas/UserDatasetDTO'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      description: Provide your LeadBoxer API Key
      name: x-api-key
      in: header
x-provenance:
  method: searched
  source: https://developers.leadboxer.com/reference
  harvested: '2026-10-30'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://developers.leadboxer.com/reference/addcustomtrackingdomain.md
  - https://developers.leadboxer.com/reference/adddataset.md
  - https://developers.leadboxer.com/reference/adduser.md
  - https://developers.leadboxer.com/reference/adduserdataset.md
  - https://developers.leadboxer.com/reference/assignleads.md
  - https://developers.leadboxer.com/reference/authentication.md
  - https://developers.leadboxer.com/reference/createsegment.md
  - https://developers.leadboxer.com/reference/deletecustomtrackingdomain.md
  - https://developers.leadboxer.com/reference/deletedatasetexclusion.md
  - https://developers.leadboxer.com/reference/deletedefaultsegment.md
  - https://developers.leadboxer.com/reference/deletesegment.md
  - https://developers.leadboxer.com/reference/getavailablecreditgrants.md
  - https://developers.leadboxer.com/reference/getcustomtrackingdomains.md
  - https://developers.leadboxer.com/reference/getdatasetexclusions.md
  - https://developers.leadboxer.com/reference/getevents.md
  - https://developers.leadboxer.com/reference/getsegments.md
  - https://developers.leadboxer.com/reference/getsessions.md
  - https://developers.leadboxer.com/reference/getting-started.md
  - https://developers.leadboxer.com/reference/getuserdatasets.md
  - https://developers.leadboxer.com/reference/getuserdatasets_1.md
  - https://developers.leadboxer.com/reference/getusersbysegmentidanddatasetid.md
  - https://developers.leadboxer.com/reference/leaddetail.md
  - https://developers.leadboxer.com/reference/lookupdomain.md
  - https://developers.leadboxer.com/reference/lookupemail.md
  - https://developers.leadboxer.com/reference/lookupemailbyquery.md
  - https://developers.leadboxer.com/reference/lookupip.md
  - https://developers.leadboxer.com/reference/my-requests.md
  - https://developers.leadboxer.com/reference/removedataset.md
  - https://developers.leadboxer.com/reference/removeuser.md
  - https://developers.leadboxer.com/reference/removeuserdataset.md
  - https://developers.leadboxer.com/reference/resendinvite.md
  - https://developers.leadboxer.com/reference/savedatasetexclusion.md
  - https://developers.leadboxer.com/reference/savedefaultsegment.md
  - https://developers.leadboxer.com/reference/updatedatasetname.md
  - https://developers.leadboxer.com/reference/updatedcustomtrackingdomain.md
  - https://developers.leadboxer.com/reference/updateformtracking.md
  - https://developers.leadboxer.com/reference/updateleadtags.md
  - https://developers.leadboxer.com/reference/updatename.md
  - https://developers.leadboxer.com/reference/updatesegment.md
  - https://developers.leadboxer.com/reference/updatesegmentuser.md
  - https://developers.leadboxer.com/reference/users.md
  - https://developers.leadboxer.com/reference/userscsv.md
  - https://developers.leadboxer.com/reference/validatecustomtrackingdomain.md
  merge:
    pages: 43
    deduped: 355
    conflicts_kept_first: 0