Changelog
2026-05-28
Section titled “2026-05-28”- Non-breaking: Added nullable
user.nameanduser.emailAddressfields toGET /v1/whoami. - Docs-only: Added account identity response examples that show the display name and primary email address.
Phase 4A Website Library
Section titled “Phase 4A Website Library”- Non-breaking: Added Website Library domain, link, linked-page, and linked-ad endpoints to the public
/v1API. - Non-breaking: Added
website_domainsandwebsite_linkscollection item types. - Non-breaking: Added hosted MCP Website Library tools. Website Library tools are no-credit in this phase.
Phase 2 docs package
Section titled “Phase 2 docs package”- Created a standalone
@afterlib/public-api-docspackage for AfterLib API documentation. - Added editorial guides for authentication, credits, ads, pages, collections, pagination, errors, and request logs.
- Added docs checks for links, examples, and public-copy safety.
Change types
Section titled “Change types”AfterLib API changes should be classified before the docs are published:
- Breaking: removes an endpoint, removes a response field, changes a field type, adds a required request field, changes API key access behavior, changes credit charging behavior, or changes an error code that clients can handle.
- Non-breaking: adds an optional request field, adds a response field, adds a new endpoint, adds an example, or clarifies wording without changing behavior.
- Deprecation: keeps behavior working while announcing a future removal or replacement.
- Docs-only: changes examples, navigation, or explanations without changing API behavior.
Breaking changes need a migration note, a changelog entry, and product approval before public launch. Deprecations should include the old behavior, the replacement, and the removal date once that date is known.
Entry format
Section titled “Entry format”Use this format for future entries:
## YYYY-MM-DD
- **Non-breaking:** Added ...- **Breaking:** Changed ...- **Deprecation:** Deprecated ...- **Docs-only:** Clarified ...