# Anthid

> Anthid provides order and execution management through an API and web dashboard. Record trading instructions before broker dispatch, apply controls to new creates, stream order and position activity, and query a durable ledger across supported broker accounts. Paper trading is available on every plan.

- [Introduction to Anthid](https://docs.anthid.com/pages/intro/introduction.md): What Anthid does, where it sits, and what your firm stops having to build
- [Quickstart](https://docs.anthid.com/pages/intro/quickstart.md): Connect a paper account and send a first order, in a few minutes
- [Operate orders in the dashboard](https://docs.anthid.com/pages/guides/oms-workflow.md): Place an order, trace its commands and broker outcome, and review the account in Anthid's web app.
- [Intents](https://docs.anthid.com/pages/concepts/intents.md): What an intent is, why Anthid records the instruction separately from the order, and what that separation buys you
- [Orders](https://docs.anthid.com/pages/concepts/orders.md): What an order record is, why it carries two identifiers, and why finished is not the same as filled
- [Positions](https://docs.anthid.com/pages/concepts/positions.md): What a position record represents, where the number comes from, and why Anthid reports the broker's figure rather than calculating its own
- [Limits and entitlements](https://docs.anthid.com/pages/concepts/limits.md): Check which features and usage limits your organization has, and distinguish query access from record retention.
- [Brokers](https://docs.anthid.com/pages/brokers/overview.md): Connect trading accounts through Anthid using a unified broker integration layer.
- [Supported Order Types](https://docs.anthid.com/pages/brokers/supported-order-types.md): Order type support varies by broker.
- [Supported Destinations](https://docs.anthid.com/pages/brokers/supported-destinations.md): Route strategy values accepted by Anthid and their broker support.
- [Supported Time In Force](https://docs.anthid.com/pages/brokers/supported-time-in-force.md): Available time-in-force instructions and broker support.
- [Lightspeed Connect](https://docs.anthid.com/pages/brokers/lightspeed-connect.md): Connect Lightspeed Connect accounts through Anthid.
- [Controls Overview](https://docs.anthid.com/pages/controls/overview.md): Protect your trading systems with organization, account, and symbol-level controls.
- [Community](https://docs.anthid.com/pages/community/overview.md): Connect with other Anthid users and the Anthid team.
- [Roadmap](https://docs.anthid.com/pages/community/roadmap.md): Where Anthid is headed next
- [Security](https://docs.anthid.com/pages/about/security.md): How Anthid protects broker credentials, keeps one client's data out of another's, and attributes every change to the credential behind it
- [Compliance](https://docs.anthid.com/pages/about/compliance.md): How Anthid records and preserves order instructions, control changes, and refusals, and what that means for broker-dealer and registered adviser clients
- [API Authentication](https://docs.anthid.com/api-reference/introduction.md): Authenticate and send requests to the Anthid APIs
- [Connections API](https://docs.anthid.com/api-reference/connections/overview.md): Query broker connection statuses last seen by the platform.
- [List connection statuses](https://docs.anthid.com/api-reference/connections/list-connection-statuses.md): Lists real and simulated account statuses in environments the caller may read. Users and API keys are scoped to their organization; service tokens may read across organizations. Simulated accounts are omitted if their listing fails. Requires intent read permission in at least one environment.
- [Get a connection status](https://docs.anthid.com/api-reference/connections/get-a-connection-status.md): Returns the account's active or pending connection status. Requires intent read permission for its environment. Users and API keys may read only their organization; service tokens may read across organizations.
- [Organizations API](https://docs.anthid.com/api-reference/organizations/overview.md): Manage users, organizations, and organization onboarding state.
- [Get current user](https://docs.anthid.com/api-reference/organizations/get-current-user.md): Returns the authenticated user's name and email address from the identity provider.
- [Update current user](https://docs.anthid.com/api-reference/organizations/update-current-user.md): Updates the authenticated user's metadata and locale at the identity provider. Supplied metadata replaces the existing map. Requires a user principal with an active organization.
- [Delete current user](https://docs.anthid.com/api-reference/organizations/delete-current-user.md): Permanently deletes the authenticated user at the identity provider and queues a deletion event. Requires a user principal with an active organization.
- [Get user by id](https://docs.anthid.com/api-reference/organizations/get-user-by-id.md): Returns a named user's name and email address from the identity provider. Authorized service accounts can resolve any user; a signed-in user can resolve only themselves.
- [Create an organization](https://docs.anthid.com/api-reference/organizations/create-an-organization.md): Starts organization setup for the authenticated user and returns its ID before provider setup completes. The required `idempotency_key` identifies the workflow; repeating it returns the original organization ID. Only user principals may call this.
- [List current user organizations](https://docs.anthid.com/api-reference/organizations/list-current-user-organizations.md): Lists the organizations the authenticated user belongs to.
- [Get organization](https://docs.anthid.com/api-reference/organizations/get-organization.md): Returns an organization by its internal ID. Users may read any organization they belong to; API keys may read only their own organization. Service tokens require `organization:read`.
- [Update organization name](https://docs.anthid.com/api-reference/organizations/update-organization-name.md): Updates the active organization's name. The caller must be an organization admin; authorization uses the active organization context.
- [Delete organization](https://docs.anthid.com/api-reference/organizations/delete-organization.md): Deletes an organization and queues removal of its external identity record. The caller must be an organization admin and retain membership in another organization.
- [Get organization by provider id](https://docs.anthid.com/api-reference/organizations/get-organization-by-provider-id.md): Returns an organization by its identity-provider ID. Service accounts can read any organization; users can read organizations they belong to.
- [Get organization onboarding](https://docs.anthid.com/api-reference/organizations/get-organization-onboarding.md): Returns onboarding completion timestamps. Users may read any organization they belong to; API keys may read only their own organization. Service tokens require `organization:read`.
- [Update organization onboarding](https://docs.anthid.com/api-reference/organizations/update-organization-onboarding.md): Marks one onboarding step complete. Users may update any organization they belong to. Service tokens require `organization:read`. API keys cannot update onboarding.
- [Controls API](https://docs.anthid.com/api-reference/controls/overview.md): Manage and evaluate manual, risk, and time controls across organizations, trading accounts, and symbols.
- [Get current organization control](https://docs.anthid.com/api-reference/organization-controls/get-current-organization-control.md): Returns the caller's organization manual control. Requires Controls Premium. Users need an organization role; API keys need both `paper:control:read` and `live:control:read`.
- [Upsert organization control](https://docs.anthid.com/api-reference/organization-controls/upsert-organization-control.md): Creates or replaces the caller's organization manual control. Omitted optional fields are cleared. Requires Controls Premium. Users need an admin role; API keys need both `paper:control:edit` and `live:control:edit`.
- [Patch organization control](https://docs.anthid.com/api-reference/organization-controls/patch-organization-control.md): Creates or patches the caller's organization manual control. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Premium. Users need an admin role; API keys need both `paper:control:edit` and `live:control:edit`.
- [Delete organization control](https://docs.anthid.com/api-reference/organization-controls/delete-organization-control.md): Deletes the caller's organization manual control. Requires Controls Premium. Users need an admin role; API keys need both `paper:control:edit` and `live:control:edit`.
- [Get organization control](https://docs.anthid.com/api-reference/organization-controls/get-organization-control.md): Returns the manual control for an organization. This route requires service-account credentials with `control:read`.
- [Get account control](https://docs.anthid.com/api-reference/account-manual-controls/get-account-control.md): Returns manual controls for a trading account. Users and API keys require Controls Basic or Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert account control](https://docs.anthid.com/api-reference/account-manual-controls/upsert-account-control.md): Creates or replaces manual controls for a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch account control](https://docs.anthid.com/api-reference/account-manual-controls/patch-account-control.md): Creates or patches manual controls for a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete account control](https://docs.anthid.com/api-reference/account-manual-controls/delete-account-control.md): Deletes manual controls for a trading account in the caller's organization. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [List control changes for an account](https://docs.anthid.com/api-reference/account-manual-controls/list-control-changes-for-an-account.md): Lists account and symbol control changes, newest first. Includes the actor's credential type, without actor identifiers. Requires Controls Basic or Premium and control read access for the account.
- [Get account time control](https://docs.anthid.com/api-reference/account-time-controls/get-account-time-control.md): Returns time-window controls for a trading account. Users and API keys require Controls Basic or Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert account time control](https://docs.anthid.com/api-reference/account-time-controls/upsert-account-time-control.md): Creates or replaces time-window controls for a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch account time control](https://docs.anthid.com/api-reference/account-time-controls/patch-account-time-control.md): Creates or patches time-window controls for a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete account time control](https://docs.anthid.com/api-reference/account-time-controls/delete-account-time-control.md): Deletes time-window controls for a trading account in the caller's organization. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Get account risk control](https://docs.anthid.com/api-reference/account-risk-controls/get-account-risk-control.md): Returns risk limits for a trading account. Users and API keys require Controls Basic or Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert account risk control](https://docs.anthid.com/api-reference/account-risk-controls/upsert-account-risk-control.md): Creates or replaces risk limits for a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch account risk control](https://docs.anthid.com/api-reference/account-risk-controls/patch-account-risk-control.md): Creates or patches risk limits for a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete account risk control](https://docs.anthid.com/api-reference/account-risk-controls/delete-account-risk-control.md): Deletes risk limits for a trading account in the caller's organization. Requires Controls Basic or Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [List effective symbol controls](https://docs.anthid.com/api-reference/effective-controls/list-effective-symbol-controls.md): Lists symbol-level manual, risk, and time controls, ordered by symbol in pages of 25. Does not merge organization or account controls. Users and API keys require Controls Premium and account control read access; services need `control:read` and `x-organization-id`.
- [Get symbol control](https://docs.anthid.com/api-reference/symbol-manual-controls/get-symbol-control.md): Returns manual controls for a symbol on a trading account. Users and API keys require Controls Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert symbol control](https://docs.anthid.com/api-reference/symbol-manual-controls/upsert-symbol-control.md): Creates or replaces manual controls for a symbol on a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch symbol control](https://docs.anthid.com/api-reference/symbol-manual-controls/patch-symbol-control.md): Creates or patches manual controls for a symbol on a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete symbol control](https://docs.anthid.com/api-reference/symbol-manual-controls/delete-symbol-control.md): Deletes manual controls for a symbol on a trading account in the caller's organization. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Get symbol time control](https://docs.anthid.com/api-reference/symbol-time-controls/get-symbol-time-control.md): Returns time-window controls for a symbol on a trading account. Users and API keys require Controls Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert symbol time control](https://docs.anthid.com/api-reference/symbol-time-controls/upsert-symbol-time-control.md): Creates or replaces time-window controls for a symbol on a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch symbol time control](https://docs.anthid.com/api-reference/symbol-time-controls/patch-symbol-time-control.md): Creates or patches time-window controls for a symbol on a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete symbol time control](https://docs.anthid.com/api-reference/symbol-time-controls/delete-symbol-time-control.md): Deletes time-window controls for a symbol on a trading account in the caller's organization. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Get symbol risk control](https://docs.anthid.com/api-reference/symbol-risk-controls/get-symbol-risk-control.md): Returns risk limits for a symbol on a trading account. Users and API keys require Controls Premium and control read access. Services need `control:read` and `x-organization-id`. The organization must own the account.
- [Upsert symbol risk control](https://docs.anthid.com/api-reference/symbol-risk-controls/upsert-symbol-risk-control.md): Creates or replaces risk limits for a symbol on a trading account in the caller's organization. Omitted optional fields are cleared. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Patch symbol risk control](https://docs.anthid.com/api-reference/symbol-risk-controls/patch-symbol-risk-control.md): Creates or patches risk limits for a symbol on a trading account. Omitted and null fields are unchanged; `clear` removes named fields. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Delete symbol risk control](https://docs.anthid.com/api-reference/symbol-risk-controls/delete-symbol-risk-control.md): Deletes risk limits for a symbol on a trading account in the caller's organization. Requires Controls Premium. Users need an organization admin role; API keys need control edit permission for the account's environment.
- [Evaluate controls](https://docs.anthid.com/api-reference/control-evaluation/evaluate-controls.md): Evaluates organization controls for JSON `null`, or effective order controls for an order context with a resolved `instrument`. Non-equity instruments are blocked. Supply `side` when position or daily-loss controls apply; those controls block orders without it. Both allowed and blocked results retur…
- [Trading Accounts API](https://docs.anthid.com/api-reference/accounts/overview.md): Manage broker-connected accounts, their enabled state, and encrypted broker credentials.
- [List trading accounts](https://docs.anthid.com/api-reference/accounts/list-trading-accounts.md): Lists trading accounts visible to the caller, newest first. Users and API keys are limited to their organization and never see deleted accounts: they may pass their own `organization_id` or omit it, and naming another organization is refused. Service tokens with `credential:read` may list all organi…
- [Create a trading account](https://docs.anthid.com/api-reference/accounts/create-a-trading-account.md): Creates a trading account and securely stores its broker credentials. An optional `commission_per_share` beside the credential sets the broker's commission per share, in dollars, and an optional `minimum_commission` sets its minimum commission per order, in dollars. Both are nonnegative decimal stri…
- [Get a trading account](https://docs.anthid.com/api-reference/accounts/get-a-trading-account.md): Returns trading-account metadata, including disabled accounts and simulated accounts. Users and API keys can read their organization's accounts. Service tokens require `credential:read`.
- [Update a trading account](https://docs.anthid.com/api-reference/accounts/update-a-trading-account.md): Updates the account's enabled state or commission settings. Commission values are nonnegative decimal strings in dollars. Omitted or null fields keep their values; zero sets an explicit zero. At least one non-null field is required. Only organization admins may update accounts.
- [Delete a trading account](https://docs.anthid.com/api-reference/accounts/delete-a-trading-account.md): Deletes a trading account and its credentials, then queues removal of the stored secrets. The account stops appearing in reads immediately. The call is idempotent: deleting an already-deleted account succeeds without repeating the work. The caller must be an organization admin.
- [List broker credentials for an organization](https://docs.anthid.com/api-reference/broker-credentials/list-broker-credentials-for-an-organization.md): Lists credential metadata across the caller's organization without returning secret values. The organization is taken from the authenticated principal and cannot be named in the request. Pass `account_id` to narrow the listing to one trading account; an account the caller does not own matches nothin…
- [List broker credentials](https://docs.anthid.com/api-reference/broker-credentials/list-broker-credentials.md): Lists up to 100 credentials for the account without secret values. Users and API keys must own the account through their organization. Service tokens with `credential:read` may list any account. Use `GET /v1/accounts/credentials` to list across an organization.
- [Get a broker credential](https://docs.anthid.com/api-reference/broker-credentials/get-a-broker-credential.md): Returns credential metadata without returning the secret value. The credential must belong to the account in the path. Users and API keys can read credentials in their organization. Service tokens require `credential:read`.
- [Update a broker credential](https://docs.anthid.com/api-reference/broker-credentials/update-a-broker-credential.md): Replaces the secret value for a broker credential. The credential must belong to the account in the path. The caller must be an organization admin. A replacement naming a live environment requires the live-trading entitlement, for every broker alike.
- [Delete a broker credential](https://docs.anthid.com/api-reference/broker-credentials/delete-a-broker-credential.md): Disables a broker credential and its trading account, then queues removal of the stored secret. The credential must belong to the account in the path. The caller must be an organization admin.
- [Get a decrypted broker credential](https://docs.anthid.com/api-reference/broker-credentials/get-a-decrypted-broker-credential.md): Returns the broker's secret credential payload. The credential must belong to the account in the path. This sensitive endpoint is limited to service tokens with `credential:decrypt`.
- [Get a credential's organization](https://docs.anthid.com/api-reference/broker-credentials/get-a-credentials-organization.md): Returns the organization that owns a broker credential. The credential must belong to the account in the path. Only service tokens with `credential:read` may call this endpoint.
- [List simulated test accounts](https://docs.anthid.com/api-reference/accounts/list-simulated-test-accounts.md): Lists up to 1,000 non-deleted simulated accounts, newest first, without pagination. Service tokens with `credential:read` may read any organization or omit the filter to read all. Admins of configured internal organizations may read only their own organization.
- [Register a simulated test account](https://docs.anthid.com/api-reference/accounts/register-a-simulated-test-account.md): Registers a paper account whose orders are filled by a simulator. Service tokens with `accounts:admin` may name any organization. Admins of configured internal organizations may register accounts only in their own organization. API keys are refused.
- [Retune or disable a test account](https://docs.anthid.com/api-reference/accounts/retune-or-disable-a-test-account.md): Updates a simulated account. Omitted or null fields keep their values. Disabling stops the account on the next scheduler sweep; retuning restarts a running account. Service tokens with `accounts:admin` may update any organization. Admins of configured internal organizations may update only their own…
- [Remove a test account](https://docs.anthid.com/api-reference/accounts/remove-a-test-account.md): Soft-deletes a simulated account and stops it on the next scheduler sweep. Existing orders are retained. Service tokens with `accounts:admin` may delete any organization's accounts. Admins of configured internal organizations may delete only their own accounts.
- [Report the transactional outbox's health](https://docs.anthid.com/api-reference/accounts/report-the-transactional-outboxs-health.md): Reports queue counts and oldest timestamps by status and event type across all organizations, without tenant identifiers or payloads. Failed rows are no longer retried. Requires a service token with `credential:read` or an admin of a configured internal organization.
- [Report which simulated accounts are actually running](https://docs.anthid.com/api-reference/accounts/report-which-simulated-accounts-are-actually-running.md): Compares simulated accounts with current runner heartbeats. `observed` contains counts across all organizations; `test_accounts` contains accounts in the caller's scope. Heartbeats expire after 60 seconds. Requires a service token with `credential:read` for all organizations, or an admin of a config…
- [Intents API](https://docs.anthid.com/api-reference/intents/overview.md): Submit, inspect, and measure broker-agnostic trading intents.
- [List intent actions](https://docs.anthid.com/api-reference/intents/list-intent-actions.md): Lists an intent's append-only action history. Results are newest first by default and can be filtered by account or symbol. Each action includes the resolved `instrument`, dispatch `state`, and broker `runtime_status`.
- [Submit intent](https://docs.anthid.com/api-reference/intents/submit-intent.md): Submits a create, replace, or cancel command for an account in the caller's organization. API keys need intent edit permission for the account environment; users need an admin role. Creates require a routable `order_venue`, resolve the symbol's instrument, and pass trading controls. Live creates als…
- [Void a command](https://docs.anthid.com/api-reference/intents/void-a-command.md): Settles an organization-scoped command key. `VOIDED` prevents any later submission under that key; `WRITTEN` returns the intent already written. Waits for concurrent writes and returns the same outcome on retries. API keys need intent edit permission for the account environment; users need an admin…
- [Get latest intent action](https://docs.anthid.com/api-reference/intents/get-latest-intent-action.md): Returns the latest action recorded for an intent. An optional trading account ID narrows the lookup to that account. The response includes the submitted `symbol`, the resolved `instrument`, dispatch `state`, and the separate broker `runtime_status`. A null runtime status means the broker has not rep…
- [List intent actions](https://docs.anthid.com/api-reference/intents/list-intent-actions.md): Lists an intent's append-only action history. Results are newest first by default and can be filtered by account or symbol. Each action includes the resolved `instrument`, dispatch `state`, and broker `runtime_status`.
- [List refused submissions](https://docs.anthid.com/api-reference/intents/list-refused-submissions.md): Lists submissions refused by authorization, entitlement, or trading controls, newest first within one environment. Filter by account, refusal stage, or trailing days.
- [Ledger API](https://docs.anthid.com/api-reference/ledger/overview.md): Query current and historical broker orders, positions, and order statistics.
- [Get current positions](https://docs.anthid.com/api-reference/ledger/get-current-positions.md): Lists the latest broker positions, filtered by account and symbol. Each includes the broker symbol and an `instrument` tagged by `asset_class`. An exact account-and-symbol lookup returns 404 when no position exists. Service callers need `intent:read` and `x-organization-id`.
- [Get historical positions](https://docs.anthid.com/api-reference/ledger/get-historical-positions.md): Lists historical broker position snapshots for the caller's organization, defaulting to the last 90 days within the plan history window. Explicit bounds expand to whole minutes and must span at most 92 days. Each position includes the broker symbol and an `instrument` tagged by `asset_class`.
- [Get exposure over time](https://docs.anthid.com/api-reference/ledger/get-exposure-over-time.md): Reports positions at each bucket's close, hourly for one day and otherwise daily in New York. Positions carry forward until the broker reports a change. Notional uses average cost and the instrument multiplier. Each bucket includes long and short totals and an instrument breakdown, without netting a…
- [Get current orders](https://docs.anthid.com/api-reference/ledger/get-current-orders.md): Lists the latest state of broker orders for the caller's organization. Results can be filtered by account, symbol, intent, broker order ID, status, and state. Orders carry an `instrument` object tagged by `asset_class`; the symbol is available as `instrument.symbol`.
- [Get order](https://docs.anthid.com/api-reference/ledger/get-order.md): Returns the latest broker state for one order in the caller's organization. Read access is checked against the order account's environment. Orders include an `instrument`; its symbol is `instrument.symbol`.
- [Get historical orders](https://docs.anthid.com/api-reference/ledger/get-historical-orders.md): Lists historical broker order snapshots for the caller's organization, defaulting to the last 30 days within the plan history window. Explicit bounds expand to whole minutes and must span at most 92 days. Orders include an `instrument` tagged by `asset_class`; its symbol is `instrument.symbol`.
- [Get order stats](https://docs.anthid.com/api-reference/ledger/get-order-stats.md): Returns order counts and commission totals in hourly buckets for one day, otherwise daily New York buckets. `previous` covers the preceding window of equal length. Nonzero `unpriced_fill_count` means some filled orders lack a configured commission rate, so `fees` is incomplete.
- [Get order lifecycle metrics](https://docs.anthid.com/api-reference/ledger/get-order-lifecycle-metrics.md): Reports order outcomes and latency in hourly buckets for one day, otherwise daily New York buckets. Orders count in their first-snapshot bucket; ingest lag is measured per snapshot. Percentiles are null when no samples exist. Requires a paid plan.
- [Get order health signals](https://docs.anthid.com/api-reference/ledger/get-order-health-signals.md): Reports amendment counts, including cancels, and stale orders in PENDING_NEW, PENDING_CANCEL, PENDING_REPLACE or UNSPECIFIED status. Amendment buckets end at 3 or more. Returns at most 100 stuck orders, oldest first; `stuck_count` includes all matches. Requires a paid plan.
- [Get realized return per trading day](https://docs.anthid.com/api-reference/ledger/get-realized-return-per-trading-day.md): Returns realized dollar profit or loss less recorded commission, grouped into Sunday-to-Saturday weeks in America/New_York. Each week includes all seven days. Opening fills count as trades and incur fees even when they realize no profit. Exchange and regulatory fees are excluded; fills without a con…
- [Get completed intents](https://docs.anthid.com/api-reference/ledger/get-completed-intents.md): Lists filled, cancelled and rejected intents for the caller's organization. Returns one row per action; `terminal_only=true` selects the terminal action of each intent. Actions include `symbol`, resolved `instrument`, `terminal_status` and `terminal_at`. The plan history window bounds `start`, inclu…
- [Count completed intents](https://docs.anthid.com/api-reference/ledger/count-completed-intents.md): Counts distinct completed intents in the trailing window for the caller's organization. Amendments do not increase the count; live intents are excluded.
- [Get platform handoff latency](https://docs.anthid.com/api-reference/ledger/get-platform-handoff-latency.md): Returns platform-wide intent-to-broker handoff latency in milliseconds. Uses the trailing hour when it has at least 20 samples; otherwise reads up to the latest 20 handoffs within seven days. `window_seconds` reports the measured span. `p50_ms` needs one sample; `p95_ms`, `p99_ms` and `max_ms` need…
- [List traded symbols](https://docs.anthid.com/api-reference/ledger/list-traded-symbols.md): Returns sorted symbols traded in the trailing window or still held by the caller's organization. The window is capped by the caller's plan. Results are not paginated.
- [Instruments API](https://docs.anthid.com/api-reference/instruments/overview.md): Look up instrument identities and contract details.
- [List instruments](https://docs.anthid.com/api-reference/instruments/list-instruments.md): Lists the shared equity and option catalogue. Defaults to ACTIVE entries; catalogue status does not grant trading permission. Each `instrument` is tagged by `asset_class`. Text filters are trimmed and blank values are ignored. Continue with `next_cursor` until null, keeping filters and sort directio…
- [Get instrument](https://docs.anthid.com/api-reference/instruments/get-instrument.md): Returns one instrument by its stable platform ID, regardless of catalogue status. No asset class is required. Available to authenticated users, API keys and services.
- [List short sale borrow rates](https://docs.anthid.com/api-reference/instruments/list-short-sale-borrow-rates.md): Lists overnight borrow rates from each broker's latest loaded list. Either date parameter selects history; both bounds include the named New York calendar day, and an omitted bound is open. Rates are dollars per share per night. Null means no premium was stated; no row means the symbol was not liste…
- [Streaming](https://docs.anthid.com/api-reference/stream/overview.md): Receive real-time order and position updates through Anthid's gRPC streaming APIs.
- [Node.js](https://docs.anthid.com/api-reference/stream/nodejs.md): Connect to Anthid's Streaming API using Node.js and gRPC.
- [Python](https://docs.anthid.com/api-reference/stream/python.md): Connect to Anthid's Streaming API using Python.
- [Rust](https://docs.anthid.com/api-reference/stream/rust.md): Connect to Anthid's Streaming API using Rust and Tonic.
- [Limits and entitlements](https://docs.anthid.com/pages/concepts/limits.md): Check which features and usage limits your organization has, and distinguish query access from record retention.
- [Get billing claims](https://docs.anthid.com/api-reference/billing/get-billing-claims.md): Returns the entitlements and usage limits for an organization. Users and API keys can read their own organization. Service tokens require `billing:read`.
- [Create a billing portal session](https://docs.anthid.com/api-reference/billing/create-a-billing-portal-session.md): Creates a Stripe billing portal session and returns its URL. Requires a user who is an admin of the organization in the path.
- [Blog](https://docs.anthid.com/pages/blog/overview.md): Platform updates, engineering notes, and practical guidance from the Anthid team
- [Anthid is more than an EMS/OMS](https://docs.anthid.com/pages/blog/articles/beyond-ems-oms.md): How Anthid brings broker connectivity, durable instructions, trading controls, live operations, and execution history into one managed platform.
- [Why use Anthid instead of building your own execution layer](https://docs.anthid.com/pages/blog/articles/overview.md): What the layer between a strategy and a broker actually costs to own, what Anthid takes off your plate, and when building it yourself is still the right call
- [Recorded before acknowledged: why an instruction and its execution fail independently](https://docs.anthid.com/pages/blog/articles/recorded-before-acknowledged.md): How Anthid orders the record and the execution of an instruction, what that ordering rules out, and what it lets you answer when nothing came back from the broker
- [SENT is not FILLED: the two-state order lifecycle](https://docs.anthid.com/pages/blog/articles/sent-is-not-filled.md): Why Anthid reports how far the platform got and what the broker did as two separate fields, what goes wrong when they are collapsed into one, and which field answers which question
- [Build vs buy: the real cost of trading infrastructure](https://docs.anthid.com/pages/blog/articles/build-vs-buy-trading-infrastructure.md): Why the estimate for an execution layer is always wrong, what the layer actually costs to staff, and how to settle the question in an afternoon
- [Anthid vs Lightspeed: which one should you build on?](https://docs.anthid.com/pages/blog/articles/anthid-vs-lightspeed.md): Anthid is the execution and risk layer your strategy talks to, and Lightspeed is a brokerage it routes to, so the question is whether to build your own layer on Lightspeed Connect or put Anthid in front of it
- [How to add a second broker without a rewrite](https://docs.anthid.com/pages/blog/articles/add-a-second-broker-without-a-rewrite.md): Why the second broker breaks a home-built execution layer, why it is a setting when the layer is Anthid's, and a rollout plan that costs no code changes
- [Platform update | August 2026](https://docs.anthid.com/pages/blog/platform-news/august-2026.md): Lower latency under concurrent load, sessions that recover from broker-side drops on their own, and a smaller metrics surface
- [Welcome to the Anthid blog](https://docs.anthid.com/pages/blog/welcome.md): What we plan to publish here and how it fits alongside the rest of the documentation
- [AUDIT](https://docs.anthid.com/AUDIT.md)
- [Trading infrastructure your firm does not have to build](https://docs.anthid.com/index.md): Connect broker accounts, put controls in front of every order, and keep a durable record of what was instructed and what happened.

## OpenAPI Specs

- [accounts.openapi](/api-reference/accounts.openapi.json)
- [billing.openapi](/api-reference/billing.openapi.json)
- [connections.openapi](/api-reference/connections.openapi.json)
- [controls.openapi](/api-reference/controls.openapi.json)
- [instruments.openapi](/api-reference/instruments.openapi.json)
- [intents.openapi](/api-reference/intents.openapi.json)
- [ledger.openapi](/api-reference/ledger.openapi.json)
- [organizations.openapi](/api-reference/organizations.openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.