Changelog

October 19, 2026

• Fix: updated_since on providers, provider groups, enrollments and group enrollments now returns a record when anything nested in it changes. Before this fix, editing a line of business, a location participation, a requirement, a follow-up, an assignee, a provider or group identifier, a group address or a group membership did not count as a change, so incremental syncs missed those edits.
• A record also counts as changed when a name or number shown inside it changes on the related record, such as a provider's name or NPI, a group's name, NPI or TIN, a location's address, a payer's name or an assignee's name.
• The updatedAt field on those four resources now reflects the latest of these changes, so it can move without the top-level fields changing.

July 22, 2026

• Initial release of the read-only public API.
• Endpoints: providers, provider groups, enrollments, group enrollments, expirables and document metadata, each with list and, where applicable, detail routes.
• Organization API keys with five scopes, an optional expiry, and immediate revocation.
• Keyset pagination on every list endpoint, with updated_since incremental sync.
• Per key daily request and error counts in the console.

These changes can happen within version 1 without notice, so write your client to tolerate them:

• New fields added to a response object.
• New values added to an existing enumerated field, such as an enrollment status.
• New optional query parameters.
• Rewording of the message text inside an error envelope.

These will not happen within version 1:

• Removing or renaming a field.
• Changing the type of an existing field.
• Changing the meaning of an existing error code.
• Removing an endpoint.

Parse responses tolerantly: ignore unknown fields rather than failing on them, and treat an unrecognized enumerated value as a passthrough string instead of an error.