API Reference
All endpoints use HTTPS and require a valid API key in the Authorization header. See
Authentication for details.
The API is split into two resource groups:
- Content API - list, create, update, and delete portfolio content
Base URL
https://api.oscarrondon.com/v1
Endpoint Overview
| Method | Path | Description |
|---|---|---|
| GET | /v1/content |
List content items |
| POST | /v1/content |
Create content |
| PUT | /v1/content/{id} |
Update content |
| DELETE | /v1/content/{id} |
Delete content |
| GET | /v1/users |
List users |
| POST | /v1/users |
Create user |
| PUT | /v1/users/{id} |
Update user |
| DELETE | /v1/users/{id} |
Delete user |
Error Codes
The API uses standard HTTP status codes. Error responses include a message field with a
human-readable description.
| Code | Name | Description |
|---|---|---|
400 |
Bad Request | Invalid or malformed request parameters. |
401 |
Unauthorized | Missing or invalid API key. |
404 |
Not Found | The requested resource does not exist. |
422 |
Unprocessable | Request body failed validation. Check the errors field for details. |
429 |
Rate Limited | Too many requests. Respect the Retry-After response header. |
500 |
Server Error | Internal server error. If the issue persists, contact support. |