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

# Create File Upload

> Reserves a file and returns a short-lived presigned POST form to upload it
to. Submit the form as multipart/form-data with the returned fields first
and the bytes in a trailing `file` part. The upload is unusable until
ConfirmFileUpload accepts it.

Required scope: documents:write

Error Codes:
  - DEVELOPER.SCOPE_INSUFFICIENT: The key lacks the documents:write scope.
  - FILE.INVALID_CONTENT_TYPE: The content type is not application/pdf.
  - FILE.INVALID_SIZE: size_bytes is zero, negative, or above the limit.
  - FILE.PENDING_LIMIT_EXCEEDED: Too many unconfirmed uploads for the key owner.



## OpenAPI

````yaml /api-reference/openapi.yaml post /developer/v1/files
openapi: 3.0.3
info:
  description: >-
    Публичный Developer API Doodocs People. Аутентификация — заголовок
    X-API-Key.
  title: Doodocs People API
  version: 1.0.0
servers:
  - description: Production
    url: https://app.doodocs.kz/api
security:
  - ApiKeyAuth: []
tags:
  - description: ApiKeyService exposes Developer API key utilities.
    name: ApiKeyService
  - description: >-
      DocumentService is the public Developer API for documents: reading,
      creating,
       downloading, routing, and signing.

       Authentication: X-API-Key. Every call runs as the key's owner within the key's
       tenant — the owner's document permissions decide what is visible and which
       actions are allowed, exactly as they would in the web app. Fields that carry
       personal data of other participants (names, IIN, positions) are never exposed;
       participants are identified by id only.

       Typical flow: discover a template with ListDocumentTemplates /
       GetDocumentTemplate (to learn its variable_schema), create a draft with
       CreateDocument, set its route with SetDocumentRoute, launch it with
       SendDocument, then apply signatures with SignDocument as slots become active.

       To circulate a document produced elsewhere, upload it with FileService and
       pass the confirmed file_id to CreateDocument instead of a template.
    name: DocumentService
  - description: |-
      EmployeeService is the public Developer API for reading employees.

       Authentication: X-API-Key. The key's tenant and the key owner's data scope
       determine which employees and fields are visible; sensitive fields the caller
       may not view are omitted and listed in `redacted_fields`.
    name: EmployeeService
  - description: |-
      FileService uploads the files documents are created from.

       Authentication: X-API-Key. An upload belongs to the key's owner, and only
       their key can attach it to a document.

       Flow: CreateFileUpload reserves the file and returns a presigned POST form,
       the client sends the bytes straight to storage, ConfirmFileUpload marks the
       upload complete, and CreateDocument attaches it by id.
    name: FileService
  - description: IngestService accepts batches of external records into the tenant.
    name: IngestService
  - name: LoginService
  - description: |-
      WebhookService lets a tenant manage subscriptions to Developer API events.

       Authentication: X-API-Key with the webhooks:manage scope.
    name: WebhookService
paths:
  /developer/v1/files:
    post:
      tags:
        - FileService
      summary: Create File Upload
      description: >-
        Reserves a file and returns a short-lived presigned POST form to upload
        it

        to. Submit the form as multipart/form-data with the returned fields
        first

        and the bytes in a trailing `file` part. The upload is unusable until

        ConfirmFileUpload accepts it.


        Required scope: documents:write


        Error Codes:
          - DEVELOPER.SCOPE_INSUFFICIENT: The key lacks the documents:write scope.
          - FILE.INVALID_CONTENT_TYPE: The content type is not application/pdf.
          - FILE.INVALID_SIZE: size_bytes is zero, negative, or above the limit.
          - FILE.PENDING_LIMIT_EXCEEDED: Too many unconfirmed uploads for the key owner.
      operationId: FileService_CreateFileUpload
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateFileUploadRequest'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateFileUploadResponse'
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
          description: Default error response
components:
  schemas:
    CreateFileUploadRequest:
      properties:
        content_type:
          description: >-
            Must be application/pdf: the file is attached as the document's PDF
            as it
             is, without conversion.
          type: string
        filename:
          description: Filename to store the file under (shown when downloading).
          type: string
        size_bytes:
          description: Exact size of the bytes to upload; storage rejects a larger object.
          type: string
      required:
        - filename
        - content_type
        - size_bytes
      type: object
    CreateFileUploadResponse:
      properties:
        file:
          allOf:
            - $ref: '#/components/schemas/FileUpload'
          description: The reserved upload (status PENDING).
          readOnly: true
        upload:
          allOf:
            - $ref: '#/components/schemas/PresignedUpload'
          description: The presigned form to POST the bytes to.
          readOnly: true
      type: object
    Status:
      description: >-
        The `Status` type defines a logical error model that is suitable for
        different programming environments, including REST APIs and RPC APIs. It
        is used by [gRPC](https://github.com/grpc). Each `Status` message
        contains three pieces of data: error code, error message, and error
        details. You can find out more about this error model and how to work
        with it in the [API Design
        Guide](https://cloud.google.com/apis/design/errors).
      properties:
        code:
          description: >-
            The status code, which should be an enum value of
            [google.rpc.Code][google.rpc.Code].
          format: int32
          type: integer
        details:
          description: >-
            A list of messages that carry the error details.  There is a common
            set of message types for APIs to use.
          items:
            $ref: '#/components/schemas/GoogleProtobufAny'
          type: array
        message:
          description: >-
            A developer-facing error message, which should be in English. Any
            user-facing error message should be localized and sent in the
            [google.rpc.Status.details][google.rpc.Status.details] field, or
            localized by the client.
          type: string
      type: object
    FileUpload:
      description: FileUpload is a file owned by the key's owner.
      properties:
        content_type:
          description: MIME type of the file (application/pdf).
          readOnly: true
          type: string
        create_time:
          description: When the upload was reserved.
          format: date-time
          readOnly: true
          type: string
        filename:
          description: Filename as reserved at creation.
          readOnly: true
          type: string
        id:
          description: Upload id (UUID) — pass to ConfirmFileUpload and CreateDocument.
          readOnly: true
          type: string
        size_bytes:
          description: Reserved size of the file in bytes.
          readOnly: true
          type: string
        status:
          description: 'Where the upload stands: PENDING, UPLOADED, or LINKED.'
          enum:
            - FILE_UPLOAD_STATUS_UNSPECIFIED
            - FILE_UPLOAD_STATUS_PENDING
            - FILE_UPLOAD_STATUS_UPLOADED
            - FILE_UPLOAD_STATUS_LINKED
          format: enum
          readOnly: true
          type: string
      type: object
    PresignedUpload:
      description: PresignedUpload is the form to POST the bytes to.
      properties:
        expires_at:
          description: When the form stops being accepted; re-create the upload after that.
          format: date-time
          readOnly: true
          type: string
        fields:
          additionalProperties:
            type: string
          description: Form fields to send before the file part, verbatim.
          readOnly: true
          type: object
        url:
          description: Storage URL to POST the multipart form to.
          readOnly: true
          type: string
      type: object
    GoogleProtobufAny:
      additionalProperties: true
      description: >-
        Contains an arbitrary serialized message along with a @type that
        describes the type of the serialized message.
      properties:
        '@type':
          description: The type of the serialized message.
          type: string
      type: object
  securitySchemes:
    ApiKeyAuth:
      in: header
      name: X-API-Key
      type: apiKey

````