Rackspace Cloud Office
Connect Rackspace domain, mailbox, alias, and DKIM context to Konrado.AI
Rackspace Cloud Office uses API credentials rather than the SSH installation command. Use it when support tickets ask about hosted email domains, mailboxes, aliases, or DKIM records.
What Is It?
The Rackspace Cloud Office integration lets Konrado.AI read email-account context from Rackspace while drafting replies. It helps support agents answer questions about domains, mailboxes, aliases, and DKIM without switching systems for every lookup.
What It Can Do
| Capability | How it helps support |
|---|---|
| Domain lookup | Confirm which Rackspace email domains are present for an account |
| Mailbox context | Help answer mailbox existence or account-context questions |
| Alias context | Check alias-related details when responding to forwarding or delivery questions |
| DKIM context | Help answer authentication and deliverability tickets that mention DKIM |
| Reseller subaccount lookup | Use me or a specific customer account number depending on the Rackspace account type |
| System status check | During investigations, Konrado.AI checks the Rackspace system status page to rule out platform-wide incidents |
What It Cannot Do
| Not supported | Why this matters |
|---|---|
| Create, delete, or modify mailboxes | The integration is documented for support context |
| Change aliases, DKIM, DNS, or passwords | Operators should perform changes in Rackspace after review |
| Send email or access mailbox contents | The integration should not expose private mailbox messages |
| Replace Rackspace account administration | Konrado.AI drafts replies; Rackspace remains the source of operational changes |
Data Access & Permissions
Use this section as the reference for compliance and SOP questions about what Konrado.AI can and cannot do with Rackspace Cloud Office data.
Every API call Konrado.AI makes is read-only. All 29 Rackspace API endpoints the integration consumes use HTTP GET — there are no calls that create, modify, or delete anything in your Rackspace account.
What Konrado.AI reads:
- Domains and alternate domains
- Mailbox settings and usage (Rackspace Email and Exchange)
- Email aliases
- Distribution groups
- Spam filter settings and safelist/blocklist entries
- DKIM status
- Customer account information (for resellers: subaccount names and numbers)
What Konrado.AI cannot do:
- Read the contents of any email
- Log into mailboxes
- Change any setting, mailbox, domain, or account
Complete list of API operations
For full transparency, here is every Rackspace API operation the integration can make. All 29 are HTTP GET (read) requests — there are no create, update, or delete operations anywhere in the integration.
| # | Operation | Request |
|---|---|---|
| 1 | List customer accounts | GET /v1/customers |
| 2 | Get customer account info (also used by Test Connection) | GET /v1/customers/{account} |
| 3 | List customer contacts | GET /v2/customers/{account}/contacts |
| 4 | Get a single contact | GET /v2/customers/{account}/contacts/{contactId} |
| 5 | List domains | GET .../domains |
| 6 | Get a domain | GET .../domains/{domain} |
| 7 | List alternate domains | GET .../domains/{domain}/alternatedomains |
| 8 | Get DKIM status for a domain | GET /v2/.../domains/{domain}/dkim |
| 9 | List Rackspace Email mailboxes | GET .../rs/mailboxes |
| 10 | Get a Rackspace Email mailbox | GET .../rs/mailboxes/{mailbox} |
| 11 | List Exchange mailboxes | GET .../ex/mailboxes |
| 12 | Get an Exchange mailbox | GET .../ex/mailboxes/{mailbox} |
| 13 | List aliases | GET .../rs/aliases |
| 14 | Get an alias | GET .../rs/aliases/{alias} |
| 15 | List distribution lists | GET .../ex/distributionlists |
| 16 | Get a distribution list | GET .../ex/distributionlists/{name} |
| 17 | List distribution list members | GET .../ex/distributionlists/{name}/members |
| 18 | List distribution list senders | GET .../ex/distributionlists/{name}/senders |
| 19 | List distribution list email addresses | GET .../ex/distributionlists/{name}/emailaddresses |
| 20 | Get domain spam settings | GET .../domains/{domain}/spam/settings |
| 21 | Get domain spam safelist | GET .../domains/{domain}/spam/safelist |
| 22 | Get domain spam blocklist | GET .../domains/{domain}/spam/blocklist |
| 23 | Get domain spam IP safelist | GET .../domains/{domain}/spam/ipsafelist |
| 24 | Get domain spam IP blocklist | GET .../domains/{domain}/spam/ipblocklist |
| 25 | Get mailbox spam settings | GET .../rs/mailboxes/{mailbox}/spam/settings |
| 26 | Get mailbox spam safelist | GET .../rs/mailboxes/{mailbox}/spam/safelist |
| 27 | Get mailbox spam blocklist | GET .../rs/mailboxes/{mailbox}/spam/blocklist |
| 28 | Get mailbox spam IP safelist | GET .../rs/mailboxes/{mailbox}/spam/ipsafelist |
| 29 | Get mailbox spam IP blocklist | GET .../rs/mailboxes/{mailbox}/spam/ipblocklist |
In addition, Konrado.AI reads Rackspace's public system-status page (HTML) during investigations to rule out platform-wide incidents. This is not an API call and does not touch your account.
Rackspace Cloud Office does not offer read-only or scoped API keys — a key inherits its Super Admin's full access. Konrado.AI only ever issues the read requests listed above, but because the key itself isn't restricted, we recommend a dedicated admin login and revoking the key if you remove the integration.
Security Model
Use Rackspace API User Key and Secret Key values, not your Rackspace control-panel password. Prefer a dedicated Super Admin login created specifically for the API — Rackspace attributes every key action to its owning admin, so dedicated credentials keep Konrado.AI activity distinct from human activity in your logs. Store the keys securely, and revoke them if the integration is removed.
Ticket Examples
- "Does this customer have a mailbox for billing@example.com?"
- "Is DKIM configured for this email domain?"
- "Which aliases exist for this mailbox?"
- "Why is mail authentication failing for this domain?"
- "Is this Rackspace reseller subaccount connected correctly?"
Prerequisites
- Access to Konrado.AI Integrations.
- A Rackspace Cloud Office Super Admin login. Super Admin access is required to create the API key — Standard and Limited Admins cannot. Konrado.AI then uses that key for read-only lookups only (see Data Access & Permissions); it never changes anything in your Rackspace account.
- The Rackspace customer account number, or
mefor a regular non-reseller account.
Rackspace API keys are unique to each administrator, and every action taken with a key is attributed to that admin in the Rackspace logs. Rackspace recommends creating a dedicated admin login for API use instead of using your personal profile, so your audit logs clearly separate application activity (Konrado.AI) from human activity. Give that admin Super Admin access and generate the API key from its profile.
Get Rackspace API Keys
Open My Account in Rackspace, then select My Profile.
In My Profile, open API Keys and use the User Key and Secret Key from the API key modal.
Use the Rackspace API User Key and Secret Key. Do not paste your Rackspace control-panel password.
Installation
In Konrado.AI, open Integrations > Applications, click Add Integration, and choose Rackspace Cloud Office.
Fill in the Rackspace API values:
| Field | What to enter |
|---|---|
| User Key | Rackspace API User Key |
| Secret Key | Rackspace API Secret Key |
| Customer Account Number | me for a regular (non-reseller) account, or the customer account number of the subaccount you want this integration to read |
| WHMCS Server ID | Leave blank for a single Rackspace account — see Multiple Rackspace Accounts |
Enter me if you are connecting your own Rackspace Cloud Office account — Konrado.AI reads the account the API keys belong to. If you are a reseller, enter the specific customer account number of the subaccount this integration should read, not me (see For Resellers).
For more information, see Rackspace's Cloud Office API key setup guide and the Rackspace Email & Apps API documentation.
For Resellers
If you resell Rackspace Cloud Office, a few things work differently:
meis not for resellers.meresolves to the account the API keys belong to — for a reseller that is your master reseller account, which does not itself hold your customers' domains and mailboxes. Leaving the field asmemeans Konrado.AI looks at the wrong account.- Enter the customer account number. In the Customer Account Number field, enter the account number of the subaccount you want this integration to read. To find it, open that customer's account in your Rackspace Reseller Control Panel and look at the top-right corner — the account number is shown next to the admin username, formatted as
adminusername (123456). Click that username menu to expand it. Copy the number (the digits only) into Konrado.AI. - One set of reseller API keys covers all customer subaccounts. You do not need separate keys per customer — the same reseller User Key and Secret Key work for every subaccount; only the customer account number changes per integration.
Multiple Rackspace Accounts
If you operate more than one Rackspace account, add one integration per account, each with its own API keys. Konrado.AI consults all of them automatically.
When WHMCS hosts the same product type across two Rackspace accounts, a service's Rackspace account is distinguishable only by the WHMCS server it is assigned to (for example, server 15 vs. server 8). Pin each integration to its WHMCS server with the WHMCS Server ID field so lookups route deterministically to the right account.
Once a second Rackspace account is connected, every Rackspace integration in your organization must have a WHMCS Server ID set. A single integration does not need one.
To find a server's ID in WHMCS admin, open Setup → Products/Services → Servers and click the server — the ID is the id parameter in the edit page URL.
Verify Success / Failure
Click Test Connection before saving. A successful test confirms that the API keys and customer account number can access the Rackspace Cloud Office API.
Troubleshooting
| Issue | What to check |
|---|---|
| Test Connection fails | Confirm the User Key, Secret Key, and Customer Account Number are correct |
| Account data is missing | Use me for a regular account, or the exact customer account number for a reseller subaccount |
| Authentication fails | Confirm you copied API keys from Rackspace My Profile > API Keys, not the control panel password |
| DKIM or alias context is missing | Confirm the connected Rackspace account can access the domain or mailbox in question |
| "Requires a WHMCS server ID" error when saving | You have more than one Rackspace integration — set the WHMCS Server ID on each one (see Multiple Rackspace Accounts) |
Remove
Delete the Rackspace Cloud Office integration in Konrado.AI and revoke the dedicated Rackspace API keys if they are no longer needed.