Features
SP-API Integration
Connect your Amazon seller account with BYOK credentials for live data: customer feedback, reimbursements, keyword intelligence and review requests.
SP-API Integration
Rufusly supports Bring Your Own Keys (BYOK) SP-API connections. You create a private SP-API application in Seller Central, authorise it, and paste the credentials into Rufusly Settings. No Amazon developer approval needed.
Why BYOK?
BYOK lets you connect your own private Amazon application immediately, with no waiting and no dependency on third-party approval. You stay in control of your own credentials from day one.
Setup guide
Step 1: Create a private app in Seller Central
- Go to Seller Central → Apps and Services → Develop Apps
- Click Add new app client
- Name it anything (e.g. "Rufusly Private")
- Set the IAM ARN field. You can use
arn:aws:iam::123456789012:rootas a placeholder - Save and note the LWA Client ID and LWA Client Secret
Step 2: Self-authorise the app
- In the app page, click Authorize → Authorize app
- Follow the OAuth flow. You are authorising your own app on your own account
- Copy the Refresh Token at the end of the flow
Step 3: Assign the required roles
When creating or editing your app, check all of these roles:
| Role | Required for |
|---|---|
| Selling Partner Insights | Listing data, customer feedback |
| Listings | Read and update listing content, publish |
| FBA Inventory | Inventory status |
| Finances | Finance summary, reimbursements |
| Orders | Review Booster (order lookup) |
| Buyer Solicitation | Sending review requests |
| Brand Analytics | Keyword intelligence, customer voice |
Step 4: Add credentials to Rufusly
- Go to Settings → Connections
- Under Amazon SP-API (Private App), enter:
- LWA Client ID - LWA Client Secret - Refresh Token - Your marketplace
- Click Save connection
Rufusly validates the credentials immediately by exchanging the refresh token for an access token.
What SP-API switches on
Once connected, these features become active:
| Feature | Where |
|---|---|
| Auto-enrich listing rewrites with customer voice | Listing Studio (automatic) |
| Auto-enrich listing rewrites with keyword data | Listing Studio (automatic) |
| Publish to Amazon button | Listing Studio Step 3 |
| Review Booster | Settings → Connections |
| Customer Voice Report | MCP tool + Prompts tab |
| FBA Reimbursement Finder | MCP tool + Prompts tab |
| Keyword Intelligence Report | MCP tool + Prompts tab |
| Review Booster (MCP) | MCP tool + Prompts tab |
Auto-enrichment in Listing Studio
When you rewrite a listing with an ASIN provided and SP-API connected, Rufusly automatically:
- Fetches customer feedback topics for the ASIN (positive, negative, return reasons)
- Checks the report cache for existing Brand Analytics keyword data
These are injected into the Claude prompt as additional context: the AI amplifies praised features and addresses complaints proactively in the bullets. This is non-blocking: if the fetch fails, the rewrite continues without it.
Security
LWA credentials (Client ID, Secret, Refresh Token) are encrypted at rest using AES-256 before storage. They are decrypted server-side only when making SP-API calls. They are never returned to the client.