Entur · Schema
ConsentCrmResponse
A condensed view of consent information
CompanyPublic TransportJourney PlanningMobilityOpen DataNorwayTransitGraphQL
Properties
| Name | Type | Description |
|---|---|---|
| consentBaseVersion | integer | The consent base version associated with the consent |
| consentCode | string | The consent code of the base consent associated with the consent |
| consentId | integer | The id of the Consent that has been consented |
| consentOrganisationId | integer | The organisation that owns the Consent. Typically an 'Operatør' |
| countryCode | string | The telephone number country code |
| createdByOrgId | integer | The organisation through which the consent was given |
| customerNumber | integer | Customer number, a unique identifier for the customer. |
| customerRef | string | Customer ref, a unique identifier for the customer within an organisation |
| string | The customer's email | |
| fromStopPlace | string | The stop place where the customer’s journey started, in NeTEx format. |
| givenConsentId | integer | Given consent id. |
| lineRef | string | Reference to the customers journey line, in NeTEx format |
| originalDatedServiceJourneyId | string | Unique Id for a specific Service Journey, in NeTEx format with ENT as operator |
| telephoneNumber | string | The customer's telephone number |
| toStopPlace | string | The stop place where the customer’s journey ended, in NeTEx format. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/entur/main/json-schema/entur-consent-crm-response-schema.json",
"title": "ConsentCrmResponse",
"description": "A condensed view of consent information",
"x-generated": "2026-10-09",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/entur-consents-openapi.yml#/components/schemas/ConsentCrmResponse",
"required": [
"consentBaseVersion",
"consentCode",
"consentId",
"consentOrganisationId",
"createdByOrgId",
"customerNumber",
"customerRef",
"givenConsentId"
],
"type": "object",
"properties": {
"consentBaseVersion": {
"type": "integer",
"description": "The consent base version associated with the consent",
"format": "int32"
},
"consentCode": {
"type": "string",
"description": "The consent code of the base consent associated with the consent"
},
"consentId": {
"type": "integer",
"description": "The id of the Consent that has been consented",
"format": "int64"
},
"consentOrganisationId": {
"type": "integer",
"description": "The organisation that owns the Consent. Typically an 'Operatør'",
"format": "int64"
},
"countryCode": {
"type": "string",
"description": "The telephone number country code"
},
"createdByOrgId": {
"type": "integer",
"description": "The organisation through which the consent was given",
"format": "int64"
},
"customerNumber": {
"type": "integer",
"description": "Customer number, a unique identifier for the customer.",
"format": "int64"
},
"customerRef": {
"type": "string",
"description": "Customer ref, a unique identifier for the customer within an organisation"
},
"email": {
"type": "string",
"description": "The customer's email"
},
"fromStopPlace": {
"type": "string",
"description": "The stop place where the customer’s journey started, in NeTEx format."
},
"givenConsentId": {
"type": "integer",
"description": "Given consent id.",
"format": "int64"
},
"lineRef": {
"type": "string",
"description": "Reference to the customers journey line, in NeTEx format"
},
"originalDatedServiceJourneyId": {
"type": "string",
"description": "Unique Id for a specific Service Journey, in NeTEx format with ENT as operator"
},
"telephoneNumber": {
"type": "string",
"description": "The customer's telephone number"
},
"toStopPlace": {
"type": "string",
"description": "The stop place where the customer’s journey ended, in NeTEx format."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/entur-consent-crm-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.