1 Live Demo Entry Point
Environment | Base URL |
---|---|
Public demo | https://demo.ankatech.co/ |
Open the link in any modern browser. The Swagger UI loads with a drop‑down\ named Select a definition. Three OpenAPI definitions are published:
Definition name (UI) | Purpose |
---|---|
AnkaSecure Auth API | Obtain JWT access & refresh tokens. |
AnkaSecure Core API | All cryptographic & key‑management endpoints. |
AnkaSecure Admin API | Tenant / user / application administration. |
Mandatory order Always authenticate through Auth API first. Use the issued access token in both Core API and Admin API.
2 Authentication (API‑first)
The Auth API exposes Application and User flows. Both return an access token and an optional refresh token.
2.1 Human User login
POST https://demo.ankatech.co/api/authenticate/login
Content‑Type: application/json
{
"tenantId" : "11111111-1111-1111-1111-111111111111",
"email" : "[email protected]",
"password" : "demoAdmin12345!"
}
Successful 200 OK response (excerpt):
2.2 Application Client login
POST https://demo.ankatech.co/api/authenticate/app
Content‑Type: application/json
{
"clientId" : "eeeeeeee-eeee-eeee-eeee-eeeeeeeeeeee",
"clientSecret" : "allApp12345!"
}
Both flows are production capabilities --- the demo server is not limited in scope or lifetime, so you can script continuous tests.
2.3 Refresh flow
POST https://demo.ankatech.co/api/authenticate/refresh
Content‑Type: application/json
Authorization: Bearer <REFRESH‑JWT>
{
"refreshToken" : "<REFRESH‑JWT>"
}
A new access‑token is returned, optionally alongside a rotated refresh‑token if rotation is enabled for the tenant.
3 Authorise Swagger UI with your token
-
Select AnkaSecure Core API from the definition list.
-
Press the Authorize button (green padlock).
-
Paste the access‑token in the field named
bearerAuth
→ prefix withBearer
. -
Repeat for AnkaSecure Admin API when you need administrative calls.
Swagger now injects the header automatically:
Tip If a
401
is returned, re‑run the refresh call or perform a fresh login.
4 Quick Navigation
Capability | Tag (Core API) | Representative endpoint |
---|---|---|
List supported algorithms | Key Management | GET /api/key-management/supported-algorithms |
Generate a key | Key Management | POST /api/key-management/keys |
Encrypt / Decrypt (Base64) | Secure | POST /api/crypto/encrypt / /decrypt |
Sign / Verify (Base64) | Secure | POST /api/crypto/sign / /verify |
Streaming encryption | Secure Streaming | POST /api/crypto/stream/encrypt |
Rotate a key | Key Management | POST /api/key-management/keys/{kid}/rotations |
List HUMAN users | Admin API / Human Users Administration | GET /api/admin/humans |
All request & response schemas are fully documented inside Swagger. No undocumented behaviour exists on the demo host.
5 AnkaSecure SDK --- Quick Start
Full SDK docs, installers and copy‑paste examples live at SDK Overview . You'll find:
-
Maven/Gradle coordinates and version matrix.
-
End‑to‑end snippets (login, refresh, encrypt, streaming upload).
-
Ready‑made Spring Boot filter for automatic token injection.
-
Kotlin coroutines and RxJava helpers.
Hint: If you prefer scripting, download ankasecure CLI from the same page---the tool covers every demo scenario, including streaming file encryption.
6 Operational limits
Resource limit | Value |
---|---|
Max JSON payload size | 5 MB |
Max multipart file size (streaming APIs) | 5 MB (demo) |
Default JWT lifetime | 1 hour |
Refresh‑token lifetime | 72 hours |
Production customers can request limit adjustments via support@ankatech.co.
7 Change log
Date (UTC) | Change |
---|---|
2025‑05‑06 | First public release of consolidated Auth / Core / Admin demo documentation. |
© 2025 AnkaTech Co. All rights reserved.