1. Request a code
Send only the customer-visible name of your application. There is no client registration or developer secret.
POST /oauth/device/authorize client_name=Your Application
Add Cascacore without fuss or muss.
Add a “Connect with Cascacore” button. Your application requests a short-lived code, the customer signs in or creates an account, pays for their own credits, and approves. Your application receives its customer-owned bearer credential automatically.
2. Customer approves
Open the returned verification URL. Cascacore handles account creation, email verification, Stripe payment, optional auto-refill, and explicit consent.
https://core.casca.me/connect Code: ABCDE-23456
3. Use the bearer token
Poll at the returned interval and securely store the one-time credential. It belongs to that customer and is independently revocable.
Authorization: Bearer cc_live_…
One integration, richer screens
Build the experience—not a provider adapter.
The same customer-owned connection can enrich every supported media type with a consistent response shape.
Complete detail pages
Render synopsis, runtime, ratings, cast and crew, collections, artwork, trailers, availability, seasons, episodes, and playback markers.
Music and spoken word
Connect artists, albums, tracks, contributors, durations, recording IDs, cover art, audiobook authors, narrators, and series order.
Edition-aware libraries
Show authors, descriptions, publishers, publication dates, languages, page counts, editions, Cascacore identity, and cover art.
Discovery and games
Use normalized genres, platforms, studios, age ratings, artwork, trailers, popularity, collections, and curated lists.
Who pays?
The customer does. Developers never collect Cascacore payments, never receive access to billing settings, and never share one master credential across users. Test through the same ordinary customer flow.