Googleapis Proximitybeacon

Connector for the googleapis-proximitybeacon API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://proximitybeacon.googleapis.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• proximitybeacon_beacons_list — GET /v1beta1/beacons — Searches the beacon registry for beacons that match the given search criteria. O
• proximitybeacon_geteidparams — GET /v1beta1/eidparams — Gets the Proximity Beacon API's current public key and associated parameters use
• proximitybeacon_namespaces_list — GET /v1beta1/namespaces — Lists all attachment namespaces owned by your Google Developers Console project.
• proximitybeacon_beacons_get — GET /v1beta1/{beaconName} — Returns detailed information about the specified beacon. Authenticate using an [
• proximitybeacon_beacons_attachments_list — GET /v1beta1/{beaconName}/attachments — Returns the attachments for the specified beacon that match the specified namesp
• proximitybeacon_beacons_diagnostics_list — GET /v1beta1/{beaconName}/diagnostics — List the diagnostics for a single beacon. You can also list diagnostics for all

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: proximitybeacon_beacons_list
# (attach an 'oauth' credential to the task — no inline secrets)