Skip to main content

Common Issues

Issue: “Unauthorized” Error (401)

Possible Causes:
  • Missing Authorization header
  • Incorrect token format
  • Token not found in system
Solutions:
  • Verify header format: Authorization: Bearer YOUR_TOKEN
  • Check token was copied correctly (no extra spaces or line breaks)
  • Ensure token hasn’t been deleted from the system
  • Verify token exists in API Token Management page
Test Command:

Issue: “Forbidden” Error (403)

Possible Causes:
  • Token expired
  • Token verification failed
  • Clock synchronization issue
Solutions:
  • Check token expiration date in token management UI
  • Create new token if expired
  • Verify system clock is synchronized
  • Check JWT token claims using jwt.io
Debug Steps:
  1. Visit https://jwt.io
  2. Paste your token in the debugger
  3. Check the exp (expiration) claim
  4. Compare with current Unix timestamp

Issue: “License Expired” Error (402)

Possible Causes:
  • License was inactive when token was created
  • Token created during trial period that has ended
  • License renewal pending
Solutions:
  • Verify current license status in Confluence settings
  • Create new token with active license
  • Contact admin to renew license
  • Check license expiration date

Issue: “Already Exists” Error (400)

Possible Causes:
  • Page with same title and parent already exists
  • overwrite parameter set to false
Solutions:
  • Set overwrite: true to update existing page
  • Use different page title
  • Verify parentId is correct
  • Check for duplicate pages in the space
Example Fix:

Issue: “Not Found” Error (404)

Possible Causes:
  • Invalid spaceId
  • Invalid parentId
  • Parent page deleted
  • User lacks access to space/parent
Solutions:
  • Verify space exists and ID is correct
  • Confirm parent page ID is valid
  • Check user has access to space/parent
  • Use Confluence API to verify IDs
Verify Space and Page:

Issue: “Bad Request” Error (400)

Possible Causes:
  • Missing required fields
  • Invalid JSON format
  • Empty content
  • Invalid markdown
  • Special characters not escaped
Solutions:
  • Verify all required fields present (spaceId, parentId, pageTitle, content)
  • Validate JSON structure
  • Check content is non-empty string
  • Test markdown syntax
  • Escape special characters in JSON
Validation Example:

Issue: “Internal Error” Error (500)

Possible Causes:
  • Server-side issue
  • Temporary service disruption
  • Malformed content causing processing error
Solutions:
  • Retry request after brief delay
  • Check Atlassian Status page
  • Simplify content to isolate issue
  • Contact support if persists
Retry with Exponential Backoff:

Debugging Tips

Test with curl First

Isolate issues from your code by testing with curl:
The -v flag shows full request/response details.

Enable Verbose Logging

cURL:
Node.js (axios):

Validate JSON Payload

Ensure your JSON is valid:

Check Token in JWT Debugger

  1. Visit https://jwt.io
  2. Paste token to view claims
  3. Verify expiration (exp claim)
  4. Check issued at (iat claim)
  5. Verify signature (if you have the secret)

Inspect HTTP Headers

Make sure headers are correct:

Test with Minimal Content

If you’re getting errors, try with minimal content:

Network Issues

SSL/TLS Certificate Errors

Problem: Certificate verification fails Solution:
Better solution: Fix certificate chain or use proper CA certificates.

Timeout Errors

Problem: Request times out Solution:

Proxy Issues

If behind a corporate proxy:

Performance Issues

Slow Response Times

Possible Causes:
  • Large content size
  • Network latency
  • Server load
Solutions:
  • Reduce content size
  • Split large documents
  • Implement caching
  • Use CDN for assets

Rate Limiting

Problem: Too many requests Solution:

Getting Help

If you’re still experiencing issues:
  1. Check Documentation:
  2. Gather Information:
    • API endpoint URL
    • Request payload (remove token!)
    • Response status code
    • Response body
    • Token expiration date
    • License status
  3. Contact Support:

Diagnostic Checklist

  • Token is valid and not expired
  • License is active
  • Authorization header format is correct
  • All required fields are present
  • JSON payload is valid
  • Content is not empty
  • Space ID exists and is accessible
  • Parent page ID exists and is accessible
  • Network connectivity is working
  • No firewall blocking requests
  • SSL/TLS certificates are valid
  • Using correct API endpoint URL