# Building endpoints in AmunCore

> An endpoint is a REST URL in front of a table, a stored procedure, an external API or a Shape. Every endpoint gets the same API keys, permissions, row rules, rate limits and audit trail.

## Table endpoints (visual builder)

- Load the database's tables and pick the columns to expose. The primary key is detected for you.
- Add joins, filters and combined columns, with a live SQL preview.
- Test the connection before saving.
- Clone an endpoint to make a similar one quickly.
- Bulk create: tick many tables and get one read endpoint per table in one step.
- ERP templates: ready-made mappings for Microsoft Dynamics, SAP, Oracle, QuickBooks, Xero, Zoho and more.
- Every query is parameterized, so values never become SQL.

## Stored procedures

Expose an existing stored procedure as an endpoint. Input parameters come from the query string (GET) or the JSON body (POST); output parameters and result sets are returned as JSON.

## External APIs (passthrough)

An endpoint can forward the request to an API you already use, such as a partner service, a payment provider or another department's system. Callers use one AmunCore key instead of the upstream credentials, and the call gets AmunCore's limits and audit log. Destinations must first be approved on an allowed-hosts list. APIs that answer in XML are supported.

## Shapes: fixed document formats

A Shape produces the exact document a partner or authority requires (nested objects, totals, formulas, checks) from tables you cannot change.

- Build it in a designer, with filters, sorting and values passed by the caller (for example `?id=INV-1`).
- Check the result against the required structure before publishing.
- Answer in JSON or XML, for example UBL e-invoices in the UAE.
- Frozen copies keep each document byte for byte with its SHA-256 fingerprint, the Shape version, the values passed and who asked, as proof of exactly what was sent.
- The formula assistant is built in and needs no outside AI service.

## Endpoint descriptions

A clear description on each endpoint tells AI assistants what it holds, so they pick the right one. It also appears in the generated API documentation.

## Live feed for Excel and Power BI

An endpoint that reads (GET) can have a live feed: a secret link that Excel and Power BI read and refresh, with no key to type. In Endpoints, press Feed, then Make a link. Two links are shown once: CSV for Excel (Data, From Web) and JSON for Power BI (Get data, Web, Anonymous). The feed reads with the access of the person who made it (row and column rules), up to 20,000 records, at most 240 reads an hour; it stops when that person is switched off. A new link replaces the old one at once; Switch off deletes it. Only a hash of the link is kept.

Deleting an application (its Edit page, Delete Application) first lists, by name, everything that goes with it: its endpoints, the assistants and agents that use it (also only in their steps), the Client Connectors that share it, the App Builder apps that show its data, documents or data files (or whose Ask block talks to an assistant that goes), its live feed links, and anything an earlier delete left behind (marked left over). Type its name to confirm; a loader shows each step while it is deleted. Your database itself is never touched.

Restoring: a deleted application can be restored for 7 days (Applications, Recently deleted). Every name and address is checked first (application name and API address, assistant, App Builder app and Client Connector names and web addresses); anything used now gets a free one, shown before restoring. Live feed links, open client sign-ins, run history and usage counts are not restored. Delete for good removes a kept application at once.

## Related

- [REST API reference](https://amuncore.com/docs/rest-api.md)
- [Security and access control](https://amuncore.com/docs/security.md)
- [AmunCore overview](https://amuncore.com/llms.txt)
