Base URL
https://rendery3d.com/api/enterprise/v1Authentication
Send your API key in the Authorization header using Bearer format.
Authorization: Bearer r3d_live_xxxxxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxQuickstart
First call /me to validate auth and scope, then call generation endpoints.
curl -X GET "https://rendery3d.com/api/enterprise/v1/me" \
-H "Authorization: Bearer $RENDERY3D_API_KEY"Scopes
usage:readamazon:listing-images:writeamazon:listing-copy:write
Endpoints
GET /api/enterprise/v1/me
Required scope: usage:read
Verify your key, account tier, subscription, and credit context.
POST /api/enterprise/v1/amazon/listing-images
Required scope: amazon:listing-images:write
Main product endpoint for generating listing images from source photos.
POST /api/enterprise/v1/amazon/listing-copy
Required scope: amazon:listing-copy:write
Generate Amazon-optimized listing copy in structured fields.
Error Handling
400invalid request payload401missing/invalid/revoked key402insufficient credits403missing scope or plan access429per-key rate limit exceeded500/502internal or provider failure
Security Checklist
- Keep API keys server-side only and store them in a secret manager.
- Rotate keys on a fixed schedule and revoke keys on service ownership changes.
- Use least-privilege scopes for each integration.
- Send
x-request-idfor traceability in logs.