NEW! Core Signature Service

Manoj K M
Manoj K M E Member
edited August 26, 2024 in Thrust Services #1

Recently posted to Developer Announcements….

Core Signature Service comprises several APIs that enable developers to easily embed electronic signing into new or existing applications, including the ability to easily prepare, review, send for signature, collect, and manage signed documents.

Learn more about Core Signature Service

Sign up for a free trial!

Tagged:

Comments

  • Hi @Manoj K M & team , I have signed up for free trial subscription of Core Signature. While calling document api to create document from content, getting Server error 500 as response. And while calling document api to create document from url, getting error as { "non_field_errors": [ "File name cannot contain the following special characters: '=' and '@'" ]}. Can you please guide on how to proceed further.

  • Manoj K M
    Manoj K M E Member
    edited August 20, 2024 #3

    Hi @Mrudhula ,

    For the file name we have restrictions, we are not allowing '=' and '@' characters in the file name,
    So, "non_field_errors" we get when the file name is having any of these characters.

    500 server error is when the file_from_content is not in proper base64 format, can you please try with this sample file from content in the file attached

  • Dataflow
    Dataflow New User
    edited August 20, 2024 #4

    yes i was also having same issue

  • Thanks a lot @Manoj K M, it is working now. I was giving direct string content instead of base64 format.

  • Mrudhula
    Mrudhula Member
    edited August 20, 2024 #6

    @Manoj K M Is there a way to get review document complete url which is sent in mail. In the signature response there is only document url but i want the complete url from api response where user can sign directly or any public url to view signed document

  • @Manoj K M Is there a way to get public url of signed document for any one just to view it ?

  • Hi @Mrudhula ,

    Yes, there is an option to get the public URL for the signed documents.

    Make a "GET" call for the "Retrieve Doc" API call with the document UUID which is used for creating signature request ( /api/v1/documents/:doc_uuid/ )

    In the response you will get "pdf" : <string>, public url for the signed document (Please note, the url is public for restricted time period of 10 minutes)

  • hi @Dataflow ,

    Were you able to solve the issue with the above-mentioned method?

  • Thanks @Manoj K M for the prompt reply, this is exactly what I needed.

  • Thanks for sharing such a valuable method. I was facing the same issue yesterday.