Comprehensive debugging toolkit for Documenso integrations.
Use when troubleshooting complex issues, gathering diagnostic information,
or creating support tickets for Documenso problems.
Trigger with phrases like "debug documenso", "documenso diagnostics",
"troubleshoot documenso", "documenso support ticket".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Comprehensive debugging toolkit for Documenso integrations.
Use when troubleshooting complex issues, gathering diagnostic information,
or creating support tickets for Documenso problems.
Trigger with phrases like "debug documenso", "documenso diagnostics",
"troubleshoot documenso", "documenso support ticket".
Comprehensive debugging tools for Documenso integration issues. Includes diagnostic scripts, curl debug commands, environment verification, and support ticket templates.
Prerequisites
Documenso SDK installed
Access to logs and configuration
curl and jq available
Instructions
Step 1: Quick Connectivity Test
#!/bin/bashset -euo pipefail
echo"=== Documenso Connectivity Test ==="# 1. Check API key is setif [ -z "${DOCUMENSO_API_KEY:-}" ]; thenecho"FAIL: DOCUMENSO_API_KEY not set"exit 1
fiecho"OK: API key set (${#DOCUMENSO_API_KEY} chars)"# 2. Test authentication
BASE="${DOCUMENSO_BASE_URL:-https://app.documenso.com/api/v1}"
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $DOCUMENSO_API_KEY" \
"$BASE/documents?page=1&perPage=1")
if [ "$STATUS" = "200" ]; thenecho"OK: API authentication successful"elif [ "$STATUS" = "401" ]; then
1
[ = ];
1
LATENCY=$(curl -s -o /dev/null -w \
-H \
)
curl -s -H \
| jq
echo
"FAIL: Invalid API key (401)"
exit
elif
"$STATUS"
"403"
then
echo
"FAIL: Insufficient permissions (403) — try a team API key"