Resend the UrbanPayX-branded signing invitation email to a contract request's current active signer. Use this when a signer reports they never received (or lost) their original invitation. The endpoint re-sends the email to the signer's existing address and signing link, records the new attempt, and returns the updated contract request.

Authentication & access

• Requires a client API token: Authorization: Bearer <token>.
• The caller must hold the contracts.requests.write permission and have the OWNER or OPERATIONS role.
• This is a dashboard-only action. The token must belong to a dashboard user; programmatic (non-user) tokens are rejected with 403.
• Contract signing must be enabled for your client. If it is disabled the request returns 403.

Path parameters

• request_id — the contract request whose signer should be re-invited. Must belong to your client.
• participant_id — the participant (signer) to re-invite. Must belong to the given request.

Preconditions

The targeted participant must be the one who can currently receive an invitation email:

• The contract request must not be in a terminal state (completed, canceled, declined, or expired).
• The participant must not be in a terminal state.
• The participant must be the current active signer on the request. You cannot re-invite a signer whose turn has not yet come or has already passed.
• The signer must use link delivery. Signers configured for other delivery methods cannot receive invitation emails.
• The signer must have both an email address and a signing URL on file.

A precondition failure returns 400.

Rate limiting

A 60-second cooldown applies per signer. If you resend the invitation and then call this endpoint again for the same signer within 60 seconds of the last attempt, the request returns 429. Wait for the cooldown to elapse and retry.

Response

200 — the invitation email was sent. The payload is the updated contract request, reflecting the new send attempt on the targeted participant.

Error responses

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.