Rawback Core SDK
Add Rawback authentication and typed photo-library operations to an approved Node.js agent, service, or application with the same core package used by Rawback clients.
Node.js 26 or newer, or BunES modulesserver-side only
Upgrading?Review the version and metadata on npm
Approval required
The npm package is publicly downloadable but remains UNLICENSED. Third-party use and production deployment require written Rawback approval. The guide documents the integration contract so your team can evaluate the fit.
Quick start
Each operation is typed from Rawback’s published GraphQL documents, so the variables and the result are checked at compile time.
const rawback = await createRawbackSdk({ identity })Name your integration with a stable source, version and user agent. By default the SDK reads ~/.rawback/credentials.json.
await loginSdk.auth.createDeviceSession()From an SDK created with credentials: null, open the approval link for the person signing in and poll no faster than the interval Rawback returns. Their password never reaches your code.
await rawback.services.photos.library({ pagination })What it does
Work with photos, albums, articles, dreams, shares, usage, pricing, and account data through generated TypeScript contracts.
Use browser-approved device sessions, persisted credentials, and automatic token refresh without rebuilding the session layer.
Bring the SDK into trusted Node.js services, photo agents, desktop clients, and command-line tools while keeping the interface yours.
Integration
import { createRawbackSdk } from '@rawback/sdk'
const rawback = await createRawbackSdk({
identity: {
source: 'studio-workflow',
version: '1.0.0',
userAgent: 'studio-workflow/1.0.0',
},
})
const library = await rawback.services.photos.library({
pagination: { page: 1, pageSize: 40 },
})Every service returns { data, error }. Keep pagination explicit and bounded, and inspect the error first.
Identify every client, keep credentials outside the browser, and coordinate production access with Rawback before shipping.