Sigfox (BYOK)

Sigfox (BYOK) — connector documentation

• MCP endpoint: https://byok-sigfox.connectorbay.com/mcp
• REST API: POST https://byok-sigfox.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sigfox.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Sigfox Sigfox API user login, sent in the X-Upstream-Key header and the Sigfox API user password (use an API user with read-only profiles) in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-sigfox.connectorbay.com/health · Tool schemas: https://byok-sigfox.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-sigfox · agent@connectorbay.com

What Sigfox (BYOK) is for

Sigfox (BYOK) lets an AI assistant read your own Sigfox data through the Sigfox API with a key you supply (Sigfox API user login). Read-only: 11 tools (list_devices, get_device, list_device_messages, get_device_message_counts, list_device_types, get_device_type, list_device_type_callbacks, list_contracts, get_contract, list_groups, get_group). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.sigfox.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sigfox. Sigfox and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Sigfox devices have not communicated recently?"
• "Show Sigfox device 1A2B3C"
• "What did Sigfox device 1A2B3C send in the last day?"
• "How many messages did Sigfox device 1A2B3C send this week?"
• "Which Sigfox device types do I have?"
• "Show Sigfox device type 5730"

What it does

• list_devices: List devices with name, device type, contract, group, last communication time, signal quality, state and token status. The PAC and certificate keys are not returned.
• get_device: Get one device: name, type, contract, group, last communication time, signal quality, state and token details. The PAC and certificate keys are not returned.
• list_device_messages: List the uplink messages a device sent: time, payload data, signal quality, sequence number and frame count.
• get_device_message_counts: Count the messages a device sent in the last day, week and month.
• list_device_types: List device types with name, description, downlink mode, payload type, keep-alive, contract and group.
• get_device_type: Get one device type: name, description, downlink mode, payload type, keep-alive, contract and group.
• list_device_type_callbacks: List the callbacks of a device type: id, type, subtype, and whether each is enabled or dead. Callback targets and payload configuration are not returned.
• list_contracts: List contracts with start and end times, token usage, message limits, pricing model, subscription plan and renewal settings.
• get_contract: Get one contract with dates, token usage, message limits, pricing model and renewal settings.
• list_groups: List groups with name, description, type, time zone and whether each is a leaf or an account.
• get_group: Get one group with name, description, type and time zone.

BYOK key

You bring your own Sigfox Sigfox API user login (https://support.sigfox.com/docs/api-credential-creation). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.sigfox.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://support.sigfox.com/apidocs (the API this connector calls, with a BYOK key)

Live from the Sigfox API (api.sigfox.com) with a BYOK key; documentation: https://support.sigfox.com/apidocs. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sigfox. Sigfox and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Sigfox account.

Built for: Worldwide. Languages: English.

Sigfox (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Sigfox (BYOK) is. Sigfox (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Sigfox data: Read your Sigfox IoT network account: devices, device types, uplink messages, contracts, callbacks and groups with your own API user credentials. You bring your own Sigfox Sigfox API user login; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Sigfox call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.sigfox.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Sigfox rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Sigfox receives. The request we make on your behalf, including the key and the arguments, under Sigfox's own terms and privacy policy. Sigfox acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Sigfox gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Sigfox data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Sigfox (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Sigfox at any time to end all access.

Children. Sigfox (BYOK) is a general-audience service operated by the adult using the assistant, under Sigfox's own age rules.

Changes. We will post changes here with a new effective date.

Sigfox (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Sigfox (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Sigfox (BYOK) provides: Read your Sigfox IoT network account: devices, device types, uplink messages, contracts, callbacks and groups with your own API user credentials. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Sigfox credentials and only access data you are allowed to access. Sigfox's terms apply to your use of Sigfox; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sigfox. Sigfox and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Sigfox returns, lightly trimmed; it may be incomplete, delayed or changed by Sigfox. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Sigfox account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Sigfox's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Sigfox may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Sigfox key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Sigfox takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-sigfox

Sigfox (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-sigfox.connectorbay.com/mcp
• REST API: https://byok-sigfox.connectorbay.com/openapi.json
• Live status: https://byok-sigfox.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Sigfox (BYOK) never asks for them.