zapier-docs-master/modules/zappier/NATS.md

15 lines
883 B
Markdown

# NATS — zappier-edge
Zapier cloud still never connects to NATS. The edge process **does** publish and request on the private billing bus.
| Direction | Address | Peer | Body |
|-----------|---------|------|------|
| IN HTTPS | `/v1/*` | Zapier Platform app | JSON + `x-api-key` |
| OUT HTTPS | middleware `/zapier/v1/*` | verae-middleware | same tenant request |
| OUT NATS | `verae.billing.usage.recorded` | account-balance | meter event (`customerId`, `veraeUserId`) |
| OUT NATS | `verae.billing.payment.recorded` | account-balance / others | portal reload |
| OUT NATS | `verae.billing.credit.applied` | account-balance / others | admin/CS credit |
| OUT NATS | `verae.billing.statement.get` | account-balance | portal/admin review |
| OUT NATS | `verae.billing.balance.adjust` | account-balance | prepaid mutation |
Jobs, archive, and webhooks stay on middleware workers.