Connect Redstor

Redstor is cloud backup built for MSPs. You manage your customers (Redstor calls them companies) from the RedApp, its web console, and protect their Microsoft 365, Google, Azure, machine and other data into Redstor's storage. StackJack talks to Redstor through the RedAPI, the same interface Redstor documents for partners who want to automate the RedApp.

Connecting Redstor to StackJack gives your AI assistant a family of redstor_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• Answer the morning question: which customers had failed, missed or partly failed backups, per product and per account, and the error messages behind each failure
• Check restores: the same views for restore jobs, so you can prove recoverability for an audit
• Look at storage and data residency: the storage accounts under a customer, the regions Redstor offers and how many accounts a customer has in each
• Reconcile billing: what each customer consumes by product (protected data, seats, workloads, licensed users), for one customer or all of them, as of a date, and which subscriptions each customer holds
• Find your way around: your own partner company, your customer list, the product catalog with its editions, and the RedApp users of a company

It can also make changes, on the Pro tier:

• Onboard and offboard customers: create a customer or partner company with an admin contact, enable or disable one, delete one, or move a customer to another partner
• Change what a customer is subscribed to: add a product subscription, convert a trial to a paid subscription, or remove a subscription

Reading is free. Every change needs the Pro tier, and every change is labelled so your AI assistant asks before running it.

Before you start: what Redstor requires

These are gated at the partner level by Redstor, not by StackJack, and you need all of them before the first credential exists:

• You must be a Partner Admin in the RedApp. Company Admins cannot use the RedAPI.
• Your partner must be on Redstor's new pricing plan. Redstor says the RedAPI is only available on it. If you are still on the older plan, speak to your Redstor account manager about upgrading.
• The RedAPI icon must be enabled for your partner. If you cannot see the RedAPI icon in the RedApp, ask your account manager to arrange access.

StackJack cannot do any of that for you, and nothing about Redstor's side needs approval from StackJack.

How StackJack signs in to Redstor

Redstor does not use an API key or a password. You create a service account in the RedApp, and Redstor gives you two things: a Client ID (shown on the service account) and a private key, a small text file with a .jwk ending that Redstor lets you download when the key is created. You paste both into StackJack.

There is no web address to enter. Redstor runs one shared service for every customer, so there is nowhere to put one.

Behind the scenes StackJack uses the private key to sign a short-lived sign-in request, and Redstor answers with an access token that lasts about an hour. StackJack renews it on its own, so there is nothing to rotate on a schedule. The private key never leaves StackJack's encrypted store and is never sent to Redstor itself, only used to sign.

Steps

1. Check the three requirements above. You need to be a Partner Admin, on the new pricing plan, with the RedAPI icon enabled.
2. Create a service account. In the RedApp open the RedAPI icon, choose Service accounts and add a service account. Choose the partner it belongs to and which customers it can reach, or tick Auto-assign all future customers so new customers are picked up without another visit. Only customers assigned to the service account are reachable.
3. Create a key and download the private key. Redstor asks you to sign in to the RedApp again, then offers the private and public key for download. Download the private key, the .jwk file, while the dialog is open. Redstor does not say whether you can download it a second time, so keep the file safe. If you lose it, create a new key for the service account.
4. Copy the Client ID. It appears on the service account in the Service accounts list once the key is created.
5. Enter the details in StackJack. Open Connectors, choose Redstor, paste the Client ID, then open the .jwk file in a text editor and paste all of it, from the opening brace to the closing brace, into the private key box. StackJack checks the key as you save and names the value that is missing if it is not the private key. StackJack asks for the key on every save, so keep the file to hand if you edit the connection later.
6. Run a Test Connection. A failure usually means the Client ID belongs to a different service account, the public key was pasted instead of the private one, the service account was deleted, or the partner is not on the new pricing plan.

StackJack builds its sign-in request from Redstor's published guide. If Redstor's sign-in service ever refuses part of it, the connection test names the error Redstor gave and says it is not your key. Tell StackJack support what the message said so the connector can be corrected. A refusal of that kind is never counted against your connection, so it does not switch the connection off.

What to know before your AI uses this connector

One service account covers your whole partner company

Almost every read takes a company id. Your AI starts by asking Redstor for your root company, which is your own partner company, and then asks fleet-wide questions about it or about any customer under it. Several reads have a "customers" form that answers for every customer under a company at once, which is how "which customers had failures last night" is a single question rather than one per customer.

A customer you cannot see is usually not assigned

A service account reaches only the customers it was assigned. If a customer is missing from an answer, or a request for it comes back empty, refused or "not found", check the assignment in the RedApp under RedAPI and Service accounts. Redstor does not say which of those three it answers, so any of them can mean the same thing.

Statuses are numbers

