Onboard your Orca Security environment so AiStrike can fetch cloud security data via API.◼︎
1. Prerequisites
-
An Orca Security account with permission to create API Tokens.
-
Know which Orca region your tenant is hosted in (see table in Section 3) — this determines the base URL you'll use.
2. Creating an API Token from the UI
-
Log in to Orca using your region's domain (see table below).
-
Go to Settings → Users & Permissions → API. (This lists all existing tokens; here you can also copy your Organization UUID.)
-
Click Create API Token (labeled Add API Token in some tenants).
-
Configure:
-
Name — unique identifier for the token.
-
Description — purpose.
-
Never Expire — check for a permanent token; otherwise set an Expiration date (expired tokens stay visible but stop working).
-
Service Token — check this for integrations/automation. A service token is not tied to a user account (survives if the creating user is removed), but it is permanently scoped to the creating user's permissions at creation time.
-
Role — pick the role granting required permissions (use Viewer for read-only).
-
Scope (optional) — leave unchecked for access to all cloud accounts/business units, or check "Scope access to specific resources" to limit to selected Accounts, Business Units, or Shift-Left/AppSec projects.
-
-
Click Add → Continue.
-
Copy and store the token immediately. ⚠️ It cannot be retrieved again after you click Continue.
3. Region-specific base URLs
The API is region-locked; you must use the domain matching your tenant:
|
Region |
Base URL |
|---|---|
|
US (default / Global) |
|
|
Europe |
|
|
Australia |
|
|
India |
|
|
Israel |
|
|
Brazil (SA) |
|
|
Indonesia |
|
|
GovCloud |
|
4. Connector configuration
|
Field |
Description |
|---|---|
|
Base URL |
Your region-specific Orca base URL from the table above |
|
API Token |
The token generated in Section 2 |
For help with setup, reach out to the AiStrike support team.