Access Control
Access Control
The Access Control section covers how your account is secured, how API access is managed, and how platform activity is tracked.
It contains three areas:
- API Tokens -- Create and manage tokens that allow your applications, scripts, and automation to authenticate with the Stacuity API without requiring a user login.
- Audit Activity -- A tamper-proof log of every administrative and configuration change made to your account, available for compliance, incident investigation, and operational accountability.
- Credentials -- Store and manage authentication credentials used by other parts of the platform, such as SMPP credentials referenced by Event Handlers.
Access Control Model
At present, all users with a Customer Portal account have access to all features within it. Configuration is account-wide. Anything set up by one user is visible and editable by any other user on the same account.
Overview
API Tokens allow your applications, scripts, and automation to interact with the Stacuity API without requiring a user login.
Navigate to Access Control → API Tokens.
The list shows each token's Name, Enabled status, and Created (UTC) timestamp.
- Click Create a Token.
- Enter a Name to identify the token.
- The Enabled toggle is on by default. Leave it enabled unless you want to create the token in a disabled state.
- Click Create.
After creation, the portal displays the token value once. Copy it immediately using the Copy to Clipboard button. It is not shown again.
The portal also provides a curl command you can use to test the token immediately:
curl -X GET "https://api.stacuity.com/api/v1/apitokens/verify" -H "Authorization: Bearer <your-token>" -H "Content-Type:application/json"
Token Security
- Never commit tokens to source code repositories. Use environment variables or a secrets manager.
- Revoke tokens immediately when a system is decommissioned or an integration changes.
- Use the Enabled toggle to temporarily disable a token without deleting it.
Editing a Token
- Click the edit icon next to the token.
- Update the Name or toggle the Enabled state.
- The token value is shown masked. Click the reveal icon to see it, or click Copy Token to Clipboard to copy it.
- Click Update.
Revoking a Token
- Click the delete icon next to the token.
- Confirm deletion.
Revocation is immediate. Any system using the token will receive 401 Unauthorised responses from the API.
Using the API
Include the token as a Bearer token in all API requests:
Authorization: Bearer <token>
Audit Activity
Audit Activity contains a history of administrative and configuration changes applied to Endpoints, Groups and Policies.
Overview
The Audit Activity log records every administrative and configuration change made to your account. It cannot be modified or deleted, and is available for compliance purposes, incident investigation, and operational accountability.
Navigate to Access Control → Audit Activity.
List View
| Column | Description |
|---|---|
| Timestamp (UTC) | Exact time of the action |
| Object | The type of object that was changed (e.g. API Token, Routing Policy, Endpoint Group) |
| Audit | The type of action: Created, Updated, or Deleted |
| Identifier | The UUID of the object that was changed |
| username | The user or API Token that performed the action |
| Remote IP | The IP address from which the action was performed |
Event Detail
Click the arrow on any audit row to expand it and see the full JSON record. The expanded view shows a structured before/after diff for updates, for example:
{
"update": {
"prior": {
"name": "my-token",
"allowLogin": true
},
"after": {
"name": "my-token",
"allowLogin": false
}
},
"auditType": "Updated",
"auditObject": "ApiToken"
}Credentials
Credentials are used for authentication with Stacuity and external services.
Overview
The Credentials section stores authentication credentials used by other parts of the platform, such as SMPP credentials referenced by Event Handlers.
Navigate to Access Control → Credentials.
The list shows each credential's Name, Moniker, Type, Created (UTC), and Updated (UTC).
Creating a Credential
- Click Add.
- Fill in the fields and click Create.
| Field | Required | Notes |
|---|---|---|
| Name | Yes | 2–100 characters. |
| Moniker | Yes | Used in the API. |
| Credential Type | Yes | Select the type of credential from the dropdown. |
Available credential types include SMPP and others depending on your account configuration. Select the type that matches the service you are authenticating with.
Updated about 2 hours ago
