Retrieves DocuSign signer status for each recipient on a transaction.
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Path Parameters
Unique identifier assigned when the Order Entry transaction is created. Resolves to the internal transaction; caller must be authorized for this transaction.
Example:1064752
Response
application/json
Response
Returns the signer status payload
EsignatureSignerStatusResponse
True when signer status rows were retrieved successfully.
Overall e-signature outcome: InitializationFailed | Signed | Declined | Cancelled | AwaitingAcknowledgment | VendorAcknowledged | VendorAcknowledgmentFailed | ESignatureInternalError | EmailBounced | TwoFactorAuthenticationFailed.
Per-recipient DocuSign status and contact details for the transaction.
Example:{"recipientId":"11306862","signerName":"EE EE1","signerStatus":"Needs to Sign","signerEmail":"anannya.gupta@everglades.com","dateOfAction":"2026-01-12T14:22:00","signerAuthMethod":"Phone","signerCountryCode":"1","signerPhoneNo":"8650827071"}
Show Child Parameters
Authentication
Path Parameters
Submits the Order Entry case for e-signature with the configured signer roster.
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
Case submission payload: transaction to submit and the final DocuSign signer roster (selected auth method per signer).
Transaction (case) identifier to submit for e-signature.
>= 1
Final signer roster with selected auth method and contact details.
>= 1 items
Show Child Parameters
Response
application/json
Response
Returns the case submission result envelope
SaveEsignatureResponse
True when the case was submitted to DocuSign for e-signature.
User-safe confirmation or failure text from the submission result.
Authentication
Body
Cancels the e-signature ceremony for a case (voids the DocuSign envelope and returns the case to Pending upstream).
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
Identifies the case whose e-signature ceremony should be canceled (void DocuSign; case returns to Pending).
String form of the transaction (case) id to cancel; must be a positive integer.
>= 1 characters
Response
application/json
Response
Returns the cancel result envelope
CancelEsignatureCeremonyResponse
True when the DocuSign ceremony was voided and the case returned to Pending upstream.
User-safe message when success is false; may also confirm the outcome when true.
Authentication
Body
Retriggers the DocuSign e-signature email notification for a case (only when e-signature is in progress upstream).
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
Identifies the case whose DocuSign signing notification should be resent (in-progress e-sign only).
String form of the transaction (case) id; must be a positive integer.
>= 1 characters
Response
application/json
Response
Returns the retrigger result envelope
RetriggerEsignatureEmailNotificationResponse
True when the signing notification was retriggered (e-sign in progress upstream).
User-safe message; e.g. notification successfully triggered when success is true.
Authentication
Body
Updates signer email or phone for a case while e-signature is pending upstream.
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
Transaction ID and signer rows with corrected email and/or phone while e-signature is pending upstream.
Transaction (case) identifier whose signer contact details should be updated.
>= 1
Signer rows with corrected email and/or phone while e-sign is pending.
>= 1 items
Show Child Parameters
Response
application/json
Response
Returns the update result envelope
UpdateEsignSignerDetailsResponse
True when signer contact details were updated (e-sign must be pending upstream).
User-safe message confirming the update or describing a failure.