# Mercora > Trade operations for physical commodity traders: documents, matching, reconciliation, financials and the P&L. - [Welcome to Mercora](https://docs.mercora.io/index.md): The back office for physical commodity trading. - [Quickstart](https://docs.mercora.io/getting-started/quickstart.md): Accept your invite, sign in and upload your first document. - [Walk through a trade](https://docs.mercora.io/getting-started/walkthrough.md): Follow one sugar trade from its documents to its P&L, then fix a mismatch on an aluminium trade. - [Mercora by role](https://docs.mercora.io/getting-started/by-role.md): Where operators, finance, admins and developers spend their time in Mercora, and what to read first. - [Navigating Mercora](https://docs.mercora.io/getting-started/navigating-mercora.md): What each sidebar area is for, and why your sidebar may differ from a colleague's. - [How Mercora works](https://docs.mercora.io/concepts/how-mercora-works.md): What happens to a document from arrival to approval, and why a person always approves. - [Modules](https://docs.mercora.io/concepts/modules.md): Modules are the parts of Mercora your workspace uses. Admins turn them on and off for everyone. - [Roles and permissions](https://docs.mercora.io/concepts/roles-and-permissions.md): Every member has one role, which sets what they can view and change in each area of Mercora. - [Uploading documents](https://docs.mercora.io/documents/uploading.md): Upload trade documents by hand, including saved emails and multi-document packs. - [Email ingestion](https://docs.mercora.io/documents/email-ingestion.md): How documents sent to your workspace mailbox reach Mercora, and what to check when one doesn't. - [Document processing](https://docs.mercora.io/documents/processing.md): What Mercora does with a document after it arrives, what each Inbox status means, and how to recover a document that fails. - [The Inbox](https://docs.mercora.io/documents/inbox.md): Your work queue: review what Mercora read against the original, then approve, reject or request a correction. - [Matching documents to trades](https://docs.mercora.io/documents/matching.md): How Mercora links a document to its trade, and how to match, move or unmatch one yourself. - [Discrepancies](https://docs.mercora.io/documents/discrepancies.md): How Mercora checks a document against its trade, and how to resolve the differences it finds. Also covers the expected documents checklist. - [Trades](https://docs.mercora.io/trades/overview.md): Find a trade, read what it's making, and close it out. - [Shipments](https://docs.mercora.io/trades/shipments.md): Track the vessels, containers and trucks carrying your cargo. - [Trade financials](https://docs.mercora.io/trades/financials.md): Settle a trade's invoices, record payments, net AR against AP, and plan its costs. - [Financials](https://docs.mercora.io/finance/financials.md): Find any invoice across the workspace and see what's outstanding and overdue. - [P&L](https://docs.mercora.io/finance/pnl.md): See realized and open margin across your book by commodity, book and delivery month, with the basis of every number. - [Reports](https://docs.mercora.io/finance/reports.md): See what needs your attention, track realized cashflow, and chase overdue payments. - [Counterparties](https://docs.mercora.io/records/counterparties.md): Keep one record per buyer, supplier, broker and bank, with KYC, terms, contacts, open balances and statements. - [Contracts](https://docs.mercora.io/records/contracts.md): Keep purchase and sales contracts as records, pair them into deals, and draft new ones from your own templates. - [Derivatives](https://docs.mercora.io/records/derivatives.md): Log futures fills, see your open position by contract month, and allocate fills to the physical contracts they hedge. - [Copilot](https://docs.mercora.io/copilot/overview.md): Ask about your trades, documents and money in plain words. Anything the Copilot would change waits for your Approve. - [Automations](https://docs.mercora.io/workflows/automations.md): Standing instructions that run on a schedule or when something arrives. Any change they propose waits for a person. - [Deal capture](https://docs.mercora.io/workflows/deal-capture.md): Turn deal recaps from email, WhatsApp, Teams or the Copilot into Inbox items you review, then create the contract. - [Hedging](https://docs.mercora.io/workflows/hedging.md): Turn a trader's WhatsApp confirmation or an API request into a broker order you approve in the Inbox, then record the fill. - [Freight rates](https://docs.mercora.io/workflows/freight-rates.md): Send carrier rate sheets and notices to Mercora, and confirm the changes it proposes to your freight master workbook. - [Integrations](https://docs.mercora.io/integrations/overview.md): Connect Mercora to the tools your team already uses, and control what Mercora may do with each one. - [Microsoft 365](https://docs.mercora.io/integrations/microsoft-365.md): Connect your Microsoft 365 organization, then turn on Email, Files and Teams for the Copilot and automations. - [WhatsApp](https://docs.mercora.io/integrations/whatsapp.md): Ask the Copilot from your phone, hand in deals and documents, capture hedge requests from trader groups, and approve automations by reply. - [Google Sheets](https://docs.mercora.io/integrations/google-sheets.md): Connect a Google account so Mercora keeps your hedge sheet up to date: a row for each approved hedge, completed with the broker's fill. - [QuickBooks Online](https://docs.mercora.io/integrations/quickbooks.md): Connect your QuickBooks Online companies to Mercora, check each connection, and disconnect them. - [External systems](https://docs.mercora.io/integrations/external-systems.md): Push reviewed invoices, B/Ls, contracts, deals and hedges to your CTRM, such as Agiblocks, and let the Copilot read its reporting data. - [Members](https://docs.mercora.io/admin/members.md): Invite teammates, change their role, and remove members from your workspace. - [Workspace settings](https://docs.mercora.io/admin/workspace-settings.md): Set your company profile and reporting currency, turn modules on, and configure books, entities, custom fields, invoice categories, contract templates and futures instruments. - [API keys](https://docs.mercora.io/admin/api-keys.md): Create, review and revoke the workspace API keys your own systems use to call Mercora. - [Introduction](https://docs.mercora.io/api-reference/introduction.md): Call Mercora from your own systems: base URL, authentication, scopes, errors and idempotency. - [List hedge books](https://docs.mercora.io/api-reference/hedge-requests/list-hedge-books.md): What this workspace can hedge: its active hedge rules, each with the `id` a request sends as `book`. On a workspace that books hedges in Agiboo, also each book's position and every position a request may name. - [Request a hedge](https://docs.mercora.io/api-reference/hedge-requests/request-a-hedge.md): A physical contract needs covering. The request becomes a hedge in the Mercora Inbox for an operator to send to the broker; nothing is sent from the API. A request that cannot be planned is still recorded: 201 with `state: failed` and the `reason` (unknown book, no Agiboo position, contract already… - [Get a hedge request](https://docs.mercora.io/api-reference/hedge-requests/get-a-hedge-request.md): Where a request stands, by Mercora's `id` from the POST response. A caller that lost the response sends the POST again with the same `external_id`. - [Start an automation run](https://docs.mercora.io/api-reference/automations/start-an-automation-run.md): Starts a run of an automation whose trigger is the API. The run works in Mercora; anything it would change waits for a person's approval there. 201 a new run, 200 a retry of an external_id already used with the same body, 404 no such automation in this workspace, 409 the automation doesn't run from… - [Answer a run that waits for your system](https://docs.mercora.io/api-reference/automations/answer-a-run-that-waits-for-your-system.md): Hands a run whose Wait for step waits on another system what it waited for; the run carries on from there. 202 the run carries on, 404 no such run of this automation in this workspace, 409 the run isn't waiting for a callback (already answered, or past its time limit). ## OpenAPI Specs - [openapi](/api-reference/openapi.json) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.