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

# Record a revision-notification decision on a sent PO

> Records the operator's decision on the revision-notification prompt for a
purchase order that has been edited after it was sent to the vendor.

Currently only supports the `skip` action -- the operator dismisses the
prompt without re-emailing the vendor. The send path is handled by
`POST /purchase-orders/{id}/send-to-vendor` with the body field
`template_key_override='po_revised'`.

On success, stamps `last_notified_revision = revision_count` so the
amber revision banner on PO detail clears, and records a
`po_revised_vendor_skipped` activity entry plus a
`purchase_order.revised_skipped` broadcast.

Rule 25: this endpoint is wired in both the API-key dispatch and the
Cognito-JWT dispatch -- API key callers and dashboard callers reach the
same canonical handler.

<Note>Required API key scope: `purchasing:write`</Note>




## OpenAPI

````yaml /openapi.yaml post /purchase-orders/{id}/notify-revision
openapi: 3.1.0
info:
  title: Arcus ERP Public API
  version: 1.0.0
  description: >
    Arcus ERP public REST API. Designed for external integrations and data
    migration.


    **Authentication.** Bearer token (API key) via the `Authorization` header.

    Format: `Authorization: Bearer ark_live_ent_<code>_<random>` (or
    `ark_test_*` for sandbox).

    API keys are issued per-entity in **Settings > Developers > API Keys**.


    **Entity scoping.** The entity is encoded in the API key prefix; routes are
    flat

    (e.g. `/v1/accounts`, `/v1/orders`, `/v1/products`). A small set of platform
    endpoints

    (migration, reconciliation, events, webhook endpoints, API keys) use the

    `/v1/entities/{entity_id}/...` form -- those are noted in their tags.


    **Key capabilities.**
      - Related-resource hydration via `?expand[]=` (see `x-arcus-expand` on each resource).
      - Cursor-based pagination (`starting_after` / `ending_before` / `limit`).
      - Idempotency via the `Idempotency-Key` header.
      - Webhook events for asynchronous notification.
      - Conditional requests / ETag for cache validation.
servers:
  - url: https://api.arcuserp.com/v1
    description: Arcus ERP API (accepts both live `ark_live_*` and test `ark_test_*` keys)
  - url: https://dev-api.arcuserp.com/v1
    description: >-
      Dev sandbox API (test-only data, accepts `ark_test_*` keys against dev
      RDS)
security: []
paths:
  /purchase-orders/{id}/notify-revision:
    parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
          format: uuid
    post:
      tags:
        - Purchasing
      summary: Record a revision-notification decision on a sent PO
      description: >
        Records the operator's decision on the revision-notification prompt for
        a

        purchase order that has been edited after it was sent to the vendor.


        Currently only supports the `skip` action -- the operator dismisses the

        prompt without re-emailing the vendor. The send path is handled by

        `POST /purchase-orders/{id}/send-to-vendor` with the body field

        `template_key_override='po_revised'`.


        On success, stamps `last_notified_revision = revision_count` so the

        amber revision banner on PO detail clears, and records a

        `po_revised_vendor_skipped` activity entry plus a

        `purchase_order.revised_skipped` broadcast.


        Rule 25: this endpoint is wired in both the API-key dispatch and the

        Cognito-JWT dispatch -- API key callers and dashboard callers reach the

        same canonical handler.


        <Note>Required API key scope: `purchasing:write`</Note>
      operationId: notifyRevisionPurchaseOrderV1
      parameters:
        - name: Idempotency-Key
          in: header
          required: false
          schema:
            type: string
            maxLength: 255
          description: Optional idempotency key for safe retries (Stripe-style).
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - action
              properties:
                action:
                  type: string
                  enum:
                    - skip
                  description: >
                    The operator's choice. `skip` records the dismissal and
                    clears

                    the amber banner without sending a revision email. (The
                    `send`

                    path is handled by `POST
                    /purchase-orders/{id}/send-to-vendor`

                    with `template_key_override='po_revised'`.)
      responses:
        '200':
          description: Revision-notification decision recorded.
          content:
            application/json:
              schema:
                type: object
                properties:
                  skipped:
                    type: boolean
                  revision_count:
                    type: integer
                    description: >-
                      The PO's current revision_count (now equal to
                      last_notified_revision).
        '400':
          description: Bad request -- `action` missing or not `skip`.
          content:
            application/json:
              schema:
                $ref: '#/components/responses/Error'
        '401':
          $ref: '#/components/responses/Error'
        '403':
          $ref: '#/components/responses/Error'
        '404':
          description: Purchase order not found for this entity.
          content:
            application/json:
              schema:
                $ref: '#/components/responses/Error'
      security:
        - ApiKeyAuth: []
components:
  responses:
    Error:
      description: Error response (400/401/403/404/409/422/429/500)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorEnvelope'
  schemas:
    ErrorEnvelope:
      type: object
      description: |
        Canonical error response envelope. All API errors use this shape.
      required:
        - error
        - code
      properties:
        error:
          type: string
          description: Machine-readable error key
          example: not_found
        code:
          type: string
          description: Machine-readable error code (often same as error)
          example: not_found
        type:
          type: string
          enum:
            - validation_error
            - permission_error
            - not_found
            - conflict
            - rate_limit
            - internal
            - expand_error
            - not_implemented
          example: not_found
        hint:
          type: string
          description: Human-readable one-sentence explanation (English)
          example: >-
            The requested order does not exist or does not belong to this
            entity.
        param:
          type: string
          description: The parameter that caused the error, if applicable
          example: expand[0]
        required:
          type: string
          description: The scope required (only on insufficient_scope errors)
          example: accounts:read
        request_id:
          type: string
          description: >-
            Unique request ID for support tracing (maps to CloudWatch log
            stream)
          example: req_abc123
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: |
        API key issued per entity via Settings > Developers > API Keys.
        Each key carries scopes (e.g. orders:read, products:write).
        Bearer token format: Authorization: Bearer ark_live_ent_<code>_<random>
        Test keys use ark_test_ent_<code>_<random>. Both are issued per entity
        via Settings > Developers > API Keys.

````