PIXELCORE
Developers

One link,
predictable URLs.

PixelCore exposes a REST API under /api/v1/, but most integrations only need its URL patterns. Every share is a small set of clean, guessable paths — direct bytes, a view page, a gallery, an embed and oEmbed discovery — so dropping a file into a forum, a wiki or an iframe just works.

Reference

URL patterns

The integration surface. {code} is the short share code for a file or album.

/p/{code}
Direct file URL The raw bytes of the file. This is what the browser extension copies, and what embeds and hotlinks point at.
/v/{code}
Share / view page The full share page for a single item — preview, metadata and download.
/s/{code}
Album / gallery A gallery view for a collection. A single-item code here redirects on to its /v page.
/e/{code}
Chrome-free embed A minimal, frameless render of the item — built to drop into an iframe.
/oembed?url=…
oEmbed discovery Returns oEmbed metadata so forums, Notion and other tools can unfurl a PixelCore link automatically.
Embedding & forums

Drop a file anywhere

Most platforms can unfurl or hotlink a PixelCore link without any custom work.

oEmbed for rich unfurls

Tools that speak oEmbed — forums, Notion and similar — can discover a card via /oembed?url=… and render a proper preview instead of a bare link.

Forum pattern matching

Forum software like XenForo can match the /p/ and /s/ patterns to inline images and galleries directly in a post — paste the link and it embeds.

Frameless iframes

Need a clean embed with no chrome? Point an <iframe> at /e/{code} for a minimal render that sits neatly inside your own page.

Getting files in

Uploads happen through the web app — drag and drop a file to get a link — or through the companion browser extension, which uploads and hands you a direct link without opening the site.