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

# Update up to 100 accounts, each with its own values

> `items` is up to 100 updates, each an account `id` and an update body. Each is checked and written on its own, so one failure does not stop the rest. The answer lists every item in request order with `status` `updated` or `failed`, and for a failure the `error` (code, message, details) a single update would have returned; a database timeout on one item is `internal_error` there. As with a single update, a failed item may be partly written. The request itself fails only when it is malformed (no items, more than 100, or an account twice). It counts as one write per item against your rate limit; a batch larger than your key's write limit per minute is a 422 saying how many items fit, and costs one write, as every request does.



## OpenAPI

````yaml /api/statisfy-api.openapi.json post /v1/objects/account/records/batch/update
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/objects/account/records/batch/update:
    post:
      tags:
        - accounts
      summary: Update up to 100 accounts, each with its own values
      description: >-
        `items` is up to 100 updates, each an account `id` and an update body.
        Each is checked and written on its own, so one failure does not stop the
        rest. The answer lists every item in request order with `status`
        `updated` or `failed`, and for a failure the `error` (code, message,
        details) a single update would have returned; a database timeout on one
        item is `internal_error` there. As with a single update, a failed item
        may be partly written. The request itself fails only when it is
        malformed (no items, more than 100, or an account twice). It counts as
        one write per item against your rate limit; a batch larger than your
        key's write limit per minute is a 422 saying how many items fit, and
        costs one write, as every request does.
      operationId: accounts_batch_update
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: false
              properties:
                items:
                  description: Each an account id and its update
                  items:
                    $ref: '#/components/schemas/BatchUpdateItem'
                  maxItems: 100
                  minItems: 1
                  title: Items
                  type: array
              required:
                - items
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BatchUpdateResult'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    BatchUpdateItem:
      additionalProperties: true
      properties:
        arr:
          default: null
          description: Annual recurring revenue, whole dollars
          title: Arr
          type: integer
        fields:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          default: null
          description: Custom field keys to values
          title: Fields
        id:
          title: Id
          type: string
        name:
          default: null
          description: The account's name
          title: Name
          type: string
        renewal_date:
          default: null
          description: YYYY-MM-DD
          format: date
          title: Renewal Date
          type: string
        type:
          default: null
          description: One of the account types describe lists
          title: Type
          type: string
      required:
        - id
      title: BatchUpdateItem
      type: object
    BatchUpdateResult:
      properties:
        items:
          items:
            $ref: '#/components/schemas/BatchItemResult'
          title: Items
          type: array
      required:
        - items
      title: BatchUpdateResult
      type: object
    BatchItemResult:
      properties:
        error:
          anyOf:
            - $ref: '#/components/schemas/ItemError'
            - type: 'null'
          description: Set exactly when `status` is `failed`
        id:
          title: Id
          type: string
        status:
          enum:
            - updated
            - failed
          title: Status
          type: string
      required:
        - id
        - status
      title: BatchItemResult
      type: object
    ItemError:
      description: The error envelope a single request would have returned.
      properties:
        code:
          title: Code
          type: string
        details:
          items:
            additionalProperties: true
            type: object
          title: Details
          type: array
        message:
          title: Message
          type: string
      required:
        - code
        - message
      title: ItemError
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

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