Autype
Back to blog

Updated November 22, 2026

Bibliographies Without Manual Work: Citations with CSL-JSON, Six Styles, and an Automatic Reference List

Hand-typed parenthetical citations break at the first style change. How citation keys from CSL-JSON cover six styles, keep the reference list derived from the text, and pass a six-point check before sending.

Document AutomationTutorials#document automation#citations#bibliography#csl-json#markdown

On 13 November 2026 the President of the European Court of Human Rights excluded a Romanian lawyer from representing applicants before the Court for two years. The Chamber handling her case had found numerous errors in her observations on the Court's case-law: citations to non-existent cases, invented paragraph numbers in genuine judgments and decisions, and existing case-law that was irrelevant to her arguments or contradicted them outright. She acknowledged having used AI tools to draft the submissions, and the Chamber treated the problems as a pattern rather than isolated citation mistakes.

The case is not only a story about AI. It shows what a citation in a document has to do: it is a claim that a reader or reviewer can look up in a source. That property disappears the moment citations are just text – typed by hand, pasted out of a chat window, or lifted from an older file. The document still looks tidy afterwards. It just is not true any more.

This article describes a setup where citations and the reference list come from the same data: entries as structured records, references as keys in the text, formatting as a setting. The examples use Autype, where citations run through @[key] and the bibliography is generated; the approach transfers to any CSL-capable pipeline.

Three ways citations go quietly wrong

SymptomCauseWhat the document ends up saying
Parenthetical citation typed by handFormat rebuilt manuallyMissing page number, wrong year, breaks at the next template change
Citation copied from another fileEntry pasted without its metadataSame source appears twice, spelled two ways, in the reference list
Reference list maintained by handEntries added or removed manuallyThe list names sources nobody cites, and cited sources are missing from it

The common thread: text and bibliography are two separate assertions. Maintain them separately and you maintain two truths. After the third revision, neither matches the other – and nobody notices, because each one looks plausible on its own.

What goes into a CSL entry

The Citation Style Language (CSL) is an XML-based format that describes how citations and bibliographies are formatted: open, with automatic localization and thousands of freely available styles under a CC-BY-SA licence. How those formats are structured is set out in the CSL specification; CSL-JSON carries the same information as JSON – machine-readable, diffable, versionable.

In Autype the library belongs to the document. The Citations panel holds the sources: looked up by DOI or ISBN, entered manually, or imported from CSL-JSON (.json) and BibTeX (.bib), either as a file or as pasted text. ID and type are required; title, author, year, and publisher make the formatting correct. Under "More Options" sit container title, volume, issue, pages, ISBN, ISSN, edition, editor, place of publication, DOI, and URL. Seven source types are available: book, journal article, book chapter, webpage, thesis, report, and conference paper.

One entry in CSL-JSON:

[
  {
    "id": "smith2023",
    "type": "article-journal",
    "title": "Template Drift in Regulated Documents",
    "author": [{ "family": "Smith", "given": "John" }],
    "container-title": "Journal of Document Engineering",
    "volume": "12",
    "issue": "3",
    "page": "42-58",
    "issued": { "date-parts": [[2023]] },
    "DOI": "10.1000/xyz123"
  }
]

The ID is the contract between text and library. Everything else is metadata that gets maintained once – not once per citation.

Six styles, one source

Citation formatting is a document setting, not text work. Six presets are available in Autype, selected in the Styles panel under the document defaults.

PresetIn-text formCommon inValue in defaults.citationStyle
APA 7 (default)author and yearsocial sciences, psychologyapa7
Harvardauthor and yearUK universitiesharvard
IEEEnumericengineering, computer scienceieee
Chicagonote or author and yearhumanitieschicago
MLAauthor and pagelanguage and literaturemla
Vancouvernumericbiomedical sciencesvancouver

Exact punctuation belongs to the style, not to the author. That is the real gain: switching styles is a change in one place.

A fictional example: a report for a funding body carries 17 sources in APA 7. Three days before the deadline, the review office asks for IEEE. With hand-typed citations that means rewriting dozens of parentheses, re-sorting the list, and wondering whether the page numbers survived. With keys in the text, the prose stays untouched and only the rendering changes. What remains is editorial work: checking that the cited statements actually support the argument.

