Pulsus Public API
Use the Pulsus Public API to securely integrate your applications with Pulsus. Start with authentication, then explore the available endpoints and API reference.
Where to start
- Authentication — learn how to authenticate and obtain an access token.
- API Reference — explore available endpoints, parameters, and schemas.
- Errors — understand error responses and HTTP status codes.
- Rate limits — learn about request limits and recommended usage.
Available APIs
Pulsus provides APIs through the Pulsus API and the Legacy API. Use the overview below to find the right API for your integration.
| Capability | Platform | Description |
|---|---|---|
| Application Distribution | Pulsus API | List applications, versions, installations, and distributions, and associate or remove applications from groups. |
| Application upload | Legacy API | Upload applications and distribute them to managed devices. |
| Devices | Legacy API | Retrieve device information and execute supported device operations. |
| Groups | Legacy API | Retrieve device groups and related group information. |
| Signal & location | Legacy API | Retrieve the latest signal strength and location information for managed devices. |
info
Authentication differs by API. The Public API uses OAuth 2.0 client credentials
(client_id and client_secret) to obtain a Bearer token. The Legacy
API uses an API token sent directly with each request. See the
Authentication guide for details.
Base URLs
Use the base URLs below to access Pulsus services.
| Pulsus API | Authentication | Legacy API |
|---|---|---|
https://eu.connect.pulsus.mobi | https://eu.auth.pulsus.mobi | https://eu.api.pulsus.mobi |
Need help?
Contact your Pulsus support channel for assistance. Never share client secrets, access tokens, or API tokens in tickets, screenshots, or public collections.