Link straight to documents and searches (QuickLinks)

By the end of this page your other systems can link into Content Central — this customer's folder, this PO's document, this search already run — with nothing but a URL, and you'll know the two parameter facts that make or break these links.

All URLs below hang off your Content Central address (shown here as https://docs.example.com/ContentCentral). Permissions always apply — a link opens only what its follower is allowed to see — and a signed-out user gets the login page first, then lands on the link's target.

Before any URL-building: the Search page can hand out links by itself. Run a search and use its share/copy-link control — the copied URL reproduces the whole search (criteria, catalogs, view) for anyone who follows it. For "here's the search, see for yourself" emails, that's the answer; the patterns below are for systems that build links.

https://docs.example.com/ContentCentral/FolderBrowser/FolderBrowser.aspx?id=<document GUID>

The document's GUID is its stable address (visible, among other places, atop its Version History). Store it at capture time — an XML capture job or the API can carry it back to the linking system — and your ERP's "view document" button is this URL.

.../FolderBrowser/FolderBrowser.aspx?c=Accounts Payable&d1=Bowman Fabrication&d2=PO 8888

• c — the catalog name (URL-encode spaces).
• d1, d2, d3… — one parameter per folder level, matched by name, case-insensitively.

Names, not IDs — which makes these links readable and buildable from data the other system already has (vendor name → vendor folder), at the price that renaming a folder breaks its links.

.../Search.aspx?ft=Bowman&execute=1
.../Search.aspx?c=Accounts Payable&dt=Purchase Order&f1=PO&v1=8888&execute=1

The second example is the everyday integration: field + value + execute=1 turns any system's record into a "show me the documents" button.

.../Capture.aspx?ct=electronic&cm=post&c=Accounts Payable&execute=1

• ct — capture type: electronic, directscan, directscanzonal, qcard, qcardpacket, form
• cm — coding method: pre, post, versatile, ocronly
• dq — queue destination for versatile: personal or shared
• fpc — fixed page count; eod=1 — include the end-of-document QCard
• c — catalog name; execute=1 — go immediately

The intranet's "scan an invoice" link opens the right capture page with the right choices already made.

Success check: build the field-search URL for a value you know exists, open it in a private window — login page, sign in, results already on screen. That round trip is every integration's demo.