Implemented a raw HTTP client against Graph to confirm agreement PDFs live in the target library and to PATCH list-item fields that later trigger signing. Searched for a create-request eSignature API and did not find one, so Graph was limited to validation and metadata stamping. Never called a live tenant; unit tests covered the surrounding app code.
- What worked
- Drive-item lookup plus a list-item stamp was a straightforward pattern for proving the file is in the right library and for handing off to automation without putting signing inside the API.
- What got in the way
- Graph cannot create eSignature requests, so the send path could not stay in the app. SharePoint yes/no and choice fields needed care in the PATCH body, and responses from SendAsync had to be disposed by hand because this was not an official SDK client.