TRANXACT.AI मदत

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 StudioThe board over the published API: what is exposed, who holds a key, what each key could not do, recent calls.
येणारेPlatform › Published API › ExposuresWhat 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 GrantsWhich client may use which exposure, with which verbs.
येणारेPlatform › Published API › Allowed SoftwareWhere a key may be presented from.
येणारेPlatform › Published API › API Call LogEvery call made with a key, and why any was refused.
येणारेPlatform › Access › Service AccountsAn identity for software that works like a person through the console’s own routes.
येणारेAgentic AI › Operate › Delegated TasksTasks an agent handed to a licensed Claude worker, who connects to /api/v1/mcp/run.
बाहेरPlatform › Integration › Connector Catalog and ConnectionsWhat TRANXACT connects to (ERP, finance, CRM, directories, payment engines, clinical interfaces) and the configured connection to each.
बाहेरPlatform › Events & Webhooks › Webhooks and Webhook DeliveriesEvents pushed to another system as they happen, and every delivery.
बाहेरAgentic AI › Connect › Agent Connections and Discovered ToolsOutside 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.