Can AI agents automate LINK Mobility?

LINK Mobility is automatable today through its messaging APIs. This record is the LINK Mobility CPaaS, including MyLINK and the Common SMS platform. It is not Sinch, Infobip, or Twilio. The about page says LINK is a CPaaS headquartered in Oslo. The API index lists MyLINK APIs for multichannel messaging, SMS, email, and WhatsApp, plus older Common platform documents, including a SOAP web service and an SMPP interface. The Common SMS REST document, version 2.8 updated September 23, 2026, sends mobile-terminated SMS. Assigned base URLs include https://eu.linkmobility.io/sms. Preferred auth is OAuth 2.0 client credentials: POST /auth/token with grant_type=client_credentials, where client_id and client_secret are the username and password from Support. The token response includes access_token, token_type Bearer, and expires_in, and the example expires_in is 3599. Later calls send Authorization: Bearer. The same document also allows HTTP Basic with the Support username and password. POST /sms/send submits one message as JSON and requires platformId and platformPartnerId from Support. Delivery reports can be sent to a customer URL as JSON or as an HTTP GET or POST. MyLINK portal credentials are a client id and client secret created by an admin in the portal. This pass did not open the MyLINK SMS token exchange, so that portal secret is not treated as a second proven grant. No first-party MCP page was opened. iPaaS catalogs were not opened. Computer-use viability is unassessed. The API scores 7 and is the best path.

Best path today: api · Overall automatability: 7/10