Pradeo Security API

Appearance

API Basics ​

Understanding the structure and architecture of the Pradeo Security API.

Multi-Tenant Architecture ​

Pradeo Security uses a multi-tenant architecture where each organization has its own isolated environment. Your API endpoint is specific to your tenant.

URL Format ​

https://api.<tenant>.pradeo-security.com

Where <tenant> is your unique organization identifier provided by Pradeo Security.

Example ​

If your tenant ID is acme-corp:

https://api.acme-corp.pradeo-security.com

Finding Your Tenant ID ​

Your tenant ID is provided during setup. To verify it:

  1. Contact your Pradeo Security administrator
  2. Check your onboarding documentation
  3. Look in your account settings/dashboard
  4. Check your API key credentials documentation

API Paths ​

All API endpoints are prefixed with the API version:

https://api.<tenant>.pradeo-security.com/v2/{endpoint}

Examples ​

Authentication:

bash
https://api.acme-corp.pradeo-security.com/v2/authentication/token

Devices:

bash
https://api.acme-corp.pradeo-security.com/v2/devices

Statistics:

bash
https://api.acme-corp.pradeo-security.com/v2/statistics

Device Groups:

bash
https://api.acme-corp.pradeo-security.com/v2/device-groups

Important Notes ​

Data Isolation ​

✓ Your data is isolated:

  • Data is completely separate between tenants
  • Cannot access other tenants' data
  • Credentials only work for your specific tenant

API Compatibility ​

✓ Consistent API:

  • Endpoints are standardized across all tenants
  • Request/response formats are identical
  • Same API version (v2)

Rate Limiting ​

Rate limiting is enabled on all requests:

  • Standard limits: 1000 req/min
  • If you exceed the limit, you'll receive a 429 Too Many Requests response

Next Steps ​