API reference › Assignments › No-shows and provider status
Mark a client as No Show on an assignment
POST /v1/assignment-clients/{id}/no-show
- Scope
assignments:edit- Roles
- admin, scheduler
Records that a client attached to this assignment did not show, without changing the assignment status or detaching the client — the booking record stays intact. The client is moved out of the served count and billed the no-show fee instead of the delivered service. An optional per-client fee can be entered with the mark; client no-show money has no policy fallback, so an omitted fee simply bills nothing.
Parameters
Path parameters
| Name | Type | Description |
|---|---|---|
id required | integer | assignment_client row id Example |
Every call also sends Authorization and X-Tenant-ID; see Getting started.
Request body required
| Field | Type | Description |
|---|---|---|
reason required | string | max length 1000. Example |
noShowFee | number (float) or null | Example |
affectFinancials | boolean or null | Required when a finance document linked to the work item is Sent or Approved; without it the call returns 422 FINANCIAL_CONSENT_REQUIRED. true applies the money side effects and syncs the linked documents; false changes the flag only and marks those documents out of sync. |
Example
{
"reason": "Client did not attend the appointment",
"noShowFee": 75,
"affectFinancials": true
}Example request
curl -X POST "https://api.fetchfido.ai/v1/assignment-clients/{id}/no-show" \
-H "Authorization: Bearer $FIDO_API_KEY" \
-H "X-Tenant-ID: $FIDO_TENANT_ID" \
-H "Content-Type: application/json" \
-d '{"reason":"Client did not attend the appointment","noShowFee":75,"affectFinancials":true}'Try it
Responses
200 Client marked as No Show
Client marked as No Show
{
"success": true,
"message": "Client has been marked as No Show.",
"data": {
"id": "ASG-ZGJ8T2",
"clientId": "CLT-4HD92K",
"isNoShow": true,
"noShowReason": "Client did not attend the appointment",
"noShowFee": 75,
"affectedRows": 1,
"summary": {
"attached": 3,
"noShow": 1,
"served": 2
}
}
}Response fields (13)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
data | object | |
data.id | string | Example |
data.clientId | string | Example |
data.isNoShow | boolean | Example |
data.noShowReason | string | Example |
data.noShowFee | number (float) | Example |
data.affectedRows | integer | Example |
data.summary | object | |
data.summary.attached | integer | Example |
data.summary.noShow | integer | Example |
data.summary.served | integer | Example |
401 Not signed in
Missing, invalid or expired API key.
{
"success": false,
"message": "Invalid API key. Org and user tier keys must send an X-Tenant-ID header naming the organization the key was issued for.",
"errors": null,
"code": "API_KEY_MISSING"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |
403 Not allowed
Unauthorized — admin only
{
"success": false,
"message": "You don't have permission to access this endpoint. This API key is missing the 'assignments:edit' scope.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Always empty on this status. Example |
422 Validation failed
Validation error — missing reason, unknown client record, or client already marked
{
"status": "error",
"message": "Unable to save. Please check the highlighted fields",
"errors": {
"name": [
"Please enter a name."
],
"email": [
"The email has already been taken."
]
}
}429 Too many requests
Rate limit exceeded. See Retry-After.
{
"success": false,
"message": "You've exceeded this API key's rate limit of 120 requests per minute. Try again in 37 seconds.",
"errors": null,
"code": "RATE_LIMITED"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |
500 Server error
Internal server error
{
"success": false,
"message": "An unexpected error occurred — please try again.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | string or null | Null in production. The exception message only when the application runs with debug on, so nothing is leaked to an integrator. |
code | string | Always empty: the server-error response carries no error code. Example |