Kinds of contributor
Attribution for machine tokens
A machine credential has no user of its own, so by default its writes are attributed to your integration contributor. To attribute a write to a specific person, send thex-pylon-on-behalf-of header with a contributor id (cont_…) or a borrower id (borr_…). This is attribution, not authorization — see Acting on behalf of a user for the full rules. Today it governs the uploader on document uploads.
Where contributors appear
Contributors surface on the records they authored. For example, each document exposes the contributor that uploaded it viauploadedBy:
uploadedBy is an AnyContributor, so you can request the concrete fields of a delegated-borrower contributor (such as the borrowerId it acts for) with an inline fragment:
Managing contributors via the API
The contributor management queries and mutations below are experimental and require the
use:experimental-api scope; their shape may change. createLease is generally available and does not require that scope. Mutations live under the contributor mutation namespace (as shown in the Elements handshake).
All operations are scoped to your own customer. Browse the full contributor schema in the API reference, and see Handling authentication for the
createContributor + createLease handshake Elements uses.
Contributors vs organization users. Organization users are your staff working loans (loan officers, processors, admins) and sign in to the Command Center. Contributors are who an action is attributed to — including borrowers and your integration — and are not organization logins. See Managing organization users.