Cryptolens API Documentation

This is the complete API documentation for connecting to the Cryptolens API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Cryptolens: Use the Devolens/Cryptolens Web API 3 to manage software licensing products, license keys, customers, users, resellers, messages, data objects, subscriptions, analytics, and license templates. Keep reading to get started.

Quickstart

Before you run your first Cryptolens request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Cryptolens connection — create or choose one in Connections. Note its connectionId.

Every Cryptolens action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/cryptolens/latest/actions/{actionSlug}

You need a MindCloud API Key and a Cryptolens connection. Then call an action such as Get Customer Licenses:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/cryptolens/latest/actions/get-customer-licenses" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Cryptolens account that should run the action. MindCloud stores and refreshes the Cryptolens credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Cryptolens actions

All 55 published actions for this Cryptolens version. Each page documents the endpoint, arguments, and response controls.

• PUTActivate
• POSTAdd Customer
• POSTAdd Data Object
• POSTAdd Feature
• POSTAdd Reseller
• PUTAssociate
• PUTBlock Key
• PUTChange Customer
• PUTChange Notes
• PUTChange Password
• PUTChange Reseller
• POSTCreate Key
• POSTCreate Key From Template
• POSTCreate Message
• POSTCreate Session
• POSTCreate Trial Key
• PUTDeactivate
• PUTDecrement Int Value
• PUTDissociate
• PUTEdit Customer
• PUTEdit Reseller
• PUTExtend License
• GETGet Customer Licenses
• GETGet Customers
• GETGet Events
• GETGet Key
• GETGet Keys
• GETGet License Templates
• GETGet Messages
• GETGet Object Log
• GETGet Reseller Customers
• GETGet Resellers
• GETGet Users
• GETGet Web API Log
• PUTIncrement Int Value
• PUTKey Lock
• GETList Data Objects
• GETList Products
• POSTLogin
• PUTMachine Lock Limit
• PUTRecord Usage
• POSTRegister
• POSTRegister Event
• DELETERemove Customer
• DELETERemove Data Object
• DELETERemove Feature
• DELETERemove Message
• DELETERemove Reseller
• DELETERemove User
• POSTReset Password Token
• PUTSet Int Value
• PUTSet String Value
• PUTTrial Activation
• PUTUnblock Key
• PUTUpload Values

Related apps

More apps on the Universal API, behind the same REST shape. Or browse all apps.

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms