Help / Developers

Developer overview

Read and change a shop's orders from your own code or an AI agent, with REST or MCP.

The Tejas API lets a shop's own tools, and AI agents, work with the shop's transactions: list them, read them, decide on them, and place orders for customers.

REST and MCP are two doors to the same operations. They run the same code, check the same permissions and return the same JSON. A tool and its route cannot differ.

What you can do #

• Read. List transactions, read one, read its history, find a customer, browse what the shop sells.
• Decide as the seller. Confirm, reject, pack, fulfil, accept or refuse a customer's request, mark paid, record that a payment did not arrive, refund, and edit the lines.
• Act for a customer. Onboard a customer, set their cart, place it, edit it, or cancel it. You act by the customer's Tejas id (buyer_id), never by a phone number in a URL.
• Set up. Read and change the approval settings and the storefront, read the fee invoices, get the shop's entry link, run offers and promotions.

How a call works #

1. You send an API key. It names a shop and a member of that shop. See Authentication.
2. Tejas checks the member's role for the action. A role that may not act gets 403.
3. A change carries an Idempotency-Key. A retry never acts twice. See Idempotency.
4. Tejas answers with JSON. A refused move is an error with a status, a category and a code.

Money is always a decimal string such as "250.00", never a float. Times are ISO 8601. A phone number is only ever returned masked.

Where next #

• Authentication
• REST API
• MCP
• Rate limits

Last checked: 2026-11-07