- Get a single EviNotice
- Productionhttps://api.evicertia.com/v2/EviNotice/{Id}
- Pre-production / QAhttps://api.ecertia.com/v2/EviNotice/{Id}
curl -i -X GET \
-u '<username>:<password>' \
'https://api.evicertia.com/v2/EviNotice/{Id}?IncludeAffidavits=true&IncludeAttachments=true'EviNotice retrieved
Current step in the notice lifecycle. Closed is the only terminal state.
None while open. At Closed, the first recorded milestone in this order determines the final outcome: Failed, Rejected, Accepted, Refused, Read, Received, Delivered, Sent, Certified. Received records access to the hosted notice link. Read records opening the hosted content. Cancelled is a compatibility value in the response enum and is not produced by current closure logic.
Timestamp recorded for the Processed milestone. It is populated after initial processing and content certification succeed, but its value is the admission time recorded at submission, so it normally equals SubmittedOn and does not measure processing duration.
Event time reported by the successful notification sending result. For email, this is transmission to the recipient's mail system; for mobile channels, successful transmission reported by the sending channel. This does not certify that the hosted notice was read. Do not infer callback arrival order or require strict numerical timestamp ordering from the logical lifecycle sequence.
Timestamp when the platform, after its initial checks, accepted responsibility for the communication and issued the notification send request to its sending process. It does not confirm successful transmission to the remote system. Dispatch logically precedes the sending result; equal or strictly ordered timestamp values and callback arrival order are not guaranteed.
Email: timestamp when delivery to the recipient's mail system was confirmed — best-effort, may be absent even when the message was delivered. Mobile channels: operator delivery confirmation.
Timestamp when the recipient accessed the protected content on the platform.
Time the notice closed, whatever the reason (including expiry, decision, refusal or failure); not only TimeToLive expiry.
Timestamp when the recipient opened the access link and reached the delivery page on the platform.
Free-text comment provided by the recipient when accepting or rejecting the notice.
Reminder configuration as set at submission. Absent when no reminders were configured.
Channels used to deliver the notification to the recipient.
PIN channel groups configured at submission. Each element lists channels offered for one PIN send, not parallel sends. The first PIN, sent when the recipient requests it, uses the first channel of the first group; no channel choice is offered. On a resend, the recipient chooses one channel from the next group (no choice is shown when that group has a single channel); after the third send, the last group is reused.
Whether the delivery notification email or SMS was successfully transmitted.
Human-readable summary of the transmission result (e.g. bounce or SMTP reply code).
Metadata for each generated affidavit. Present when IncludeAffidavits is true.
{ "Id": "550e8400-e29b-41d4-a716-446655440000", "Subject": "Contract review required", "LookupKey": "CONTRACT-001", "Issuer": "Sender Co.", "IssuerEmail": "sender@example.com", "RecipientAddress": "recipient@example.com", "RecipientDisplayName": "Jane Doe", "RecipientLegalName": "Acme Corp", "State": "Read", "Outcome": "None", "CreationDate": "2026-01-15T09:00:00Z", "LastUpdateDate": "2026-01-16T11:23:00Z", "SubmittedOn": "2026-01-15T09:00:01Z", "ProcessedOn": "2026-01-15T09:00:01Z", "SentOn": "2026-01-15T09:00:10Z", "DispatchedOn": "2026-01-15T09:00:03Z", "DeliveredOn": "2026-01-15T09:15:00Z", "ReceivedOn": "2026-01-16T11:20:00Z", "ReadOn": "2026-01-16T11:23:00Z", "TimeToLive": 10080, "AllowRefusal": false, "NotaryRetention": false, "OnlineRetentionPeriod": 1, "SourceChannel": "Api", "AffidavitKinds": [ "TransmissionResult", "DeliveryResult", "Read" ], "SiteName": "acme-corp", "XmissionResult": true, "XmissionSummary": "250 OK" }