Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Documenso
  3. Error 500 when adding a signature field via Documenso API

Error 500 when adding a signature field via Documenso API

Scheduled Pinned Locked Moved Documenso
2 Posts 2 Posters 162 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    alanlg
    wrote on last edited by
    #1

    Hello everyone,

    I am currently experiencing an issue with the Documenso API when attempting to add a signature field to a document. Here are the details:

    Context:
    • Application: Documenso
    • Objective: Add a signature field to a document via the API

    Issue encountered:
    When I perform a POST request to the /api/v1/documents/{documentId}/fields endpoint to add a signature field, the server returns a 500 error with the message {"message": "Something went wrong"}.

    Request details:
    • Method: POST
    • Endpoint: https://mywebsite.com/api/v1/documents/{documentId}/fields
    • Headers:
    • Authorization: {mytoken}
    • Content-Type: application/json
    Body :
    {
    "recipientId": 21,
    "type": "SIGNATURE",
    "pageNumber": 0,
    "pageX": 100,
    "pageY": 200,
    "pageWidth": 150,
    "pageHeight": 50
    }

    Steps already taken:
    1. Log verification: I have checked the application logs, but no relevant information regarding this error is present.
    2. Environment variable modification: I added the LOG_LEVEL=debug variable to obtain more detailed logs, without success.
    3. Request testing: I have tried with simplified payloads and ensured that the recipientId and documentId are correct, but the error persists.

    If anyone has encountered this issue or has suggestions on how to resolve it, I would greatly appreciate your assistance.

    Thank you in advance for your support.

    Best regards,

    Alan LG

    1 Reply Last reply
    0
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote on last edited by nebulon
      #2

      Seems like an app internal issue, but maybe some packaging side-effect, hard to tell without any server side logs.

      Are you able to create signature fields using the UI itself?

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Bookmarks
      • Search