Check RCS status
Return the current RCS KYC status for a customer, including the rejection reason and review metadata when present. Designed for cheap polling — only the status fields are returned, not the full document.
GET /api/v1/partner/customers/{customer_id}/rcs/statusResponse — 200 (submission exists)
{
"success": true,
"customer_id": "8f3b2a1e-49d8-4c2d-9e1a-b7e6d5f8a3c2",
"status": "approved",
"rejection_reason": "",
"reviewed_by": "[email protected]",
"submitted_at": "2026-05-20T10:18:42Z",
"reviewed_at": "2026-05-21T07:04:11Z"
}Response — 200 (no submission yet)
{
"success": true,
"customer_id": "8f3b2a1e-49d8-4c2d-9e1a-b7e6d5f8a3c2",
"status": "not_applied",
"message": "No RCS KYC submitted for this customer yet."
}Status values
status | Meaning |
|---|---|
not_applied | No submission exists for this customer — call Apply for RCS |
draft | Partner panel saved a draft; not yet submitted for review |
pending | Submitted; awaiting admin review |
approved | Admin approved — RCS sender is being registered (or already is) |
rejected | Admin rejected — see rejection_reason; re-call apply with a corrected payload |
submitted_at and reviewed_at are zero-valued ("0001-01-01T00:00:00Z")
when they haven’t happened yet.
Errors
| Status | Reason | Response |
|---|---|---|
400 | Invalid customer_id | { "success": false, "message": "Invalid customer_id" } |
401 | Missing or invalid partner auth | { "success": false, "message": "unauthorized" } |
404 | customer_id doesn’t belong to this partner | { "success": false, "message": "Customer not found under this partner" } |
500 | Database error | { "success": false, "message": "Failed to load status" } |
cURL
curl -X GET \
https://api.splashifypro.com/api/v1/partner/customers/$CUSTOMER_ID/rcs/status \
-H "Authorization: Bearer $SPLASHIFY_API_KEY"Notes
- Polling cadence — admin reviews are typically 1–2 business days, so polling more than once every few minutes is wasteful. Prefer webhooks (on the roadmap) where possible.
- Caching — the endpoint hits Scylla directly with no caching; safe to call frequently but please don’t.