evernote-common-errors

Diagnose and fix common Evernote API errors. Use when encountering Evernote API exceptions, debugging failures, or troubleshooting integration issues. Trigger with phrases like "evernote error", "evernote exception", "fix evernote issue", "debug evernote", "evernote troubleshooting". allowed-tools: Read, Write, Edit, Grep version: 1.0.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io>

v1.0.0

Jeremy Longshore

MIT

Allowed Tools

No tools specified

Provided by Plugin

evernote-pack

Claude Code skill pack for Evernote (24 skills)

saas packs v1.0.0

View Plugin

Installation

This skill is included in the evernote-pack plugin:

/plugin install evernote-pack@claude-code-plugins-plus

Click to copy

Instructions

# Evernote Common Errors ## Overview Comprehensive guide to diagnosing and resolving Evernote API errors, including EDAMUserException, EDAMSystemException, and EDAMNotFoundException. ## Prerequisites - Basic Evernote SDK setup - Understanding of Evernote data model ## Error Types Evernote uses three main exception types: | Exception | When Thrown | |-----------|-------------| | `EDAMUserException` | Client error - invalid input, permissions | | `EDAMSystemException` | Server error - rate limits, maintenance | | `EDAMNotFoundException` | Resource not found - invalid GUID | ## EDAMUserException Errors ### BAD_DATA_FORMAT **Cause:** Invalid ENML content or malformed data ```javascript // Error { errorCode: 1, // BAD_DATA_FORMAT parameter: 'Note.content' } // Common causes and fixes: // 1. Missing XML declaration // Wrong: '

Hello

' // Correct: `

Hello

` // 2. Forbidden HTML elements // Wrong: contains ` // Correct: remove scripts `

Content only

` // 3. Unclosed tags // Wrong: '

Hello
' // Correct: '

Hello

' ``` **Fix:** Validate ENML before sending: ```javascript function validateENML(content) { const errors = []; // Required declarations if (!content.includes('')) { errors.push('Missing root element'); } // Forbidden elements const forbidden = [ /