YaqeenDocs
Back to Yaqeen

Help

Changelog

What changed in Yaqeen and its API, newest first, with dates.

Entries are newest first. Yaqeen has no version numbers yet, so each entry carries a date. Nothing here is a promise about what comes next.

20 November 2026#

Added: People, API keys and Webhooks in Settings. Admins now manage these in the dashboard instead of calling the API. People has tabs for active, invited, deactivated and merchant accounts. An admin invites someone with a role described beside the choice, changes a role, switches an account off or on, makes a password reset link and resends or cancels an invitation. A change that needs a second admin says so and stays unchanged until they approve it. API keys lists each key with a status (active, expires soon, expired, revoked), creates a key with scopes written from what the server allows, and rotates it with a choice of how long the old key keeps working. Webhooks lists each address with a status, adds one, changes its address and events, sends a test, shows every call with the exact body and what the receiver answered, replays a call and replaces the signing secret. A key, a signing secret and a link are each shown once, and the panel does not close by accident until the admin says it was saved.

Changed: API for keys, webhooks and invitations. POST /api/v1/keys/{id}/rotate/ takes overlap_hours (0, 24 or 168). GET /api/v1/keys/ adds created_at, created_by, sandbox and status. last_used_at is now written at most once every 5 minutes. GET /api/v1/webhooks/ adds created_by, old_secret_until and a health block. New: GET /api/v1/webhooks/events/, PATCH /api/v1/webhooks/{id}/ and GET /api/v1/webhooks/deliveries/{id}/. The deliveries list takes status and event_type and returns created_at, and the test call answers with the queued delivery. GET /api/v1/users/invites/ adds created_at and invited_by, and POST /api/v1/users/invites/{id}/resend/ is new. Nothing that worked before was removed.

Added: flagged chats on a hold, and messages on the merchant's payout. A hold whose reasons include chats that ask the buyer to pay outside the platform now has a Chats tab. It shows only the store's flagged lines, with the matched words marked and the buyer's next line, and names no buyer. Opening it is written to the audit log. A reviewer can ask the store about the chats in one click. The store reads and answers in its payout panel, where the thread with the review team now lives, and the documents list asks for a short explanation of the chats.

Changed: the appeal screen for reviewers. An appeal now opens as a case: who and why the payout was held, what the merchant wrote and sent next to what they were asked for, a dated list of what has happened, and the decision with the amount it moves. Buttons open the case and the hold, and Next appeal opens the one that has waited longest. The open appeal stays in the address, so Back from the case returns to it.

Changed: Settings. Settings is now a list of sections by who a change reaches. Reviewers read the organization's review rules. Admins change the queue limits, lower plan limits and switch AI assistant connections. Merchants set notifications and phones, download their data, and ask for a copy of it or for erasure. Each section says what it is for and who it reaches, and each row says what changes.

Changed: the YQN canvas. A large result now opens over a dimmed page in the same panel as records, instead of in a column beside the chat. Escape or a click outside closes it.

Added: a Governance tab on the Policy screen. It reads top to bottom: what the system does and does not do, what it reads and never reads, how it was checked, the known gaps with the next step for each, the settings in force with how each was chosen, whether reviewers are really deciding, and how a policy change gets in. Every statement carries a tag that says where it comes from: a built-in rule, read live from your organization, measured in a test, our assumption, or not done yet. The page warns when the test results belong to a different model version than the one in use. No API changed.

Changed: the overview. The "Payout risk and model confidence" card is gone from the overview. The weekly numbers are now one "Weekly activity" card. The four figures for this week so far each show the usual week beside them, and each picks what the bar chart shows, with a line for the usual week. The last 8 weeks open in a table that adds the share of decided holds that were approved and a total row. Info tips now measure themselves and stay inside the window, so a long tip at the edge of a card is no longer cut off. No API changed.

Changed: the decision log screen. It now has the same band as Holds and Cases, with tabs for All, Holds, Appeals, Cases and Other records, each with a count. One search box finds entries by action, person or reason on the page, and a whole record id pasted into it shows every entry for that record. Two filters show decisions only, or only entries made by people or by the system. Selecting an entry opens a panel with the record it was about, the history of that record, the reason, the details the system kept, and the entry number and hash that show it was not changed. Entries that arrive after a refresh are marked with a dot for a few seconds. No API changed.

