Publishing from Marked
Connect with File → Publish → Connect Account, then publish the document you are previewing and update it on later shares.
Connect your account
Marked can log in to Marked Share for you. There is no pasting of tokens into the app: credentials are minted on the website and sent straight back to Marked over a deep link.
-
In Marked, choose File → Publish → Connect Account. Your browser opens the
connect page on
share.markedapp.com. - Sign up or log in if you are not already signed in, then click Connect Marked on the website.
-
The site hands an API token and device key back to Marked automatically via the
x-marked-3://loginURL. You should not need to copy anything.
The first time this runs, macOS may ask whether share.markedapp.com can open an
x-marked-3 URL. Allow it so the handoff can finish. If the browser blocks the launch,
the connect page still shows the credentials once and an Open Marked button as a
fallback.
That deep link is for Marked 3. Marked 2 registers x-marked:// and cannot store these
credentials, so Share only returns x-marked-3://login.
You can also start from Connect an app in Settings without opening Marked first. That still mints the same API token and device key pair; without Marked waiting for the deep link, copy them into Marked or another app. Credentials are shown a single time and are not recoverable — connect again for a new pair, then revoke the old token under Your tokens in Settings.
What publishing sends
Marked packages the document you are previewing as a TextPack, a zipped TextBundle containing the Markdown and any local images it references, and uploads that in one request. Images are stored with the document and the Markdown image paths are rewritten to hosted URLs, so a shared document is never pointing at files on your Mac.
The response includes the share URL, so the app can show you a link to copy or open. Documents created through the API are private unless the request asks for unlisted or public, so you decide when something becomes readable.
If the document carries Marked highlights in a highlights.json file, those come
across too and become your own highlight set on the published copy. See
Highlights and reviews.
An info.json in the archive can also set the published
reading style,
under the com.markedapp.share namespace or as a bare readingStyle
key. Downloads carry the same file, so the typography survives a trip out to Marked and back.
Publishing again after edits
The first publish creates a document; later publishes update that same document, so the share link you already sent out keeps working and readers get a live-update notice.
Updates are guarded against clobbering. Each version has a content hash, and an update must say which version it is replacing. If the copy on the server is newer — you edited it in the browser, or published from another Mac — the update is refused and the app can tell you which device got there first before you decide to overwrite.
| Situation | What happens |
|---|---|
| First publish | A new document is created and its id, hash, and share URL are returned. |
| Publish after local edits | The existing document is replaced, with a new version snapshot in its history. |
| Server copy is newer | The update is rejected as a conflict, naming the device that made the newer change. |
| Token revoked | Requests stop being authorized; connect again to get a fresh pair. |
Pulling reader feedback back into Marked
Reviews collected on the web can travel back to your Mac. Every highlight set has a TextBundle
download that includes a highlights.json in Marked's format, so you can open a
reviewed draft locally with the highlights and notes intact. The
highlights documentation covers the whole loop, and the
API reference lists the endpoints an app or script can use to
fetch reviews directly.
Managing access
Settings lists every token on your account with its name, creation date, and last use. Revoke takes effect immediately and is the right move for a machine you no longer use or a credential you think leaked. Revoking one token does not affect the others, and it never touches your documents.