Securely authenticate your requests using JWT bearer tokens issued through our API key system.
Authentication required for all production endpoints • 1000 requests per hour
Use a JWT bearer token obtained from your Open Guestbook dashboard to authenticate all API requests.
Generate a new API key from the dashboard. Keys include write and read scopes.
Attach your token to all requests. Example format in HTTP headers:
Authorization: Bearer YOUR_API_KEY
fetch('https://api.openguestbook.tech/v1/entries', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_TOKEN_HERE',
'Content-Type': 'application/json'
},
body: JSON.stringify({ message: "Great service!" })
})
curl -X POST 'https://api.openguestbook.tech/v1/entries' \\
-H 'Authorization: Bearer YOUR_API_KEY' \\
-H 'Content-Type: application/json' \\
-d '{"message": "My new guestbook entry"}'
Use environment variables for keys in production. Never commit tokens to source code or public repositories.
Rotate credentials every 90 days. Regenerate any leaked or compromised tokens immediately.
Assign only required permissions to each key. Separate staging and production credentials.
Track API usage patterns through the dashboard. Set alerts for abnormal activity.
Tokens are valid indefinitely until manually revoked. Best practice is to rotate every 90 days.
All requests using the revoked token will be denied with 401 Unauthorized status.
Rate limits reset hourly. API keys get 1000 requests per hour by default, with plans offering higher tiers.