Auth-Scraper - B2B Portal Session Automation
Auth-Scraper is a B2B Portal Session Automation API for explicitly authorized workflows. It demonstrates signed session credentials, CSRF-aware requests and isolated supplier-portal testing without storing third-party credentials.
Auth-Scraper - B2B Authenticated Portal Session API
B2B Authenticated Portal Session API for authorized Data Extraction workflows. Manage signed session state and CSRF-aware requests for approved supplier integrations without rebuilding the login boundary.
Search intent: B2B portal · authenticated scraping · session management · CSRF automation
Watch a session survive the login boundary.
This sandbox uses an isolated, fictional supplier portal. It demonstrates session cookies and CSRF-aware requests without contacting or storing credentials for any third-party system.
Copy the flow. Keep the authorization boundary.
import { AuthScraper } from "@foundry/auth-scraper";
const client = new AuthScraper({ apiKey: process.env.AUTH_SCRAPER_KEY });
const session = await client.sessions.create({
portal: "demo-supplier.local",
username: "admin",
password: "admin"
});
const prices = await client.sessions.getPriceList(session.id);
console.table(prices.rows);Scope-limited demo
The product demo only targets the fictional portal and rejects all other hosts and credentials.
Explicit authorization
Production workflows must be limited to portals that the customer is explicitly entitled to access.
Simple commercial unit
$49 per month includes 5 active portals for approved supplier integrations.
Use a product-scoped key outside RapidAPI.
Requires authorization review and portal-specific onboarding before activation. The entitlement includes 5 approved portal connections and is revoked when the associated subscription ends.
Confirm scope
Use the sales form to confirm authorization, scope and onboarding.
Generate one key
Open the authenticated API Access area and generate the product-scoped key once.
Call the endpoint
Send X-API-Key to POST /api/v1/auth-scraper/session; usage headers report the remaining allowance.
curl --request POST \ --url https://prodapi-gqe9kzue.manus.space/api/v1/auth-scraper/session \ --header 'X-API-Key: YOUR_DIRECT_KEY' \ --header 'Content-Type: application/json'
RapidAPI-ready endpoint contracts.
Every endpoint documents a testable request shape or an explicit public-source requirement, plus a response example, so a developer can inspect the contract before running it in RapidAPI.
curl --request POST \
--url https://YOUR_RAPIDAPI_HOST/api/v1/auth-scraper/sessions \
--header 'x-rapidapi-key: YOUR_KEY' \
--header 'x-rapidapi-host: YOUR_RAPIDAPI_HOST' \
--header 'Content-Type: application/json' \
--data '{"portal":"demo-supplier.local","username":"admin","password":"admin"}'{"status":"active","sessionId":"eyJ...","expiresInMinutes":60,"csrfToken":"csrf_..."}curl --request POST \
--url https://YOUR_RAPIDAPI_HOST/api/v1/auth-scraper/price-list \
--header 'x-rapidapi-key: YOUR_KEY' \
--header 'x-rapidapi-host: YOUR_RAPIDAPI_HOST' \
--header 'Content-Type: application/json' \
--data '{"sessionId":"SESSION_TOKEN_FROM_CREATE"}'{"portal":"demo-supplier.local","rows":[{"sku":"ALU-100","price":"€ 12.40"}],"refreshedCsrfToken":"csrf_..."}Commercial and integration questions.
Can I buy this outside RapidAPI?
Yes, after assisted approval. Requires authorization review and portal-specific onboarding before activation.
How are limits enforced?
Direct keys are scoped to this product and the 5 approved portal connections allowance. Responses include usage headers; exhausted allowances are rejected.
What data is retained?
Retention differs by workflow and is documented in the Privacy notice. Do not send secrets, credentials, regulated data or content you are not authorized to process.
What support is included?
Self-service support covers verified integration and billing issues. Enterprise response targets, uptime or recovery commitments apply only when written in an order form.