EUDAMED pull pagination: page zero, correlation and access-limited results
The acquired pull example starts at page number zero and treats pageSize as the requested maximum response entities. Its example is an authenticated actor exchange, not an unrestricted complete public registry export. Reconcile pages and response identities within the actual permission scope.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Sourced criteria · EU · EUDAMED
What changes the service scope?
Decision or task
What the source describes
What to prepare
pull / HTML li [11]
messageID: A unique identifier, issued by the requester [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [13]
correlationID: An identifier that will correlate the request to the response or to the acknowledgements, issued by the requester [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [31]
pageSize: The required maximum number of entities on a specific response page [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [55]
correlationID: The same as correlationID from the request message [5]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Dated technical/help evidence, not a complete legal duty set or live EUDAMED response. Current target-environment release, business rules, permissions and actual buyer records remain unresolved. Blank dictionary flags are unknown; occurrence and update notes keep their stated conditions. No credentials, registration deadline or completed production exchange is inferred.
Prepare the EUDAMED pull pagination work package
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Define the permitted query
Identify the actor, service, filters and authorization scope before specifying data completeness.
Useful evidence: A query/permission specification with expected inclusions and exclusions.
Reconcile pages and correlations
Start from the documented page zero and retain each page’s request/response correlation; follow the actual service’s paging contract.
Useful evidence: A paginated exchange log and entity reconciliation ledger.
Document limitations and failures
Record missing/failed pages, retries and changing source versions instead of describing partial results as a full registry.
Useful evidence: A completeness report scoped to the actual actor/query and source version.
Work packages and dependencies
Conditional: EUDAMED pull pagination: page zero, correlation and access-limited results — Review the actual current records and target-environment requirements; complete the specific mapping/onboarding or maintenance task with source/version and acceptance evidence.
Questions for providers
How will you resolve the specific field/identity or state dependencies shown here for our actual records?
Which current environment release, permissions and business rules support the proposed operation?
What mapping, unresolved-error and acceptance evidence will you hand over, and who owns each correction?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