Changed: held money and disputes screen, and the Alerts page is gone. The screen formerly called Reserves is now called Held money. It uses the same table, search and filter bar as Holds and Cases, with a Store column on disputes, and it now says in plain words what each reserve is: a set amount, a share of payouts, or money held for a dispute. It shows three totals on top (money held back, disputes to decide, next money back to a store). A dispute opens with the payout it is about, how much of that payout it covers, where it stands, what the store answered, and what each decision does to the money. The Alerts page was removed. Its weekly numbers now sit on the Overview as "This week so far", and admins see system health there. Open errors show on the Overview for the team that runs Yaqeen. GET /api/v1/reserves/disputes/ and the other dispute responses now include store_id. Nothing else in the API changed.

19 November 2026#

Changed: security fixes. Each organization's rules, suppressions, case conclusions, appeals and appeal documents are now visible and applied only inside that organization, and so are the people the assistant lists and the people a case can be assigned to. GET and POST /api/v1/ops/errors/ are now for the team that runs Yaqeen only, because the errors come from every customer: a customer's admin gets 403, and the Alerts page no longer shows the errors card to them. PUT /api/v1/usage/plan/ can only lower a limit (400 bad_limit for a value that is not a whole number, 403 over_plan above the plan). Signing out everywhere, changing a password and a password reset now also end the tokens of connected AI apps, and using a sign-in code twice revokes the tokens it gave out. Failed sign-ins on the OAuth page count per username and address, so one address can no longer lock a person out. Invitation links now carry the token after #, so it never reaches a server log.

Changed: YQN moved into the dashboard. The separate /yqn page is gone, and /yqn and /assistant now open /app/yqn. Signing in goes straight to the dashboard (or the page you were sent away from), with no in-between screen. On a wide screen the YQN panel sits beside the page and stays open from page to page. On a phone it fills the screen. Cmd+J or Ctrl+J opens and closes it, and with text selected on the page it opens with that text quoted in the box. The crosshair in the panel header lets you click a row or card on the page to ask about it, and a new question sent while YQN is answering stops the old answer first. Hand to a teammate (staff) and Ask the review team (merchants) pass the question to a person: a case assignment with a note, or a message on the hold. New endpoint: GET /api/v1/assistant/teammates/ (reviewers and admins), the active staff of your organization. Chat, run and the tool list take a language field (en or ar), and in Arabic result titles, columns, badges and tool names come back in Arabic. The panel has the chat list, starters that follow the page you are on, and the record on screen as a removable chip. While YQN works, one line names the tool it is running, then folds into the step summary. See Use YQN.

Added: the dashboard on a phone. Under 720 px the sidebar opens as a menu from the top bar. The first dashboard page of a visit plays a short opening, and the overview figures count up. Neither plays under reduced motion. Two new session keys, yaqeen-enter and yaqeen-entered, keep the opening to once per visit, and the cookie page lists them.

Added: Claude and Codex over MCP. Yaqeen runs an MCP server at POST /api/v1/mcp/ (the address without the final slash works too). It is stateless Streamable HTTP with JSON replies, and it serves protocol versions 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26. It offers twelve read-only tools from the assistant: search_holds, get_hold, explain_hold, hold_orders, hold_party_graph, list_cases, get_case, list_appeals, list_payouts, get_store, global_search and results. A message may be up to 64 KB, a browser Origin is refused unless it is on the allowed list, and the endpoint has its own throttle, 120 a minute. Each call is written to the audit log as mcp.call with the tool name and the app, never the arguments. A new API key scope mcp reaches this address and nothing else, and acts as a reviewer. See Connect Claude and Codex.

Added: OAuth sign-in for AI clients. Under /api/v1/oauth/ there are authorize, token, register and revoke endpoints, and the discovery documents /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. PKCE with S256 is required. A client identifies itself with a metadata document address or registers itself. Access tokens last 60 minutes. Refresh tokens last 30 days and work once, and showing an old one again revokes every token of that person for that client. Tokens are stored as hashes and work only at the MCP address. Only reviewers and admins can sign in, and merchant accounts are refused.

Added: MCP policy for an organization. PUT /api/v1/mcp/settings/ (a signed-in admin) sets enabled (default true) and redact (default false). Redaction swaps names, usernames and contact values for placeholders with the assistant's redactor. Each change is audited as mcp.settings. See Settings.

Added: an AI assistants tab in Settings. Admins can switch Claude and Codex access on or off for the whole organization and choose whether names and contact details are hidden from the assistant. It uses the same settings as the API call above.

Changed: old sign-in rows are now deleted. The daily sweep deletes Claude and Codex sign-in codes 1 day after they end, tokens 30 days after the refresh token ends or is revoked, and apps with no code or token for 90 days. Erasing a person deletes their codes and tokens at once. New audit events: oauth.client_registered, oauth.revoked and oauth.replay_revoked. See Retention.

