Download contract audit log
Streams the signing audit trail for a contract request through UrbanPayX,
without exposing the underlying signing-provider URL.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Download the signing audit trail for a completed contract request as a PDF. UrbanPayX fetches the audit log from the signing provider on your behalf and streams the file back inline, so the underlying provider URL is never exposed. The audit log is only available once the contract has been fully signed and completed.
Authentication & access
- Requires a client API token:
Authorization: Bearer <token>. - The caller must hold the
contracts.requests.readpermission and have the OWNER, OPERATIONS, or DEVELOPER role. - Contract signing must be enabled for your client. If it is disabled the request returns
403.
Path parameters
request_id(string, required) — the ID of the contract request whose audit log you want to download. The request must belong to your client.
Preconditions
The contract request must be in the COMPLETED state and have a finalized signing submission. If the contract has not been completed yet, the request returns 409.
Response
200— Returns the audit-log file as a binary stream, not JSON. The content type matches what the signing provider returns (typicallyapplication/pdf), and the response carries aContent-Disposition: inline; filename="contract-{request_id}-audit.pdf"header.
Error responses
| Status | When |
|---|---|
403 | Contract signing is disabled for the client |
404 | No contract request with this request_id exists under your client |
409 | The contract is not completed yet (not in the COMPLETED state or no finalized submission) |
502 | The signing provider returned an invalid response, the audit log is not yet available from the provider, or the file download failed |
503 | The signing provider is not configured, or is temporarily unavailable |
Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.