UK Data AtlasAPI

Get attribution text

Get the publisher and licence details for the data you've used, plus a plain-text block ready to paste under a map or into a report.

get
/attribution

Good to know

  • Name at least one dataset, measure, boundaryRelease or crosswalk. Each can be repeated.

Query parameters

  • datasetstring[]optional

    A dataset id from GET /datasets. Repeatable.

  • measurestring[]optional

    A measure id from GET /measures, or one of its aliases. Repeatable.

  • boundaryReleasestring[]optional

    A {geography}/{release} identity, such as localAuthority/2025-05-uk-bgc-v2. Repeatable.

  • crosswalkstring[]optional

    A crosswalk id from GET /crosswalks. Repeatable.

Returns

Envelope

The resources, the distinct licences that apply, and a ready-to-use plain-text attribution block.

  • apiVersionv1required
  • atlasReleasestringrequired

    The immutable /atlas-release releaseId for the artifacts that produced this response.

  • metaobjectrequired
    Show1 child field
    • nextCursorstring | nullrequired

      Opaque cursor for the next page, or null at the end.

When it goes wrong

  • 400A query parameter is malformed or its cursor is not valid for this result set.
  • 404No resource matches that identity.
  • 503The referenced build artifact has not been built yet.

Every error has the same shape. See Errors for how to handle them.

Technical notes

Show the precise behaviour

Collects the publisher, source and licence of every resource behind an answer, and returns a plain-text block suitable for a map corner, a report footer or a bulk-download README. Name at least one of dataset, measure, boundaryRelease or crosswalk; each may be repeated, and a resource named more than one way is listed once. A measure is attributed through the datasets its observations come from. A crosswalk is compiled by the Atlas rather than obtained, so it carries no licence of its own and the boundary releases at its endpoints are attributed instead, with the crosswalk listing them in derivedFrom. Licence names are reproduced exactly as the publisher states them and are not interpreted. One catalogue source already carries two licences across its date range, so which terms govern a combined work is the caller's judgement rather than this API's.