Update Assistant API endpoint returns success but doesn't apply changes
@Jorden Williams @Mike Copeland , hoping you can help with an API issue we're running into. We're using the REST API to manage assistants across multiple GHL subaccounts. The PUT update-assistant endpoint consistently returns {"status": "success"} but the changes never actually apply. What we tested: - Updating prompt field - returns success, GET confirms no change - Updating name field - same result - Updating instructions field (in case the field name differed) - same result - Tested on 2026-03-25 and again today (2026-03-31), same behavior both times What works fine: - create-assistant (POST) - works, prompt and model are set correctly at creation - get-assistant (GET) - works, returns full assistant data - Auth is valid (wouldn't get 200 responses otherwise) Our setup: - Bearer token auth - Hitting https://api.assistable.ai/v2/update-assistant - Sending assistant_id, location_id, and the field to update - Response is always {"status": "success", "id": "..."} Example request: curl -X PUT https://api.assistable.ai/v2/update-assistant \ -H "Authorization: Bearer <token>" \ -H "Content-Type: application/json" \ -d '{"assistant_id": "<id>", "location_id": "<loc>", "prompt": "new prompt text"}' Why this matters for us: We run the same bot (CHLOE) across 9+ subaccounts. Right now every prompt update has to be done manually in the UI for each one. A working update endpoint would let us push changes to all subaccounts in one script. Is this a known issue? Is there a different approach we should be using, or a fix in the pipeline?