Locators and author control

A citation without a location is useless in many fields. Autype accepts pages, chapters, sections, and volumes directly on the key:

These findings match earlier measurements @[smith2023, pp. 42-45].
Smith @[-smith2023, p. 42] describes the effect as stable.
@[jones2022!] introduced the method @[jones2022, sec. 2.1].
SyntaxEffect
@[smith2023]plain citation, no locator
@[smith2023, p. 42]single page
@[smith2023, vol. 2, pp. 42-45]several locators combined
@[smith2023, p. 42, note="emphasis added"]custom note on the citation
@[-smith2023, p. 42]author suppressed because the name is already in the sentence
@[smith2023!]author only, narrative form

The supported locator prefixes are p., pp., ch., sec., and vol.. Citations also work inside bold and italic text, so a sentence like Smith @[-smith2023, p. 42] stays both visually and formally correct.

The list contains only what is cited

## References

::bibliography{title="References"}

Short aliases are ::bib and ::references. One property matters more than the syntax: the list includes only sources that are actually referenced in the text with @[key]. An entry that sits in the library but is never cited does not appear. The bibliography is therefore derived from the content, not a second list that somebody has to maintain in parallel. The citations and bibliography documentation lists every attribute and locator form.

The same principle already carries cross-references and numbering: whatever follows from the content should be produced at render time, not patched in afterwards.

When to import, when to type

SituationRecommended route
One to three sources, short notemanual entry, DOI lookup for the metadata
Existing library in Zotero, Mendeley, or EndNoteexport as CSL-JSON or BibTeX and import in the panel
Many sources from PDFs and web pagesDOI or ISBN lookup, the rest manual
Same sources across several documentskeep one central CSL-JSON file under version control and re-import it

The import shows a preview of every entry it found. Individual citations can be deselected, and existing entries are skipped by default or replaced with the imported version. Duplicate IDs inside the import file surface as errors; entries already in the document surface as warnings. Taking those two messages seriously prevents most duplicate-list problems before they exist.

Where the automation stops

A cleanly formatted reference list does not prove that the source exists. In the case above the details were formally citable – the decisions and paragraph numbers simply were not there. Checking therefore means resolving the DOI, searching for the title in the original, and reading the cited statement in context. No tool removes that work, and none should imply it does.

Two practical limits are worth stating. First, one ID means one work: two versions of the same paper belong in one entry with consistent fields, not in two entries with conflicting years. Second, the style applies to the document. One section in IEEE and the next in APA is not a formatting question; it is a sign that two texts were stitched together from different sources.

Checklist before you send

  1. Every statement that points to a source carries a key – no hand-typed parenthetical citations.
  2. Every key used exists in the library; render errors are fixed, not ignored.
  3. Every entry has type, title, author, and year; DOI or URL set wherever one exists.
  4. Page references sit as locators on the citation, not as prose next to it.
  5. The style matches the requirement, and the rendered list was read once end to end: order, name forms, titles.
  6. Spot check: look up three sources in five minutes – open the DOI, compare the title, open the cited passage.

A citation is a promise that somebody can check. Structured entries, keys in the text, and a generated bibliography keep that promise through the fifth revision – and make it visible when the promise no longer holds.

Sources (retrieved 22 November 2026)

Autype documentation, "Citations & Bibliography": https://docs.autype.com/markup-reference/citations

Autype documentation, "Citations Panel": https://docs.autype.com/getting-started/editor/sidebar-citations

Autype documentation, "Citations Schema": https://docs.autype.com/automation/llm-resources/citations-schema

Citation Style Language, CSL 1.0.2 Specification: https://docs.citationstyles.org/en/stable/specification.html

European Court of Human Rights, press release of 18 November 2026: https://www.echr.coe.int/w/romanian-lawyer-barred-for-two-years-from-representing-applicants-before-the-court-over-unverified-ai-generated-citations

Ready to automate your documents?

Start creating business documents with Autype. No credit card required.