Email the responsible party for signature (write scope)
Sends the rendered SS-4 to the responsible party to sign. They sign under penalties of perjury as the person named on line 7a — Cherry is only the third-party designee and can never be the signer.
signerEmail is resolved to a person Cherry already knows: the address must belong to a workspace member or trusted contact, AND the name Cherry holds for that address must be the responsible party named on the form. A colleague cannot be nominated in their place. signerName is optional and treated as a confirmation; if it disagrees with the record the request is refused rather than overridden.
The signing link is never returned. It is a bearer credential — anyone holding it can sign — so it is mailed to the recipient and nowhere else. Poll the application’s status to see when it has been signed.
Authorizations
Cherry API key, created in the app. Sent as Authorization: Bearer ck_live_….
Path Parameters
EIN application id, from listEinApplications or the incorporation response.
Body
Response
The form is out for signature