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

# Add a product to the not-confused-with list

> Adds a same-named product by name and domain, applied from the next scan on. Matches on domain, so a pending suggestion or dismissed entry for it is accepted. Returns the full list.



## OpenAPI

````yaml https://api.usenotra.com/openapi.json post /v1/projects/{projectId}/geo/name-collisions
openapi: 3.1.1
info:
  title: Notra API
  version: 1.0.0
  description: >-
    OpenAPI schema for Notra content endpoints. Use GET /v1/status for public
    reachability. Error responses include recovery guidance. Breaking changes
    ship under a new major path; deprecated operations send Deprecation and
    Sunset headers at least 90 days before removal.
servers:
  - url: https://api.usenotra.com
    description: Production
  - url: https://demo-api.usenotra.com
    description: >-
      Sandbox with sample data. Get a free sandbox key at demo.usenotra.com, no
      signup needed
security:
  - BearerAuth: []
tags:
  - name: Webhooks
    description: Manage outbound webhook subscriptions and delivery history.
  - name: Discovery
    description: >-
      Public API status, keyless pricing quotes and authenticated workspace
      discovery.
  - name: Content
    description: >-
      Manage posts, brand identities, and GitHub or Linear integrations, and
      queue content generation. Organization is inferred from the API key
      (identity.externalId).
  - name: Autopilot
    description: >-
      Inspect Autopilot for a workspace, or start and stop runs as a workspace
      owner or admin.
  - name: Schedules
    description: >-
      Manage scheduled content generation. Organization is inferred from the API
      key (identity.externalId).
  - name: Event Triggers
    description: >-
      Manage event-based content generation triggered by GitHub webhooks.
      Organization is inferred from the API key (identity.externalId).
  - name: Chats
    description: >-
      Manage chat sessions. Organization is inferred from the API key
      (identity.externalId).
  - name: Skills
    description: >-
      Manage reusable writing skills. Organization is inferred from the API key
      (identity.externalId).
  - name: Feedback
    description: >-
      Collect and triage feedback submitted by AI agents. Agents post to the
      organization's feedback URL without credentials; reading and triage
      require an API key with feedback.read or feedback.write.
  - name: GEO
    description: >-
      Manage generative engine optimization: projects, tracking settings,
      prompts, prompt sequences, competitors, scans, visibility reads, content
      gaps and briefs, agent readiness and AI traffic. Project-scoped endpoints
      require the GEO plan entitlement in addition to their scope;
      organization-level ingest endpoints require only the traffic scope.
  - name: Sites
    description: >-
      Notra Sites are hosted blogs and changelogs built from a GitHub
      repository. Read Sites and their deployments, start builds, preview posts
      on a Site, open pull requests that publish posts to it, and manage
      blog.json authors and the author page through staged Design changes.
      Domains, settings, rollbacks and deletion stay in the dashboard.
externalDocs:
  description: Notra API versioning and deprecation policy
  url: https://www.usenotra.com/docs/api/versioning
paths:
  /v1/projects/{projectId}/geo/name-collisions:
    post:
      tags:
        - GEO
      summary: Add a product to the not-confused-with list
      description: >-
        Adds a same-named product by name and domain, applied from the next scan
        on. Matches on domain, so a pending suggestion or dismissed entry for it
        is accepted. Returns the full list.
      operationId: addGeoNameCollision
      parameters:
        - schema:
            type: string
            minLength: 1
            pattern: ^[A-Za-z0-9_-]{1,100}$
            example: b1f2c3d4-0000-4000-8000-000000000000
          required: true
          name: projectId
          in: path
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AddGeoNameCollisionRequest'
      responses:
        '200':
          description: Name collision saved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListGeoNameCollisionsResponse'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '402':
          description: GEO plan or available AI credits required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Organization, project or resource not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '503':
          description: Authentication or billing service unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    AddGeoNameCollisionRequest:
      type: object
      properties:
        name:
          type: string
          minLength: 1
          maxLength: 128
          description: Name of the other product.
          example: Acme
        domain:
          type: string
          maxLength: 128
          description: >-
            Domain of the other product. A pending suggestion for the same
            domain is accepted.
          example: acme.io
      required:
        - name
        - domain
    ListGeoNameCollisionsResponse:
      type: object
      properties:
        notConfusedWith:
          type: array
          items:
            $ref: '#/components/schemas/GeoNameCollision'
          description: >-
            Accepted entries. Answers that name your brand but are about one of
            these products are not counted as mentions.
        suggestions:
          type: array
          items:
            $ref: '#/components/schemas/GeoNameCollision'
          description: >-
            Same-named products that scan answers cited on other domains,
            waiting to be accepted or dismissed.
        organization:
          type: object
          properties:
            id:
              type: string
              description: >-
                Workspace ID. Account API keys can send it, or the slug, as
                X-Notra-Organization-Id.
            slug:
              type: string
              description: URL-safe workspace handle, unique across Notra.
            name:
              type: string
              description: Workspace display name.
            logo:
              type:
                - string
                - 'null'
              description: Workspace logo image URL. Null when none is set.
          required:
            - id
            - slug
            - name
            - logo
          description: Workspace the request ran in.
      required:
        - notConfusedWith
        - suggestions
        - organization
      description: The project's not-confused-with list and its suggestions.
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        code:
          type: string
        recovery:
          type: string
      required:
        - error
    GeoNameCollision:
      type: object
      properties:
        id:
          type: string
          description: Entry id.
        name:
          type: string
          description: Name of the other product, usually the same as yours.
        domain:
          type: string
          description: Domain of the other product, such as `acme.io`.
        status:
          type: string
          enum:
            - pending
            - accepted
            - dismissed
          description: >-
            `accepted` entries are applied to mention detection; `pending` ones
            are suggestions waiting for review.
        source:
          type: string
          enum:
            - manual
            - scan
          description: >-
            `manual` when added by hand, `scan` when a scan suggested it from
            cited sources.
        evidenceUrl:
          type:
            - string
            - 'null'
          description: >-
            Cited page that made a scan suggest the entry, or `null` for manual
            entries.
        createdAt:
          type: string
          description: When the entry was created, as an ISO 8601 timestamp.
      required:
        - id
        - name
        - domain
        - status
        - source
        - evidenceUrl
        - createdAt
      description: >-
        A different product that shares your brand's name. Answers about it
        don't count as mentions of you.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: >-
        Send your API key in the Authorization header as Bearer API_KEY. Account
        API keys work in every workspace you belong to: send
        X-Notra-Organization-Id with the workspace id or slug to choose one.
        Workspace endpoints require it when you belong to more than one
        workspace; GET /v1/me/workspaces works without it. Organization keys
        only accept their own workspace there.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.