All integrations

HotspotSystem

BUSINESS · COMMERCE & FINANCE

Hotspot locations, customers, subscribers, vouchers, and login transactions in the account they connected.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

hotspotsystem_get_customersREAD

Get a list of the resource owner's customers across every location -- the end users who signed in at a hotspot, with their contact details and, for social logins, the social profile the network returned via GET /v2.0/customers

api
hotspotsystem_get_locationsREAD

Get a list of the resource owner's hotspot locations (venues). Measured 2026-09-24, a location record carries id, name, address, city, state, zip and country_code -- more fields than the 2016 contract's id/name pair documents, and any of them may be named in `fields` via GET /v2.0/locations

api
hotspotsystem_get_locations_by_locationid_customersREAD

Get a list of the resource owner's customers at the specified location via GET /v2.0/locations/{locationId}/customers

api
hotspotsystem_get_locations_by_locationid_subscribersREAD

Get a list of the resource owner's subscribers at the specified location via GET /v2.0/locations/{locationId}/subscribers

api
hotspotsystem_get_locations_by_locationid_transactions_macREAD

Get a list of the resource owner's MAC transactions at the specified location via GET /v2.0/locations/{locationId}/transactions/mac

api
hotspotsystem_get_locations_by_locationid_transactions_paidREAD

Get a list of the resource owner's paid transactions at the specified location via GET /v2.0/locations/{locationId}/transactions/paid

api
hotspotsystem_get_locations_by_locationid_transactions_socialREAD

Get a list of the resource owner's social transactions at the specified location via GET /v2.0/locations/{locationId}/transactions/social

api
hotspotsystem_get_locations_by_locationid_transactions_voucherREAD

Get a list of the resource owner's voucher transactions at the specified location via GET /v2.0/locations/{locationId}/transactions/voucher

api
hotspotsystem_get_locations_by_locationid_vouchersREAD

Get a list of the resource owner's access vouchers at the specified location. NOTE: measured 2026-09-24 this endpoint answers 500 {"error":"Cannot read property 'currency' of undefined"} on an account whose location has no currency configured -- a provider-side defect, not a tool defect via GET /v2.0/locations/{locationId}/vouchers

api
hotspotsystem_get_locations_optionsREAD

Get the resource owner's locations as a flat id/name option list for a picker, including the synthetic id `0` meaning All locations. Takes no paging or field parameters via GET /v2.0/locations/options

api
hotspotsystem_get_meREAD

Verify the resource owner's credentials, returning the operator's numeric userId and operator name. This is the provider's own credential check: a valid key answers 200 and any other value answers 401 {"error":"Invalid authentication!"} via GET /v2.0/me

api
hotspotsystem_get_pingREAD

Find out whether the HotspotSystem API is reachable. Measured 2026-09-24: this endpoint answers 200 {"ping":"pong"} with NO credential at all, so a 200 here proves the API is up and proves NOTHING about the connection's key -- use Verify credentials for that via GET /v2.0/ping

api
hotspotsystem_get_subscribersREAD

Get a list of the resource owner's subscribers across every location -- the end users holding a recurring subscription rather than a one-off session via GET /v2.0/subscribers

api
hotspotsystem_get_transactions_macREAD

Get a list of the resource owner's MAC transactions across every location -- sessions started by device address, with the sign-in form's answers via GET /v2.0/transactions/mac

api
hotspotsystem_get_transactions_paidREAD

Get a list of the resource owner's paid transactions across every location -- sessions bought with a card or other payment, with the amount and currency via GET /v2.0/transactions/paid

api
hotspotsystem_get_transactions_socialREAD

Get a list of the resource owner's social transactions across every location -- sessions started through a social network login, with the social profile the network returned via GET /v2.0/transactions/social

api
hotspotsystem_get_transactions_voucherREAD

Get a list of the resource owner's voucher transactions across every location -- sessions paid for with an access voucher, with the amount and currency via GET /v2.0/transactions/voucher

api
hotspotsystem_get_vouchersREAD

Get a list of the resource owner's access vouchers across every location, with each voucher's code, traffic and time limits, price and currency. NOTE: measured 2026-09-24 this endpoint answers 500 {"error":"Cannot read property 'currency' of undefined"} on an account whose location has no currency configured -- a provider-side defect, not a tool defect via GET /v2.0/vouchers

api

Put HotspotSystem behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.