Overview

This section is Allaria's brokerage API: everything you do with an account after it exists.

• Placing orders.
• Reading positions and movements.
• Buying and selling dollars through MEP.
• Operating mutual funds.
• Running savings plans.
• Reading market data.
• Investing a PSP's customer balances in mutual funds.

Allaria is a licensed ALyC (Agente de Liquidación y Compensación, a broker-dealer registered with the CNV).

Before you start

Three things have to be in place, in order. The endpoints here assume all of them.

1. Credentials and a token. See Get started.
2. An open account. Nothing here creates accounts. The account comes from Onboarding if your company is not an obliged entity, or from Account Opening if it is.
3. The account's number. Every endpoint in this section identifies the account by its comitente — the number Onboarding or Aperturas returned. It appears under several different names depending on the endpoint; see Account identifiers.

One number, several spellings

These are all the comitente:

• account-id in Trading paths;
• account_number in most response bodies;
• accountNumber on some MEP endpoints.

The cvu is the one identifier that is not the same thing — it belongs to an Allaria+ wallet account, not a brokerage account.

What each section is for

Section	Use it when	Notes
Movements	You need an account's transaction history, or want to be notified when funds arrive	listen-fund-deposits is a webhook you receive, not an endpoint you call
Portfolio Position	You need what an account currently holds and what it is worth	A snapshot. For the trading-system view instead, see get-oms-position and get-esco-position under Trading
Savings Plans	Your client invests a recurring amount into a managed plan	Terms and conditions have to be accepted for each new subscription
Market Data	You need prices: the dollar exchange rate, or mutual fund quotes	Read-only, not account-scoped, so it needs no comitente
Trading	Your client buys or sells: orders, MEP dollars, mutual funds, fees, risk profile, signed documents	The largest section. Ordered roughly in the sequence you need it
Services for PSPs	Your company is a PSP and invests its customers' balances in an Allaria mutual fund	An end-to-end flow with its own overview. Only for PSPs

Trading, in the order you need it

The Trading section has eight subsections, listed in the sidebar in the order you need them. The sequence for placing a client's first order is:

1. Investment Profile — read the client's PRI (risk level). It decides which instruments they may operate. An order outside their profile is rejected.
2. Documents — the client has to have signed the terms and conditions, and for some operations a daily affidavit. check-document-signed tells you whether they have.
3. Reference Data — get-byma-data for the tradable instruments, get-holiday-assessment to know whether the market is open.
4. Fees — calculate-fees before confirming, so you can show the client the real cost.
5. Operations — check-operation-allowed is the pre-flight check that combines the above.
6. Orders — place it: market, limit or stop-limit. Then get-order-by-id or get-orders-by-account to follow it.

MEP Operations and Mutual Funds are separate flows that do not go through Orders:

• MEP Operations buys or sells US dollars through the securities market. Two legs — buy a bond in pesos, sell it in dollars — which Allaria runs for you:
  1. Quote with get-mep-quote.
  2. Execute with execute-mep-operation.
  3. Poll get-mep-operation-status.
  4. create-mep-transfer moves the resulting dollars out.
• Mutual Funds subscribes to and redeems FCIs with create-mutual-fund-operation, then get-mutual-fund-operation-by-id.

Paths that look inconsistent

Three shapes appear in this section and all three are correct — they reflect how each service is reached, not an error in the docs.

Shape	Sections	Why
/v1/bymas/allaria/...	Movements, Portfolio Position	bymas is an internal service name that ended up in the public path. Treat it as an opaque segment
/v1/broker/... and /v1/operations/...	Trading	Same situation, different service
/v1/psp/fondos/{fondo}/cotizacion, /v1/psp/tenencia-val	Services for PSPs	The service behind them names its routes in Spanish. Send them exactly as documented

There is nothing to configure for any of this. See Systems you will see named if a name in a path or an error message is unfamiliar.

Common failure modes

Symptom	Cause
403 on every endpoint in one section	Your credentials are not authorized for that product — contact integraciones@allaria.com.ar
404 on an account that exists	You sent a cvu where a comitente was expected, or the reverse. See Account identifiers
An order is rejected as not allowed	The client's PRI does not cover that instrument, or a required document is unsigned. Run check-operation-allowed first
An operation fails outside market hours	The market is closed. Check get-holiday-assessment
Request times out with no status code	Your IP is not whitelisted — see Access