--- title: Rackspace API Integration on Truto slug: rackspace category: Helpdesk canonical: "https://truto.one/integrations/detail/rackspace/" --- # Rackspace API Integration on Truto **Category:** Helpdesk **Status:** Beta ## MCP-ready AI tools Truto exposes 11 tools for Rackspace that AI agents can call directly. - **list_all_rackspace_accounts** — List Rackspace accounts available to the authenticated user for viewing and ticket creation. Returns: name, id, rcn, serviceLevel, severities, type, permission, tags, npsOptOut. Max 500 per page. - **list_all_rackspace_categories** — List Rackspace ticket categories available for ticket creation. Returns: id, name, description, classification, subcategories. - **list_all_rackspace_tickets** — List Rackspace support tickets. Returns one record per ticket including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. - **create_a_rackspace_ticket** — Create a new Rackspace support ticket. Returns the created ticket including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. Required: accountId, subject, category, subcategory, comment.text. - **get_single_rackspace_ticket_by_id** — Get a single Rackspace support ticket by id. Returns the full ticket object including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. Required: id. - **update_a_rackspace_ticket_by_id** — Update a Rackspace support ticket by id, setting its status to Closed or replacing its resource list. Returns an empty 204 response on success. Required: id. - **rackspace_tickets_add_comment** — Add a comment to an existing Rackspace support ticket. Returns an empty 204 response on success. Required: ticket_id, comment.text. - **rackspace_attachments_upload** — Upload a file in Rackspace via multipart form data. Returns: expires, max_file_count, max_file_size, signature, redirect_url, url, uuid. Required: filename. The upload URL expires within 10 minutes and the returned UUID must be submitted with a ticket update to associate the file with a ticket. - **list_all_rackspace_resources** — List Rackspace resources the user has access to, used to select a category during ticket creation. Returns: id, accountId, name, platform, type, location, _links, network. Max 500 results per page. - **list_all_rackspace_ticket_events** — List Rackspace consolidated ticketing events from the CloudFeeds Atom feed for a specified account. Returns: id, updated, published, title, category, link, content. Required: account_id. - **create_a_rackspace_token** — Authenticate to the Rackspace Cloud Identity service by submitting username and API key credentials to obtain an authentication token. Returns the access object containing the token (id, expires, tenant), service catalog with endpoint URLs, and user information with roles. Credentials are supplied automatically from the integration's stored auth configuration. ## How it works 1. **Link your customer's Rackspace account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Rackspace.** The Proxy API is a 1-to-1 mapping of the Rackspace API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Embed Rackspace ticketing in your ITSM platform** — Let enterprise customers running on Rackspace managed cloud escalate incidents from your helpdesk directly to Rackspace's Fanatical Support engineers, without leaving your product. - **Auto-create Rackspace tickets from monitoring alerts** — Give observability and APM customers a way to convert critical alerts into Rackspace support tickets automatically, with diagnostic logs and affected resources attached for faster triage. - **Power multi-tenant MSP dashboards** — Enable MSPs and RMM platforms to pull tickets across every Rackspace account they manage into a single pane of glass, so they can prioritize incidents across their entire client base. - **Map support tickets to cloud infrastructure** — Help cloud management platforms tie active Rackspace tickets to specific VMs, load balancers, and databases so users can see which assets have open support cases in context. - **Sync ticket activity into customer-facing portals** — Let SaaS platforms mirror Rackspace ticket updates, comments, and status changes into their own client portals in near real time, so end users never have to log into the Rackspace portal. ## What you can build - **Two-way ticket sync** — Create, fetch, and update Rackspace tickets from your product while pushing status changes and comments back to your internal ticket record. - **Alert-to-ticket automation** — Programmatically open categorized Rackspace tickets from monitoring events, tagging them to the correct resource and category on creation. - **Attachment-enabled diagnostic hand-offs** — Upload logs, crash dumps, and screenshots to Rackspace tickets and post an accompanying comment so support engineers get full context in one action. - **Event-driven ticket activity feed** — Poll ticket events to surface a live activity stream of Rackspace agent replies and status changes inside your app. - **Resource-aware ticket forms** — Prefill ticket creation forms with the customer's actual Rackspace resources and category options fetched at runtime, eliminating manual lookups. - **MSP multi-account console** — List and switch between all Rackspace accounts a customer manages, then aggregate tickets across them into a unified incidents view. ## FAQs ### How does authentication to Rackspace work through Truto? Rackspace uses token-based authentication. Truto handles the token exchange via the create_a_rackspace_token flow and manages refresh transparently, so your end users only need to supply their Rackspace credentials once during connection. ### Can I manage tickets across multiple Rackspace accounts for the same customer? Yes. list_all_rackspace_accounts returns every account tied to the authenticated user, which is essential for MSPs and agencies that operate on behalf of multiple client tenants under a single connection. ### What ticket operations are supported? You can list tickets, fetch a single ticket by ID, create new tickets, update existing tickets, and add comments. You can also upload attachments and list ticket events to track updates over time. ### How do I get real-time updates on ticket changes? Rackspace exposes ticket activity via list_all_rackspace_ticket_events, which is backed by the CloudFeeds Atom feed. You can poll this endpoint through Truto to detect new agent replies, status changes, and other lifecycle events. ### Can tickets be tied to specific cloud resources? Yes. list_all_rackspace_resources returns the customer's managed assets, and list_all_rackspace_categories returns valid ticket categories. You can reference these when calling create_a_rackspace_ticket to associate an incident with the correct asset and classification. ### How are file attachments handled? Use rackspace_attachments_upload to push logs, diagnostics, or screenshots to a ticket, then use rackspace_tickets_add_comment to provide context. Truto normalizes the upload flow so you don't need to manage Rackspace's multipart quirks directly.