Update a Client Match
Update an existing match between the specified client and another client.
This endpoint updates an existing match object between two clients, allowing modifications to priorities, due dates, group, and status.
Example Request:
curl "https://<your-agency>.smartmatchapp.com/api3/clients/<client_id>/matches/<match_id>/" \
-u <token>: \
-X PUT \
-F group=2 \
-F client_priority=7 \
-F match_priority=5 \
-F client_due_date="2024-05-01" \
-F match_due_date="2024-06-01" \
-F status=1 \
-F client_status=2 \
-F match_status=3
Form Fields:
group: (Optional) The group ID this match is associated with.
client_priority: (Optional) Priority level for the client in this match.
match_priority: (Optional) Priority level for the match client.
client_due_date: (Optional) Due date for the client in this match.
match_due_date: (Optional) Due date for the match client.
status: (Optional) The status ID for this match.
client_status: (Optional) The status ID for the client in this match.
match_status: (Optional) The status ID for the match client.
Example Success Response:
HTTP 204 No Content
Rate Limits:
5 requests within 10 seconds
Error Responses:
| 400 | Bad Request |
Validation errors, |
| 401 | Unauthorized |
This error occurs when the <token> is missing, invalid, or the API access is disabled. Possible errors: "not authenticated" or "token is disabled" or "Agency API is disabled" |
| 404 | Not Found |
This error occurs if the client or the specified match with the ID does not exist. |
| 405 | Method Not Allowed |
This error occurs if an HTTP method other than PUT is used (e.g., POST or GET). |
| 429 | Too Many Requests |
This error occurs when the client has sent too many requests in a given amount of time, leading to rate limiting by the server. Possible errors: "too many requests" |
| 500 | Server Error |
Possible errors: "Internal server error" |