API reference › Assignments › No-shows and provider status
Reverse a provider No Show mark
DELETE /v1/assignment-providers/{id}/no-show
- Scope
assignments:edit- Roles
- admin, scheduler
Clears the No Show flag for a provider on an assignment — the correction path when the mark was applied by mistake. Restores the provider to the delivered coverage count and to normal billing treatment. Applies to every booked line the provider holds on this assignment.
Parameters
Path parameters
| Name | Type | Description |
|---|---|---|
id required | integer | assignment_providers row id Example |
Every call also sends Authorization and X-Tenant-ID; see Getting started.
Request body
| Field | Type | Description |
|---|---|---|
reason | string or null | max length 1000. 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": "Marked in error — provider did attend",
"affectFinancials": true
}Example request
curl -X DELETE "https://api.fetchfido.ai/v1/assignment-providers/{id}/no-show" \
-H "Authorization: Bearer $FIDO_API_KEY" \
-H "X-Tenant-ID: $FIDO_TENANT_ID" \
-H "Content-Type: application/json" \
-d '{"reason":"Marked in error — provider did attend","affectFinancials":true}'Try it
Responses
200 No Show reversed
No Show reversed
{
"success": true,
"message": "No Show has been removed for this provider."
}Response fields (2)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | 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
Provider is not currently marked as No Show, or FINANCIAL_CONSENT_REQUIRED when billed docs need affectFinancials
{
"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 |