Remove me.
If you are using the legacy Adobe Sign SOAP APIs, we highly recommend migrating your apps to consume the v6 REST APIs. The list below shows the SOAP endpoints with their REST equivalents. Both endpoints link directly to the full method description. * General-purpose Methods * Document Methods * Status Methods * User Methods * Web Form Methods * Test Methods * Deprecated Methods
## General-purpose Methods: | SOAP Endpoint | REST Endpoint | | :— | :—- | | getBaseUris | /baseUris, GET |
Note: Base URIs: API calls starting v5 of REST API must be made on a specific base URL obtained either from the api_access_point returned from the OAuth workflow or by making a call to the GET /baseUris
endpoint.
x-api-user
. Files are specified through /transientDocuments.POST /agreements/{agrId}/views
endpoint for the interactive behavior.| SOAP Endpoint | REST Endpoint | | :— | :—- | | createLibraryDocumentInteractive | /libraryDocuments/{libraryDocumentId}, POST |
POST /agreements/{agrId}/views
endpoint for the interactive behavior.| SOAP Endpoint | REST Endpoint | | :— | :—- | | removeDocument | /agreements/{agrId}/documents, DELETE |
DELETE /agreements/{agrId}/documents
endpoint; and to remove it from Manage Page(GET /agreements), use PUT /agreements/{agrId}/visibility
getDocumentInfo
, getDocuments
, getAuditTrail
etc. work on documentKeys
, which can be an ID for an agreement, widget, or library document. The REST API demarcates these as separate resources (cleaner design and strongly typed) and hence, based on the kind of resource you are working on, there is a corresponding /libraryDocuments, /widgets to these. Example: /widgets/{widgetId}, GET
will getDocumentInfo for widgetId
, and similarly for documents, audit trail, etc.externalId
can be used to map your internal IDs to Adobe Sign IDs.| SOAP Endpoint | REST Endpoint | | :— | :—- | | verifyUser | /users/{userId}, GET|
The REST equivalent can be used to see if the user exists, but does not support password verification.
| SOAP Endpoint | REST Endpoint | | :— | :—- | | searchUserDocuments | TBD |
| SOAP Endpoint | REST Endpoint | | :— | :—- | | getDocumentEventsForUser | /agreement/{agrId}/events, GET |
| SOAP Endpoint | REST Endpoint | | :— | :—- | | getEmbeddedView | /agreements/{agrId}/views, POST |
Use the name = DOCUMENT to get the embedded view of an agreement.
Use x-api-user
for specifying the user whose agreements are to be retrieved.
Use x-api-user
for specifying the user whose library documents are to be retrieved.
| SOAP Endpoint | REST Endpoint | | :— | :—- | | getWidgetsForUser | /widgets, GET |
x-api-user
for specifying the user whose widgets are to be retrieved.groupId
in the request.| SOAP Endpoint | REST Endpoint | | :— | :—- | | createPersonalEmbeddedWidget | v5 REST Only /widgets/{widgetId}/personalize, PUT |
| SOAP Endpoint | REST Endpoint | | :— | :—- | | personalizeEmbeddedWidget | /widgets, POST |
INACTIVE
.Use status value as ACTIVE
.
SOAP Endpoint | REST Endpoint |
---|---|
personalizeEmbeddedWidget | /widgets, POST |
### Document Methods: | SOAP Endpoint | REST Endpoint | | :— | :—- | | initiateInteractiveSendDocument | /agreements/{agrId}/views, POST |
### Status Methods: | SOAP Endpoint | REST Endpoint | | :— | :—- | | getDocumentUrlByVersion | /agreement/{agreementID}/combinedDocument/url, GET |
| SOAP Endpoint | REST Endpoint | | :— | :—- | | getLatestDocumentUrl | `/agreements/{agrId}/documents/{docId}/url, GET <>`__/agreements/{agrId}/combinedDocument/url, GET |