> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/mutations/patchpickingoutboundshipmentnotificationdata.md).

# patchPickingOutboundShipmentNotificationData

Apply RFC 6902 JSON Patch operations to the picking outbound shipment notification's data field.

Audience: Programmer

Apply RFC 6902 JSON Patch operations to the picking outbound shipment notification's data field.

**Served by:** [picking](https://docs.pyck.cloud/graphql-api/services/picking.md)

## Arguments

| Name      | Type                                                                                | Default | Description |
| --------- | ----------------------------------------------------------------------------------- | ------- | ----------- |
| `id`      | ID!                                                                                 |         |             |
| `patches` | \[[JSONPatchInput](https://docs.pyck.cloud/graphql-api/inputs/jsonpatchinput.md)!]! |         |             |

## Returns

[PickingOutboundShipmentNotificationOutput](https://docs.pyck.cloud/graphql-api/types/pickingoutboundshipmentnotificationoutput.md)

## Example

Applies RFC 6902 JSON Patch operations to the picking outbound shipment notification's data field. Only changed fields are modified; untouched fields are preserved. See <https://datatracker.ietf.org/doc/html/rfc6902> for the specification.

```graphql
mutation PatchPickingOutboundShipmentNotificationData($id: ID!, $patches: [JSONPatchInput!]!) {
  patchPickingOutboundShipmentNotificationData(id: $id, patches: $patches) {
    eventCount
    pickingOutboundShipmentNotification {
      createdAt
      createdBy
      data
      dataTypeID
      dataTypeSlug
      deletedAt
      deletedBy
      id
      orderID
      tenantID
      updatedAt
      updatedBy
    }
    transactionID
  }
}
```

**Variables**

```json
{
  "id": "<picking outbound shipment notification id to patch>",
  "patches": [
    {
      "op": "REPLACE",
      "path": "/meta/name",
      "value": "\"PatchedNotification\""
    },
    {
      "op": "REPLACE",
      "path": "/sum",
      "value": "42"
    }
  ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/mutations/patchpickingoutboundshipmentnotificationdata.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
