Which screen connects what
Inbound — other software reaching TRANXACT — is Platform › Published API and Platform › Access › Service Accounts. Outbound — TRANXACT reaching other systems — is Platform › Integration, Platform › Events & Webhooks and Agentic AI › Connect.
| الاتجاه | شاشة | الغرض منه |
|---|---|---|
| وارد | Platform › Published API › API Studio | The board over the published API: what is exposed, who holds a key, what each key could not do, recent calls. |
| وارد | Platform › Published API › Exposures | What may leave the company: a screen, its columns, its rows, and the verbs. |
| وارد | المنصة › واجهة برمجة التطبيقات المنشورة عملاء واجهة برمجة التطبيقات | The outside software holding a key; who it acts as; Issue key. |
| وارد | Platform › Published API › API Grants | Which client may use which exposure, with which verbs. |
| وارد | Platform › Published API › Allowed Software | Where a key may be presented from. |
| وارد | Platform › Published API › API Call Log | Every call made with a key, and why any was refused. |
| وارد | Platform › Access › Service Accounts | An identity for software that works like a person through the console’s own routes. |
| وارد | Agentic AI › Operate › Delegated Tasks | Tasks an agent handed to a licensed Claude worker, who connects to /api/v1/mcp/run. |
| مغادرة | Platform › Integration › Connector Catalog and Connections | What TRANXACT connects to (ERP, finance, CRM, directories, payment engines, clinical interfaces) and the configured connection to each. |
| مغادرة | Platform › Events & Webhooks › Webhooks and Webhook Deliveries | Events pushed to another system as they happen, and every delivery. |
| مغادرة | Agentic AI › Connect › Agent Connections and Discovered Tools | Outside tools and MCP servers the company’s own agents may call. |
Being told instead of asking: webhooks
Rather than polling the published API, a system can be sent events. A webhook names the events it wants (a record event is record.<module>.<screen>.<action>) and a target URL; each delivery is a POST of { "event", "data", "eventId", "sentAt" } with the headers x-tranxact-event, x-tranxact-delivery and x-tranxact-attempt, and, when the webhook has a secret, x-tranxact-signature: sha256=<HMAC-SHA256 of the exact body with that secret>. A delivery that fails is retried after 1, 3, 7 and 15 minutes up to the webhook’s retry limit; every attempt is on Webhook Deliveries.