Changed: the Yaqeen site. The integrations section shows eight ways to connect, including MCP with the Claude and Codex logos. A new section, "Connect Claude or Codex", shows the site's address with a Copy button and a card each for the Claude settings, Codex and Claude Code. The FAQ has a question about staff using Claude or Codex. The language switch is a globe icon. A small suggestion bubble from YQN appears after 15 seconds, changes its sentence every 15 seconds and stops after the fifteenth. Closing it hides it until the next turn. It keeps one browser storage key per session, yaqeen-yqn-nudge on the site and yq-nudge on the docs, and the cookie page lists the first.

Added: privacy and legal pages. The Yaqeen site has pages for the privacy notice, terms, cookies, trust and sub-processors, in English and Arabic, linked from the footer. The cookie page lists every cookie and browser storage key. Yaqeen sets no non-essential cookie, so there is no consent choice. A short cookie note says this once and can be closed. Sign-up now asks you to accept the current privacy notice and terms. POST /api/v1/auth/signup/ takes a required accepted_policy field, the version from the new public GET /api/v1/privacy/policy/, and answers 400 policy_not_accepted when it is missing or old. Yaqeen records the version and the time. Our governance documents (data map, retention schedule, rights and breach procedures, an impact assessment and an AI governance note) are available on request.

Added: ask about your own data. A merchant can file an access or erasure request for their own data with POST /api/v1/privacy/me/requests/. Staff answer it from the existing request list. See Privacy and trust.

Changed: erasure. Erasing an owner now also covers store contact and address fields, every identifier hash (replaced by random tokens), dispute statements, appeal files in the document store, push tokens, sign-in links and assistant chats. If the document store cannot be reached, nothing is erased and the request stays open. Reviewer notes, decision notes, money rows and the audit log still stay. See Data we store.

Added: retention. The daily privacy sweep now deletes assistant chats after 90 days, finished webhook deliveries after 30 days and error records after 90 days, and expired sessions are cleared daily. Owner records are still erased only when an admin starts the erasure, never on their own. See Retention.

Changed: the assistant's language model. There is no default model provider. Every call to a model passes through Yaqeen's redacting gateway, and notes that people typed are not sent unless that is switched on. See AI and your data.

Added: sign out everywhere, and policy acceptance for Google sign-up. POST /api/v1/auth/logout-everywhere/ ends every session of the signed-in person on every device and answers how many other sessions it ended. A Google account that is new to Yaqeen must now send accepted_policy (the version from GET /api/v1/privacy/policy/) with POST /api/v1/auth/google/, or the call answers 400 policy_not_accepted. The sign-up page sends it. An existing account signs in without it.

Changed: buyers' contact details are no longer stored. The customers table keeps keyed hashes of the phone, email and address and the coarse place (district, city, postcode, short address), and no longer has a name, phone number, email address or street address. An upload or a customers feed row that carries them is accepted and the plain values are dropped. full_name and mobile_number are no longer required in a customers feed row. See Data we store.

Changed: fonts and headers. The site and the docs serve their fonts themselves, so a visitor's browser no longer contacts Google Fonts. Both send a content security policy and a permissions policy. A session lasts 14 days.

18 November 2026#

Added: the dashboard. Yaqeen now has a web dashboard at /app for staff and merchants. Reviewers and admins get an overview, the hold list and hold detail with the linked-party graph, cases, appeals, alerts, policies, the simulator, the decision log and the YQN assistant. Merchants get a portal with their payouts, the holds on them, the appeal form with document upload and a timeline of decisions. Every screen works in English and in Arabic, right to left, and is built for desktop screens. It runs on the existing API under /api/v1 and adds no new endpoints.

Changed: the analyst role is gone. Staff roles are now reviewer and admin, plus merchant, and the system account that never signs in. A reviewer reads everything an analyst read and can also approve, reject or release a hold, decide appeals, assign and close cases, see the KPIs, the decision log and the monitoring numbers, and run the simulator and policy backtests. Existing analyst accounts and open invitations became reviewers. New sign-ups and invitations that name no role get reviewer, and a request with the role analyst now answers 400 invalid_role. A developer key with the read scope now acts with the reviewer identity but can only send GET, HEAD and OPTIONS requests. The decide scope can also post decisions, and ingest and scim stay admin. Entries below that mention analysts describe the API as it was on their date. A POST to /api/v1/scim/v2/Users needs an explicit role (reviewer or admin) and answers 400 with "A role is required." otherwise, because there is no default role. An admin who activates a self-signed-up account that has never signed in must set the role in the same PATCH /api/v1/users/{id}/, or the call answers 400 role_required. A key with only the read scope still cannot read the audit log and its export, case exports, ops/kpis, ops/monitoring, ops/weekly-report, queue/workload, policy or onboarding. See Roles.

