Trust score
How is this computed?Composite of 5 axes from our methodology (proof-based officialness, live verification, metadata completeness, license clarity, agent readiness).
- Officialnessweight 25%40/100
40/100 from 5 proof signals (domain / portal-backlink / GitHub-org / reciprocal / policy).
- Availabilityweight 25%100/100
Latest verification succeeded.
- Metadata completenessweight 20%90/100
9 of 10 recommended metadata fields populated.
- License clarityweight 15%50/100
License info not yet tracked for APIs (datasets only).
- Agent readinessweight 15%70/100
OpenAPI spec URL declared · Spec format known (openapi) · Homepage URL present · Topic tags assigned
Official Proof
Public Sector APIProof Evidence
official domain (parliament.uk)
Data schema (43 fields)
| Field | Type | Description |
|---|---|---|
| chapterNumber | integer (int32) | Chapter overview with the chapter number specified |
| startLetter | string | Index terms by start letter |
| skip | integer (int32) | The number of records to skip from the first, default is 0. |
| take | integer (int32) | The number of records to return, default is 20, maximum is 20. |
| indexTermId | integer (int32) | Index term by if |
| partNumber | integer (int32) | Part by part number |
| searchTerm | string | Index terms which contain search term. |
| reference | string | Section overview by reference. |
| sectionId | integer (int32) | Section by id. |
| step | integer (int32) | Number of sections to step over from given section. |
| numberErskineMayChapterOverview | integer (int32) | — |
| titleErskineMayChapterOverview | string | — |
| descriptionErskineMayChapterOverview | string | — |
| sectionsErskineMayChapterOverview | array<object> | — |
| contentErskineMayFootnote | string | — |
| idErskineMayIndexTerm | integer (int32) | — |
| termErskineMayIndexTerm | string | — |
| displayAsErskineMayIndexTerm | string | — |
| seeLinksErskineMayIndexTerm | array<object> | — |
| referencesErskineMayIndexTerm | array<object> | — |
| parentTermErskineMayIndexTerm | object | — |
| childTermsErskineMayIndexTerm | array<object> | — |
| seeValueErskineMayIndexTermSearchResult | string | — |
| totalResultsErskineMayIndexTermSearchResultErskineMaySearch | integer (int32) | — |
| searchResultsErskineMayIndexTermSearchResultErskineMaySearch | array<object> | — |
| searchTermsErskineMayIndexTermSearchResultErskineMaySearch | array<string> | — |
| suggestedSearchErskineMayIndexTermSearchResultErskineMaySearch | string | — |
| seeTypeErskineMayIndexTermSeeLink | string | — |
| paragraphReferenceErskineMayParagraphSearchResult | string | — |
| searchResultTextErskineMayParagraphSearchResult | string | — |
| sectionTitleErskineMayParagraphSearchResult | string | — |
| sectionTitleChainErskineMayParagraphSearchResult | string | — |
| chapterTitleErskineMayParagraphSearchResult | string | — |
| chaptersErskineMayPart | array<object> | — |
| titleChainErskineMaySectionDetail | string | — |
| subSectionsErskineMaySectionDetail | array<object> | — |
| parentSectionIdErskineMaySectionDetail | integer (int32) | — |
| parentSectionTitleErskineMaySectionDetail | string | — |
| partTitleErskineMaySectionDetail | string | — |
| contentHtmlErskineMaySectionDetail | string | — |
| isUpdatedErskineMaySectionDetail | boolean | — |
| updatedDateErskineMaySectionDetail | string (date-time) | — |
| footnotesErskineMaySectionDetail | array<object> | — |
Schema captured from openapi 1 day ago.
Verification Status
Using the API
Configuration
- Base URL
- https://erskinemay-api.parliament.uk
- Version
- v1
- Format
- openapi
- Endpoints
- 11
Try the API
/api/Chapter/{chapterNumber}Returns a single chapter overview by chapter number.
/api/IndexTerm/browseReturns a list of index terms by start letter.
/api/IndexTerm/{indexTermId}Returns an index term by id.
/api/PartReturns a list of all parts.
/api/Part/{partNumber}Returns a part by part number.
Requests are proxied through our servers. Only GET endpoints are testable.
Query examples
curl -s 'https://erskinemay-api.parliament.uk/swagger/v1/swagger.json' -H 'Accept: application/json'Machine-readable API description (use it to generate clients).
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.