Forums
Guys, We are in the process of setting up accounts and we have a few where Integration is not set. Is feature needed for any account that will have API calls ran against it? I am trying to generate an auth token for one of these users and I am getting this error below.
{
    "messageKey": "http.status.405",
    "technical": "",
    "packageId": null,
    "messageLanguage": null,
    "entity": null,
    "parameters": {},
    "message": "Method Not Allowed",
    "code": 405,
    "name": "Method Not Allowed"
}
Forums
We implemented eSign application to get signature only during signing ceremony.When we create package we added static PDF and this static PDF contains all input information.User need to enter signature only(all other inputs are read only).Now we need to build another application that requires user input before signing document.When we embed eSign signing ceremony URL in iFrame,user needs to enter few other information like Name,age..etc(Editable PDF,not static PDF) and sign the document. Once signing is completed,all fields should be non-editable.
Forums
Guys, We are looking at this page for creating the Auth token for a user. https://docs.esignlive.com/content/c_integrator_s_guide/rest_api/authentication_tokens.htm?Highlight=user%20authentication#Create We have to do a POST request to this api call. /authenticationTokens/user The documentation says that either a Cookie header or an Authorization header is required. I am curious to know, where do we get the value for the SessionId in the cookie example below. Cookie: ESIGNLIVE_SESSION_ID=cdf5b882667d24a2 We are trying to get a user authentication for our Notary so that when they click th