Initiate the consent flow for a student and guardian
Machine-to-machine entry point for a partner system to start TimeBack’s email consent flow for an explicit student and guardian: generates the DocuSign envelope and emails the guardian an HMAC-protected signing link. Gated on the consent.write scope and the caller owning the student’s org. Returns 400 if the student’s consent is already granted, or if a named guardian has no active relationship to the student.
Authorizations
OAuth 2.0 client credentials flow. Contact timeback@trilogy.com to request credentials for your application.
Path Parameters
Unique identifier of the student
Body
The parent/guardians to request consent from. Each entry carries the guardian's UUID and may optionally carry a corrected legal name.
1URL the guardian's browser is redirected to after they finish signing in DocuSign. Applies to every guardian in this request. Required: the platform hosts no landing page, so the caller must supply where the guardian lands after signing.
Explicit signal that a repeat call is an intentional resend. With the default (false), a repeat call for a guardian who was already emailed reuses the envelope and sends no further email, regardless of elapsed time. Set true to re-email; a forced resend is still debounced by a short server-side window, so a double-click or retry cannot double-send. Applies to every guardian in this request.
Response
Consent request accepted