Skip to main content
The Pxxl CDN API gives your backend direct access to object storage, asset management, and edge analytics. Use it to upload build artifacts, serve static files from edge cache nodes, track monthly bandwidth consumption, and pull proxy traffic logs for security analysis — all without leaving your deployment workflow. This page covers the raw HTTP endpoints. If you would rather use a typed client, jump to the Node SDK or Go SDK. For ready-to-deploy starter projects that already wire up uploads, see Boilerplates.

Endpoints

Upload an Asset

Send a multipart/form-data POST request to upload a file to your storage space. Set visibility to public for files served from edge cache nodes, or private for files accessed via pre-signed URLs.

Check Usage Summary

Query your current storage and bandwidth consumption, along with remaining wallet credits:

Response Shapes

The raw HTTP API returns small envelopes such as { "success": true, "data": ... }. The SDKs unwrap some of those envelopes for convenience.

Summary Response

GET /api/v3/cdn/summary returns account-level CDN storage, traffic, analytics, space status, and cloud-credit state.

Pxxl-managed S3 access keys

Pxxl storage buckets can issue scoped S3-compatible access keys. These keys connect to a bucket managed by Pxxl. They do not import an AWS S3, Cloudflare R2, MinIO, or other external bucket into a project. Create a key for a specific bucket:
The supported permissions are: The response includes the S3-compatible endpoint, region, bucket, path-style setting, access key ID, and secret access key. Store the secret when it is returned and keep it on a server or CI system. Manage keys with these endpoints:
Pxxl does not expose provider bucket names or internal object paths through the regular asset responses. Use the returned connection details and the bucket-scoped permission for a direct S3-compatible client.

Asset Object

List, upload, summary recentAssets, and SDK upload calls return the same safe asset shape. Provider names, bucket names, raw R2 keys, and internal tenant paths are not exposed.

List Assets Response

GET /api/v3/cdn/assets accepts page, limit, search, and kind.
limit is capped at 200. If page or limit is invalid, Pxxl falls back to safe defaults.

Upload Asset Response

POST /api/v3/cdn/assets stores the upload, records usage, charges cloud credits when enabled, and returns the created asset.
If the account lacks enough cloud credits, Pxxl returns 402:

Download and Delete Responses

GET /api/v3/cdn/assets/:id/download returns the raw file bytes, not JSON. Pxxl sets safe headers such as Content-Type, Content-Disposition, X-Content-Type-Options: nosniff, and a locked-down content security policy. DELETE /api/v3/cdn/assets/:id returns:

Usage Response

GET /api/v3/cdn/usage?limit=100 returns recent usage events, recent credit ledger entries, and current credit state. limit is capped at 500.

Get Proxy Logs

Retrieve edge traffic logs and security anomaly events recorded by the Pxxl CDN proxy:
Proxy logs include allowed and blocked request counts, risk index ratings, GeoIP concentration breakdowns, and the top IP sources contributing the highest traffic volumes to your project domains.
If you accidentally expose a CDN upload API key in a client bundle, a public repository, or a build log, rotate it immediately from Dashboard > API Keys. Delete the compromised key, create a replacement with the same CDN upload and read scopes, and update the secret in your backend environment before redeploying.