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

# Upload SQLite database for a tenant

> Upload a SQLite database file for the authenticated Tenant. Use this when each of your tenants has its own database. Send the file as multipart/form-data with the field name "file". Accepted formats: .db (raw SQLite) or .db.gz (gzip-compressed). Data is synced automatically on a schedule after upload. **Note:** This is an experimental feature. If you are interested in using it, please contact us.



## OpenAPI

````yaml POST /api/partner-db/upload
openapi: 3.0.0
info:
  title: Reach API
  version: 1.0.0
  description: API documentation for Reach platform
servers:
  - url: https://api.embedreach.com
    description: Production server
security: []
paths:
  /api/partner-db/upload:
    post:
      tags:
        - Partner DB
      summary: Upload SQLite database for a tenant
      description: >-
        Upload a SQLite database file for the authenticated Tenant. Use this
        when each of your tenants has its own database. Send the file as
        multipart/form-data with the field name "file". Accepted formats: .db
        (raw SQLite) or .db.gz (gzip-compressed). Data is synced automatically
        on a schedule after upload. **Note:** This is an experimental feature.
        If you are interested in using it, please contact us.
      parameters:
        - name: reach-tenant-id
          in: header
          required: false
          schema:
            type: string
            description: >-
              Tenant ID. Required when using a platform-scoped JWT to identify
              which tenant the upload is for.
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                file:
                  type: string
                  format: binary
                  description: SQLite database file (.db or .db.gz)
              required:
                - file
      responses:
        '202':
          description: Status 202 response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  message:
                    type: string
                  data:
                    type: object
                    properties: {}
                required:
                  - success
        '400':
          description: Bad Request - Validation or request error
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                    default: false
                  message:
                    type: string
                    description: Error message describing what went wrong
                  errors:
                    type: array
                    items:
                      type: string
                    description: Optional array of specific validation errors
                required:
                  - message

````