RSS Feed

Current RSS endpoints

Pinrail already publishes RSS-style operational feeds from pinrail-platform today.

Current feed URLs:

• GET /v1/feeds/account.xml
• GET /v1/feeds/terminals/{terminal_id}.xml

Both endpoints return application/rss+xml and inherit the same authenticated account visibility rules as the rest of the developer surface.

Account feed

Use the account feed when you want a scoped, cross-terminal digest of visible activity.

The current account feed includes rows such as:

• terminal heartbeat and status changes
• recent transaction activity
• alert incidents
• switch journal observations tied to visible terminals

Per-terminal feed

Use the terminal feed when you want a lighter operational stream for one machine.

The current terminal feed covers categories such as:

• terminal status
• transaction activity
• switch journal events
• queued and completed command activity
• provisioning job activity
• alert incidents

Example requests

curl -sS \
  -H 'X-API-Key: $PINRAIL_API_KEY' \
  https://api.pinrail.xyz/v1/feeds/account.xml

curl -sS \
  -H 'X-API-Key: $PINRAIL_API_KEY' \
  https://api.pinrail.xyz/v1/feeds/terminals/TERM123.xml

Recommended use cases

RSS is a good fit when you want:

• human-readable syndication
• internal dashboard widgets
• simple polling by low-code tools
• sponsor-bank or operations digest views without building a webhook receiver first

Relationship to webhooks

Use RSS when you want visibility and lightweight consumption.

Use webhooks when you want:

• machine-to-machine automation
• signed push delivery
• faster event handling without polling
• testable destination registration and event subscriptions in the TMS

Contract discovery

Use GET /v1/integrations/catalog as the machine-readable index for which services currently expose RSS feeds and which service families they map to.