Getting started
Quickstart
Three steps: create an org, mint a scoped key, then upload or log from your server.
1. Create your account
- Go to app.back2rp.org/register.
- Create an organization for your server or community.
- Open Dashboard → API keys.
2. Create an API key
Pick the scope that matches what you want to do:
| Prefix | Use for | Common endpoints |
|---|---|---|
| cnf_img_ | Images / screenshots | POST /api/v1/upload · /upload/chunked/* |
| cnf_vid_ | Video clips | POST /api/v1/upload · /upload/chunked/* |
| cnf_aud_ | Audio | POST /api/v1/upload · /upload/chunked/* |
| cnf_fil_ | Any file as-is | POST /api/v1/file · /file/chunked/* |
| cnf_log_ | Structured logs | POST /api/v1/logs |
Direct vs large files
Direct multipart works for small bodies. For large media (and for all FiveM video/audio), use chunked uploads or presigned URLs. Maximum size on every path is 100 MB.
Legacy keys
Older
gsk_* keys still work. New keys use cnf_*.3. Upload a file
curl
curl -X POST https://app.back2rp.org/api/v1/upload \
-H "Authorization: Bearer cnf_img_your_key" \
-F file=@screenshot.pngSuccessful uploads return a JSON payload with a public CDN URL you can hotlink (unless the file is pending moderation or hidden).
4. Send a log event
curl
curl -X POST https://app.back2rp.org/api/v1/logs \
-H "Authorization: Bearer cnf_log_your_key" \
-H "Content-Type: application/json" \
-d '[{"name":"connections","level":"info","message":"Player connected","metadata":{"player":"32"}}]'What next?
Read the upload guides, wire up the FiveM resource, or open the interactive API.