Backup statuses come back as numbers: 0 failed, 1 completed successfully, 2 completed with warnings, 3 completed with errors. Redstor documents those meanings for the backup history only. Restore statuses are numbers too, and the same scale is likely but not confirmed by Redstor. Your AI is told this, but it helps to know when you read a raw answer.

Empty answers are normal

Redstor answers many reads with an empty body when there is nothing to return. StackJack passes that through as an empty result rather than treating it as a failure, so an empty list means nothing matched.

Changes are labelled, and some spend money

Every change is marked so your AI assistant asks first. Some are worth reading twice:

• Adding a subscription without the trial flag starts a billable product for the customer, converting a trial makes it a paid subscription, and removing a subscription changes what the customer is billed for. Redstor documents no way to undo any of them. StackJack makes the trial flag a required choice rather than a default, so a request cannot start a paid product by omission.
• Disabling a company is a real outage for that customer, and Redstor does not document exactly what a disabled company stops.
• Deleting a company or removing a subscription has outcomes Redstor does not document for the customer's backup data.
• Moving a customer to another partner may leave your service account without access to it afterwards. Redstor does not say.
• Creating a company with an admin contact may email that person an invitation. Redstor does not document whether it does, so give a contact only when you intend them to be invited.

What the RedAPI does not cover

Redstor's marketing mentions creating users, scheduling backups and starting recoveries through the API, but none of those is in the published RedAPI, so StackJack has no tool for them. The user list is read-only. Plans, policies and alerting are not exposed either.

If you already use Backup Radar

Backup Radar has its own Redstor integration and StackJack can already read Backup Radar. This connector adds what Backup Radar does not carry: the error messages behind each failure, restore status, storage, consumption, and the company and subscription lifecycle.

Plans and limits

Every read is available on the Free tier. Every change needs Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Redstor tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Redstor publishes no request limit, only a fair-use policy, so StackJack paces itself conservatively and waits when Redstor asks it to. A wide sweep across many customers takes longer rather than failing. Pacing smooths a burst; it does not guarantee that every call arrives. Ask for fewer rows per page or narrow to one company if throttling persists. Lists are read a page at a time, up to 100 rows a page, and your AI follows Redstor's continuation token until the list ends. See Retrying a failed or timed-out write.

Several Redstor accounts

One service account covers one Redstor partner. If you hold more than one Redstor partner account, add one connection for each from the connector's card, name each clearly, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single partner. See Several connections of one connector.

Redstor is changing its sign-in

Redstor has said it plans to unify RedAPI authentication across the CyberSentriq product suite, which Redstor now belongs to, and that customers will be given notice. If the connection test starts failing after a Redstor change, the test names the error Redstor gave, and StackJack will update the connector. The Redstor name and the product stay as they are.

Troubleshooting

"StackJack cannot use the Client ID or private key saved for Redstor": what is stored is not a usable private key, or the Client ID is empty. Open the connector and enter both again. The key must be the private one: a private key file carries values named d, p, q, dp, dq and qi, and the public file does not. If you no longer have the file, create a new key for the service account in the RedApp and download it when the dialog offers it.

"Redstor rejected the Client ID and private key saved here": most often the Client ID is from a different service account than the key, or the service account or its key was deleted in the RedApp. Confirm the account still exists under RedAPI and Service accounts, and if in doubt create a new key and paste both again.

"Redstor accepted the service account but will not let it do this": usually customer assignment. Open the RedApp, then RedAPI, then Service accounts, and check the customer is ticked, or tick Auto-assign all future customers.

"Redstor has no record with that identifier for this service account": the id may be wrong, or the customer may be outside the service account's assignment, which Redstor can report as missing. Ask your AI to list the parent collection first and use an id that came back from it.

"Redstor says this conflicts with the current state of the account": nothing is wrong with the credentials. Redstor reports a conflict when a subscription is added and when one is removed, and does not say why, so StackJack cannot tell which part of the account's state clashed. Read the customer's subscriptions to see what exists.

"Redstor rejected the request as invalid": check the values: company, account and subscription ids are GUIDs, product and edition ids are whole numbers, dates are yyyy-MM-dd, and a page is 1 to 100 rows. If Redstor gave no explanation at all and every call fails this way, its API version may have changed, and StackJack support should be told.

"Redstor is throttling requests": Redstor's fair-use policy has no published numbers. Ask for fewer rows per page, narrow the read to one company or product, or try again in a minute.

"Something answered at Redstor's address, but it was not Redstor": a sign-in page, firewall or proxy replied instead of the RedAPI. Check that outbound HTTPS to Redstor is allowed from wherever StackJack runs.

Everything returns an empty result: the service account may not be assigned any customers yet. In the RedApp, open RedAPI, then Service accounts, and assign the customers it should reach.

Redstor tools

redstor_ · 32 tools · Free 25 · Pro 7

Products

Companies

Consumption

Backup status

Restore status

Storage

Subscriptions

Users