# Get envelope details Returns the full details of a specific envelope, including document data, party information, field data, and envelope history. Endpoint: GET /envelopes/{envelope_fingerprint} Version: 1.0.0 Security: basicAuth ## Path parameters: - `envelope_fingerprint` (string, required) Unique identifier of the envelope. ## Response 200 fields (application/json): - `envelope_fingerprint` (string, required) Unique identifier for the envelope. Example: "584ea8b41b0d4c17a96b967433b211e6" - `envelope_title` (string, required) The title of the envelope. Example: "Another Test" - `envelope_status` (string, required) Current status of the envelope. [See Envelope status values for more info →](../../envelope-status) Enum: "processing", "failed", "draft", "sent", "signed", "cancelled", "expired", "rejected", "verify" - `envelope_redirect_url` (string, required) Redirect URL after signing. Empty string if not set. - `envelope_created` (string, required) Timestamp when the envelope was created (ISO 8601). Example: "2025-07-07T11:30:27+0000" - `envelope_sent` (string,null, required) Timestamp when the envelope was sent. Null if not yet sent. - `envelope_processed` (string,null, required) Timestamp when the envelope was processed. Null if not yet processed. - `envelope_all_at_once_enabled` (boolean, required) If true, the envelope is sent to all parties at the same time. If false, the envelope is sent to parties one at a time, starting with the first. For more info on "One at a time" signing sequence, see [Setting the signing sequence](https://help.signable.app/article/191-setting-the-signing-sequence) Example: true - `envelope_requires_otp` (boolean, required) Whether a one-time-password (OTP) verification is enabled for this envelope. For more info on OTPs, see [Enabling Two-Factor Authentication for Signers](https://help.signable.app/article/208-adding-a-one-time-password-to-an-envelope) - `http` (integer, required) HTTP status code of the response. Example: 200 - `envelope_parties` (array, required) - `envelope_parties.party_id` (string, required) Unique identifier for the party in the envelope. Example: "45631119" - `envelope_parties.party_title` (string, required) Label for the party, typically their name. Example: "Abby Signable" - `envelope_parties.party_mobile_last4` (string,null, required) Last 4 digits of the party’s mobile number (if OTP is enabled). - `envelope_parties.party_password` (string,null, required) Password assigned for accessing the envelope, if applicable. Example: "Test123" - `envelope_parties.contact_id` (string, required) ID of the contact linked to the party. Example: "17225983" - `envelope_parties.contact_email` (string, required) Email address of the party. Example: "abby@signable.co.uk" - `envelope_parties.party_status` (string, required) Status of the party's signing progress. Enum: "pending", "in progress", "signed" - `envelope_parties.party_signature_type` (string, required) Indicates how the party will sign the envelope. Only value is supported. Example: "remote" - `envelope_parties.party_role` (string, required) Role of the party, they are either a signer or they are copied into the document with read-only permission. Enum: "signer", "copy" - `envelope_documents` (array, required) - `envelope_documents.document_fingerprint` (string, required) Unique identifier for the document. Example: "8ab4248168761318178b5c747c643a27" - `envelope_documents.document_title` (string, required) Title of the document. Example: "Sample Tenancy Contract" - `envelope_documents.document_page_total` (string, required) Total number of pages in the document. Example: "2" - `envelope_documents.document_pdf_url` (string, required) Direct download link to the original PDF. Example: "https://docs.signable.co.uk/original/8ab4248168761318178b5c747c643a27.pdf" - `envelope_documents.document_thumbnails` (array, required) List of thumbnail image URLs for the document pages. Example: ["https://docs.signable.co.uk/small/8ab4248168761318178b5c747c643a27-0.jpg","https://docs.signable.co.uk/small/8ab4248168761318178b5c747c643a27-1.jpg"] - `envelope_documents.document_pages` (array, required) List of full-size image URLs for the document pages. Example: ["https://docs.signable.co.uk/large/8ab4248168761318178b5c747c643a27-0.jpg","https://docs.signable.co.uk/large/8ab4248168761318178b5c747c643a27-1.jpg"] - `envelope_documents.document_fields` (array, required) List of fields assigned to parties in the document. - `envelope_documents.document_fields.field_id` (string, required) Unique identifier for the field. Example: "452902787" - `envelope_documents.document_fields.field_title` (string, required) The label or title of the field. Example: "First Name" - `envelope_documents.document_fields.field_type` (string, required) Type of the field. Signature fields are not returned. Enum: "text", "date", "checkbox", "upload", "dropdown" - `envelope_documents.document_fields.field_value` (string, required) Value filled in the field. May be empty. Example: "Abby Sackson" - `envelope_documents.document_fields.party_id` (string, required) ID of the party this field is assigned to. Example: "45631119" - `envelope_documents.document_fields.field_merge` (string,null) Merge field label used to pre-fill values. Example: "Sender Name" - `envelope_signed_pdf` (string,null) Direct download link to the signed PDF (if the envelope is signed). - `envelope_history` (array, required) - `envelope_history.history_detail` (string, required) Description of the event that occurred. Example: "Sent the envelope to Abby Signable (abby@signable.co.uk) for signing" - `envelope_history.history_ip` (string, required) IP address from where the action was triggered. Example: "147.147.97.34" - `envelope_history.history_user_agent` (string, required) Browser or device info from where the event occurred. Example: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36" - `envelope_history.history_date` (string, required) Date and time when the event occurred. Example: "2025-07-08T15:02:48+0000" - `envelope_meta` (object) Optional metadata to associate with the envelope. These key-value pairs are stored by Signable and returned in the response and all envelope related webhooks. Useful for attaching internal IDs, status flags, tags, or any contextual information relevant to your system. Example: {"internal_id":"ABC123","VIP":false}