Health check endpoints
Varmply Backend API (0.1.0)
Varmply API – MVP backend for campaigns, wallets, authentication, and influencer participation.
Common error codes: - NOT_FOUND - Resource not found (404) - VALIDATION_ERROR - Input validation failed (400) - PERMISSION_DENIED - User lacks permission (403) - CONFLICT - Resource conflict (409) - UNAUTHORIZED - Authentication required (401) - INTERNAL_SERVER_ERROR - Unexpected server error (500)
- Mock serverhttps://docs-staging.varmply.com/_mock/openapi/me/notifications
- Local development serverhttp://localhost:3000/me/notifications
- Staging environmenthttps://api-staging.varmply.com/me/notifications
- Production environmenthttps://api.varmply.com/me/notifications
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs-staging.varmply.com/_mock/openapi/me/notifications?limit=50&cursor=2024-01-01T12%3A00%3A00Z' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Notifications retrieved successfully
List of notifications (most recent first)
Unique identifier for the notification
Notification body message
Notification severity level:
- NOTIFICATION_SEVERITY_INFO: Informational notification
- NOTIFICATION_SEVERITY_WARNING: Warning notification requiring attention
- NOTIFICATION_SEVERITY_ERROR: Error notification indicating a problem
Machine-readable reason code for the notification (e.g., INSUFFICIENT_ESCROW)
Reference to the entity that triggered this notification
Whether the notification has been read by the user
ISO timestamp when the notification was marked as read (null if unread)
{ "notifications": [ { … } ], "next_cursor": "2024-01-01T11:00:00Z" }
- Mock serverhttps://docs-staging.varmply.com/_mock/openapi/me/notifications/{id}/read
- Local development serverhttp://localhost:3000/me/notifications/{id}/read
- Staging environmenthttps://api-staging.varmply.com/me/notifications/{id}/read
- Production environmenthttps://api.varmply.com/me/notifications/{id}/read
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://docs-staging.varmply.com/_mock/openapi/me/notifications/notification_123/read \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Notification marked as read successfully
Notification body message
Notification severity level:
- NOTIFICATION_SEVERITY_INFO: Informational notification
- NOTIFICATION_SEVERITY_WARNING: Warning notification requiring attention
- NOTIFICATION_SEVERITY_ERROR: Error notification indicating a problem
Machine-readable reason code for the notification (e.g., INSUFFICIENT_ESCROW)
Reference to the entity that triggered this notification
ISO timestamp when the notification was marked as read (null if unread)
{ "id": "notification_123", "title": "Earnings Blocked", "body": "Your earnings of $10.00 for submission submission_abc were blocked due to insufficient campaign escrow.", "severity": "NOTIFICATION_SEVERITY_WARNING", "reason_code": "INSUFFICIENT_ESCROW", "entity_ref": { "type": "ACCURUAL", "id": "accrual_xyz" }, "is_read": true, "read_at": "2024-01-01T12:05:00Z", "created_at": "2024-01-01T12:00:00Z" }
- Mock serverhttps://docs-staging.varmply.com/_mock/openapi/me/notifications/read-all
- Local development serverhttp://localhost:3000/me/notifications/read-all
- Staging environmenthttps://api-staging.varmply.com/me/notifications/read-all
- Production environmenthttps://api.varmply.com/me/notifications/read-all
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://docs-staging.varmply.com/_mock/openapi/me/notifications/read-all \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "success": true }