Skip to main content
wede provides official SDKs for five platforms. They add the offline layer to your applications. Operations captured without connectivity stay on the device and are synchronised automatically when the connection returns. Field teams receive messages and reply when there is no data connection. Devices are registered with the platform and removed from it.

​
Every device accounts for what it captured

From version 2.5.0, every operation a device captures with no network carries the identity of that device and its place in the device’s own numbering, sealed on the device before it is sent. When the operations reach wede, the Devices page shows for that phone, tablet or terminal what arrived, what is still missing and whether its record is intact, exactly as for any other machine. A device registers itself with wede before it sends its first operations, so every operation is attributed to it from the start. Nothing changes in your code: update the SDK and keep capturing as before. Applications on earlier versions keep working.

​
How to get access

1

Agreement

Your organisation signs an agreement with wede (contract, NDA or MOU) that includes access to the SDKs.
2

Access enabled

wede enables access for your organisation.
3

Download

Company admins and technical users open Downloads in the wede dashboard, accept the SDK terms of use and download the SDK for their platform, with installation instructions.
4

Updates

New versions appear in Downloads, and company admins are notified by email.

​
How the SDKs are protected

Each download is a unique copy for your organisation, delivered compiled and without source code. Copies identify themselves to the wede API, and wede can revoke a copy used outside the agreement. Downloads are open while the agreement and the annual licence are in force. Copies already in use keep working unless they are revoked.

​
Credentials

  • On a server, use a tenant API key (wede_live_... or wede_test_...) and keep it secret.
  • In a mobile app or a browser, sign the user in and use the session token. Never ship an API key in an app: anyone can extract it. The API accepts cross-origin requests from any origin (it authenticates only by headers, never by cookies), so a web app can use the session token directly.
A session token lasts 8 hours. Sign in again and give the SDK the new token. Five failed sign-in attempts lock the account for 15 minutes. What a session token can call depends on the user’s role. For example, sending events online needs company_admin, company_tech or corporate_client, while every tenant role can sync operations captured offline. A call outside the role returns 403. See Authentication.

​
Without an SDK

Server-to-server integrations can call the REST API directly with an API key. See the API reference.