---
title: "ProcessActivityLogs.batch_create_or_update"
method: POST
path: "/entities/ProcessActivityLogs/batch-modify"
tags: ["Process"]
---

# ProcessActivityLogs.batch_create_or_update

`POST /entities/ProcessActivityLogs/batch-modify`

## Request

- Base URL: `https://us-east.api.coevera.com/api/v100/rest/spaces/your_space_id`
- URL: `https://us-east.api.coevera.com/api/v100/rest/spaces/your_space_id/entities/ProcessActivityLogs/batch-modify`
- Auth: HTTP basic
- TypeScript: <https://skmtc.dev/coevera/apis/coevera-crm-api/docs/entities/ProcessActivityLogs/batch-modify/post.ts> (a function with typed inputs; its response is checked against the schema)

Creates or updates ProcessActivityLog records in one request: an item with an id updates that record, an item without one creates a new record.

## Query parameters

- `validation-level` integer
- `rollback-method` 0 | 1

## Request body

- BatchProcessActivityLogInput[]
  - `actor_id` string, uuid: Id of the user who triggered the run, or empty for runs triggered by automation.
  - `application_id` string, uuid: Id of the application the triggering change came from, such as the web app or an API access; scheduled runs are attributed to the Automatizer.
  - `cpu_run_time` number, double: Total CPU time consumed by the run, in seconds.
  - `end_time` string, date-time: Timestamp the run finished. Empty while the run is still in progress (e.g. waiting on scheduled actions).
  - `is_test_run` boolean: True when the run was triggered as a test (results are not persisted to records).
  - `parent_process_ids` object: Ids of parent processes that triggered this run, ordered from outermost to innermost. Empty for top-level runs.
  - `process_id` string, uuid: Id of the Automatizer process whose run this log records.
  - `run_id` string, uuid: Identifier grouping all activity logs that share the same root process run, including chained sub-process runs.
  - `start_time` string, date-time: Timestamp the run started.
  - `status` 1 | 2 | 3 | 4 | 5: Overall result of the process run: the most severe status among its log lines, Error when any step failed and Warning when a step completed with warnings. Integer enum value: 1 - Ok, 2 - Warning, 3 - Error, 4 - Scheduled, 5 - Expired
  - `id` string, uuid: ID of object to update.

## Response `200`

Result per item, in request order: the id of the created or updated record, or the error.

- object
  - `success` boolean: True when the request succeeded; false on error.
  - `data` union[]
    - union
      - string, uuid: Id of the created or updated record.
      - Error: The body of every REST error. `code` and `name` are stable identifiers; `message` is for people. The full list of codes is at https://developers.coevera.com/reference/errors/.
        - `http_status` integer, required: HTTP status code.
        - `code` integer: Numeric code of the API error.
        - `name` string: Name of the API error.
        - `message` string: Message describing the error.
        - `success` boolean, required: Always false on error.

## Other responses

- `400`: Bad request: a bad or unknown parameter (codes 117, 118), a missing permission (code 50), conflicting data (code 2002) or any other API error. The REST API answers 400 where others answer 403 or 409; check `code`.
- `401`: Not authenticated: missing or wrong credentials, a credential of another space, or an expired token (code 401, ERROR_UNAUTHORIZED).
- `422`: Validation failed (code 40000, with the failing fields) or a required parameter is missing (code 119). By default one failed item fails a whole batch and nothing is written.
- `429`: Too many requests (code 182). Wait for the seconds in Retry-After, then retry.
- `500`: Unexpected server error (code 1000, ERROR_UNKNOWN).

---

[API](https://skmtc.dev/coevera/apis/coevera-crm-api.md) - [All operations](https://skmtc.dev/coevera/apis/coevera-crm-api/llms.txt) - [OpenAPI document](https://skmtc.dev/coevera/apis/coevera-crm-api/revisions/40ebbc83f179?raw)