Common Issues
Issue: “Unauthorized” Error (401)
Possible Causes:- Missing Authorization header
- Incorrect token format
- Token not found in system
- 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
Issue: “Forbidden” Error (403)
Possible Causes:- Token expired
- Token verification failed
- Clock synchronization issue
- 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
- Visit https://jwt.io
- Paste your token in the debugger
- Check the
exp(expiration) claim - 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
- 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
overwriteparameter set tofalse
- Set
overwrite: trueto update existing page - Use different page title
- Verify
parentIdis correct - Check for duplicate pages in the space
Issue: “Not Found” Error (404)
Possible Causes:- Invalid
spaceId - Invalid
parentId - Parent page deleted
- User lacks access to space/parent
- 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
Issue: “Bad Request” Error (400)
Possible Causes:- Missing required fields
- Invalid JSON format
- Empty content
- Invalid markdown
- Special characters not escaped
- 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
Issue: “Internal Error” Error (500)
Possible Causes:- Server-side issue
- Temporary service disruption
- Malformed content causing processing error
- Retry request after brief delay
- Check Atlassian Status page
- Simplify content to isolate issue
- Contact support if persists
Debugging Tips
Test with curl First
Isolate issues from your code by testing with curl:-v flag shows full request/response details.
Enable Verbose Logging
cURL:Validate JSON Payload
Ensure your JSON is valid:Check Token in JWT Debugger
- Visit https://jwt.io
- Paste token to view claims
- Verify expiration (
expclaim) - Check issued at (
iatclaim) - 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: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
- 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:- Check Documentation:
-
Gather Information:
- API endpoint URL
- Request payload (remove token!)
- Response status code
- Response body
- Token expiration date
- License status
-
Contact Support:
- Support Portal: https://yamuno.atlassian.net/servicedesk/customer/portal/2/group/2/create/51
- Include error messages and steps to reproduce
- Attach logs (with tokens removed!)
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
Related Documentation
- API Reference - Endpoint details
- Authentication - Token management
- FAQ - Frequently asked questions
