---
title: "peripheralManager(_:didReceiveWrite:)"
framework: corebluetooth
role: symbol
role_heading: Instance Method
path: "corebluetooth/cbperipheralmanagerdelegate/peripheralmanager(_:didreceivewrite:)"
---

# peripheralManager(_:didReceiveWrite:)

Tells the delegate that a local peripheral device received an Attribute Protocol (ATT) write request for a characteristic with a dynamic value.

## Declaration

```swift
optional func peripheralManager(_ peripheral: CBPeripheralManager, didReceiveWrite requests: [CBATTRequest])
```

## Parameters

- `peripheral`: The peripheral manager that received the request.
- `requests`: A list of one or more doc://com.apple.corebluetooth/documentation/CoreBluetooth/CBATTRequest objects, each representing a request to write the value of a characteristic.

## Discussion

Discussion In the same way that you respond to a read request, each time you receive this callback, call the respond(to:withResult:) method of the CBPeripheralManager class exactly once. If the requests parameter contains multiple requests, treat them as you would a single request—if you can’t fulfill an individual request, you shouldn’t fulfill any of them. Instead, call the respond(to:withResult:) method immediately, and provide a result that indicates the cause of the failure. When you respond to a write request, note that the first parameter of the respond(to:withResult:) method expects a single CBATTRequest object, even though you received an array of them from the peripheralManager(_:didReceiveWrite:) method. To respond properly, pass in the first request of the requests array.

## See Also

### Receiving Read and Write Requests

- [peripheralManager(_:didReceiveRead:)](corebluetooth/cbperipheralmanagerdelegate/peripheralmanager(_:didreceiveread:).md)