Repository navigation
docs: name the API resource recipient links (?link=) - #69
Merged
Merged
Conversation
…ecipient_links, ?link=)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
SimplePDF renamed the public prefill resource to recipient links (simple-pdf #603 / #605), now in production (release
6f020890, 2026-11-14): the API serves/documents/{document_id}/recipient_linksand/documents/{document_id}/recipient_links/{recipient_link_id}(checked against the production OpenAPI spec),/prefillsno longer exists, and a document link carries?link=<id>instead of?prefill=<id>. This repository's docs, the React example and the build-with-simplepdf agent skill still send integrators and agents to the old names.Changes
POST /documents/{document_id}/recipient_links(what a recipient link is), the delete path, and the storage and server-side resource listscopilot/, private) and its README pass a document link with?link=instead of?prefill=?link=in the document URLs they pass througheditor_version6f020890): one description changes (a document with more form fields than a document can is a load failure); the generated types are unchanged. main would fail the same check today@simplepdf/embedREADME andmount.tsexample name both ids (documents/<document_id>?link=<recipient_link_id>)@simplepdf/embed, so its npm README stops showing?prefill=Notes
@simplepdf/react-embed-pdfand@simplepdf/web-embed-pdfpin@simplepdf/embedexactly, so the embed patch also publishes react 1.14.1 and web 1.10.1 ("Updated dependencies"), with no change to built code. An empty changeset instead would publish nothing and leave the npm README showing?prefill=until the next release.