Changed: detection. The detector was updated and retrained twice this week. It now reads more of your data: instalments, deliveries, refunds, bank accounts a store pays into, store owner logins and order chats. In our tests some patterns are found more often and some less often than before. The detail is in the evaluation pack, which is available on request.

Added: more fields and tables. The data model takes more of what an e-commerce platform holds. Owners gain gender and preferred language. Stores gain a store UUID, time zone, phone and email hashes, social handles, branch and employee counts, business and tax details and Maroof checks. Orders gain flags (gift, quick checkout, reseller, on demand, potential fraud), the IP city, region and time zone, the shipping method and consignee hashes. payment_attempts gains the card brand, issuing country and bank, funding, network, last four digits, error code and a 3D Secure flag. refunds gains the refund id, reference and status (refunded, pending or failed). installments gains the provider name and amount, and deliveries the tracking number, proof type and package count. New tables hold bank accounts a store has paid into, store owner logins and account changes, provider webhooks, storefront events, order history, comments, tags, return shipments and order chats. See Load your data.

Fixed: scoring from the database. Scoring now reads every table you load. Scores computed before this change did not use the newer tables. Run scoring again to refresh them.

Known limit: the live feed. The feed does not take store_bank_accounts, merchant_events or messages yet. Ask your Yaqeen contact to load those tables for you.

Changed: the hosted prototype. Automatic jobs, such as releasing a hold after its date and the daily backup, are paused on the hosted prototype. Ask your Yaqeen contact before you rely on them.

15 November 2026#

Added: audit anchors. The daily audit check now stores the chain head and checks every stored anchor against the log. It records a new anchor only when the chain and the old anchors are intact. The audit verify endpoint reports an anchors block.

Added: two KPI fields. GET /api/v1/ops/kpis/ returns false_positive_rate and oldest_waiting_hours, scoped to your organization.

Changed: idempotency on the feed. The payout feed now accepts Idempotency-Key. See Safe retries.

Added: onboarding checklist. GET /api/v1/onboarding/ returns four setup steps for your organization: create a key, send data, see a hold and make a decision. Each step has done set from real data, and the response names the next step. Analysts, reviewers and admins can call it.

Added: search. GET /api/v1/search/?q= finds stores by exact store id or part of a name in Arabic or English, and lists open holds on those stores. It needs at least 2 characters, returns up to 10 stores and 10 holds, and is limited to staff roles.

Added: one-time password reset links. An admin issues a link with POST /api/v1/users/{id}/reset-link/. The token is shown once, works once and ends after 60 minutes. A new link ends any older one. The person sets their own password with POST /api/v1/auth/password/reset/ and needs no sign-in. The admin never sees the password. See Roles.

Changed: documentation. The concept pages on holds, approvals, roles, organizations and privacy were rewritten. New pages explain how decisions and reasons are made and how the audit chain works. A help section adds troubleshooting, a FAQ, a glossary and a security page.

14 November 2026#

Added: review controls. A review queue with priority and deadlines, second-person approval for large or risky changes, case conclusions, bulk decisions with idempotency keys, saved views, and suppressions that end. See Second-person approval.

Added: organizations. Every customer is an organization, and each request sees only its own data. See Organizations.

Added: product features. A merchant portal, store risk profiles, signed outgoing webhooks, API keys with scopes and usage counting, a policy lab with backtest and shadow runs, customer rules, privacy requests with legal holds, case and audit exports, KPIs, reserves and disputes, and a public trust page.

Added: onboarding and tools. Invitations by email, new-store intake with a checklist, no-code column mappings with a dry run, a sandbox with yq_test_ keys, an invoice draft built from usage, and SCIM user provisioning.

Added: assistant. A chat assistant for staff and merchants. It shows what the signed-in role may use, and a change happens only through a confirm card.

Added: appeal documents, cases and notifications. Merchants can attach files to an appeal, and staff open them through links that expire in 5 minutes. Holds join cases through exact identifiers. Merchants get notifications when a hold or appeal changes.

Added: operations. An error tracker, alerts, and a daily backup that is restored into a scratch database as a check.

Added: documentation site. This site, built as static pages.

13 November 2026#

Added: the detector. Yaqeen scores payouts and recommends holds, with reasons that name linked owners. It comes with partial holds, a hold simulator, policy versions and a live feed.

Added: merchant access and appeals. Merchants see their own holds and appeal them. Approved holds are released when their end date passes, unless an appeal is open.

Changed: sign-in limits. Login is limited per username and address and, separately, per username across all addresses. The limit no longer trusts a forged client address.

Up Down to moveEnter to openEsc to close