> 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/deletereceivinginboundshipmentnotification.md).

# Delete Receiving Inbound Shipment Notification

deleteReceivingInboundShipmentNotification Mutation

Audience: Programmer

Deletes an existing `ReceivingInboundShipmentNotification` from the system. Deletion is soft: the `deletedAt` and `deletedBy` fields are set on the underlying record.

## Arguments

| Name | Type  | Description                               |
| ---- | ----- | ----------------------------------------- |
| `id` | `ID!` | Required ID of the notification to delete |

## Return Type

`ReceivingInboundShipmentNotificationDeletePayload!` - Contains information about the deletion operation and associated workflows.

## Response Fields

`ReceivingInboundShipmentNotificationDeletePayload`:

| Field       | Type                 | Description                             |
| ----------- | -------------------- | --------------------------------------- |
| `deletedID` | `ID`                 | ID of the deleted notification          |
| `workflows` | `[TemporalWorkflow]` | Any workflows triggered by the deletion |

## Usage Example

```graphql
mutation {
  deleteReceivingInboundShipmentNotification(id: "550e8400-e29b-41d4-a716-446655440000") {
    deletedID
    workflows {
      id
      type
      runID
      status
    }
  }
}
```

## JavaScript Example

```javascript
const deleteMutation = `
  mutation DeleteReceivingInboundShipmentNotification($id: ID!) {
    deleteReceivingInboundShipmentNotification(id: $id) {
      deletedID
      workflows {
        id
        type
        runID
        status
      }
    }
  }
`;

const variables = {
  id: "550e8400-e29b-41d4-a716-446655440000"
};

const response = await fetch('/graphql', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_TOKEN'
  },
  body: JSON.stringify({ query: deleteMutation, variables })
});

const result = await response.json();
console.log('Deleted notification:', result.data.deleteReceivingInboundShipmentNotification);
```

## Notes

* The notification must exist and be accessible to the current user.
* Deletion is soft: underlying records remain in the database with `deletedAt` and `deletedBy` set. They are excluded from default query results.
* Deletion may trigger downstream Temporal workflows; inspect the `workflows` field in the response to track them.
* Users must have appropriate permissions to delete inbound shipment notifications.


---

# 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/deletereceivinginboundshipmentnotification.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.