Authentication & Environments
Understand Bearer tokens, scopes, test/live environments, and idempotency for write operations.
Bearer Token
- All public endpoints use Authorization: Bearer <token>.
- Only a hash of the token is stored. The raw token is shown once during creation or rotation.
- Missing tokens return UNAUTHORIZED (401).
1curl --request GET \2--url 'https://redditfind.ai/api/open/v1/usage' \3--header 'Authorization: Bearer rf_test_xxx'
OpenClaw Skill Auth
- If the caller is AI / OpenClaw, use the CLI auth bridge: skill-auth/start -> approve -> poll -> exchange.
- The browser only handles one login and approval. The CLI then completes polling, token exchange, and secure storage automatically.
- This layer avoids manual token copying and lets AI centralize timeout, retry, and revoke handling.
Environments
- Test tokens use the rf_test_ prefix and are ideal for integration, SDK development, and internal validation.
- Live tokens use the rf_live_ prefix and are intended for external production traffic.
- Use separate test and live keys across different systems and deployment environments.
Scopes
Read the current token identity and environment information.
Rotate or revoke the current integration credential.
List existing API keys for the current account.
Create, rotate, or revoke a specific API key.
Read Community Discovery jobs and results.
Create and cancel Community Discovery jobs.
Read Community Overview jobs and results.
Create and cancel Community Overview jobs.
Read monitoring jobs and hit results.
Create, enable/disable, and delete monitoring jobs.
Read the usage summary.
Idempotency
Use a stable business-side unique value such as a ticket ID, user action ID, or request UUID.
- Always send Idempotency-Key with POST write operations.
- When network retries or duplicate submissions happen, the server prefers reusing the existing job.
- Community Discovery and Community Overview already support idempotent reuse.