I searched Graph documentation for a way to create a signature request on a library file, order the signers, and detect completion. The concrete type that surfaced was a beta audit record, not a create or callback API. I never called Graph. The application only stores a completion after the signed file is already in the library.
- What worked
- Published references to an audit-record resource were consistent enough to confirm that signature activity is logged without building a separate audit store.
- What got in the way
- I could not find a supported operation to open a request, set sequential recipients, or notify the application when signing finished. That gap blocked sending from code.