> ## Documentation Index > Fetch the complete documentation index at: https://docs.ctrl-hub.com/llms.txt > Use this file to discover all available pages before exploring further. # List permits > List all of the permits in an organisation. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v3/orgs/{org_id}/projects/permits openapi: 3.1.0 info: contact: email: support@ctrl-hub.com name: Ctrl Hub url: https://www.ctrl-hub.com description: > Ctrl Hub is the all-in-one platform for high-risk industries like utilities, construction, infrastructure, and renewables. We help teams manage everything from risk assessments and HAVS exposure to vehicle and equipment checks, with a guaranteed minimum of 200% ROI. license: name: MIT License url: https://opensource.org/licenses/MIT summary: An API for managing your compliance and risk posture termsOfService: https://www.ctrl-hub.com/terms-conditions title: Ctrl Hub version: 1.0.0 servers: - description: Production url: https://api.ctrl-hub.com - description: Staging url: https://api.ctrl-hub.dev - description: Development url: https://api.ctrl-hub.run security: [] tags: - description: | Audit events are the events that are logged by the system. name: Audit Events - description: | View the platform's health and availability. name: Status - description: > User-owned dashboards composed of cards on a fixed-slot bento layout. Cards come from a per-domain registry; the API stores their config as opaque JSON. name: Dashboards - description: | Manage appointments for work to be carried out with your customers name: Customer Appointments - description: | Manage interactions you have with your customers name: Customer Interactions - description: | Manage accounts for your customers name: Customer Accounts and Contacts - description: | Qualifications are the skills and knowledge that an organisation requires. name: Qualifications - description: | Workflows allow you to automate your processes. name: Workflows - description: | Manage documents name: Documents - description: | Manage documents name: Folders - description: | Manage documents name: Document Reviews - description: | Manage feature configurations for an organisation. name: Feature Configurations - description: | Equipment are the physical assets that an organisation manages. name: Equipment - description: | Manage your forms and their schemas name: Forms, Schemas and Categories - description: | Create and view form submissions name: Submissions - description: | View the roles available in the system. name: IAM Roles - description: > IAM role groups can be assigned to principals to manage authorisation centrally. name: IAM Role Groups - description: | Manage service accounts which can access the API programmatically. name: Service Accounts - description: | Manage bridges between organisations. name: Bridges - description: | Manage settings for an organisation. name: Settings - description: | Manage teams within an organisation. name: Teams - description: | Manage job roles within an organisation. name: Job Roles - description: | Manage users and accounts. name: Users - description: | Invite and manage invitations to organisations. name: Invitations - description: > IAM grants are the asignment of roles or permissions to principals to manage resource access. name: IAM Grants - description: | View the permissions available in the system. name: IAM Permissions - description: | SSO providers are the identity providers for an organisation. name: SSO Providers - description: | Whoami returns information about the currently authenticated principal. name: Whoami - description: | Manage your images name: Images - description: > Organisations are the center point for most resources in the platform. Most other endpoints are subresources of an organisation. name: Organisations - description: | Permits managements, integrated with street manager. name: Permits - description: | Projects manage your work and governance. name: Projects - description: > Import templates allow users to save and reuse their CSV importer configuration as named templates. name: Import Templates - description: | Properties are the physical locations. name: Properties - description: | Search across schemes, work orders, and operations. name: Search - description: | Provides the API specification in JSON and YAML formats name: Specifications - description: | Streets are the physical roads. name: Streets - description: | Integration with street manager name: Street Manager - description: | Vehicles are the physical vehicles that an organisation manages. name: Vehicles - description: > Scheme contracts (also known as regions) group schemes allocated from the network to a contractor. name: Scheme Contracts - description: > Scheme shares allow you to share your schemes with other organisations across bridges. name: Scheme Shares - description: | Schemes are large programmes of work name: Schemes - description: | Work orders the component parts of a scheme. name: Work Orders - description: | Operations are the work to be carried out within work orders. name: Operations externalDocs: description: More documentation and resources url: https://docs.ctrl-hub.com paths: /v3/orgs/{org_id}/projects/permits: get: tags: - Permits description: List all of the permits in an organisation. operationId: ListPermits parameters: - $ref: '#/components/parameters/org_id' - $ref: '#/components/parameters/permits_include' - $ref: '#/components/parameters/permit_filter' - $ref: '#/components/parameters/limit' - $ref: '#/components/parameters/offset' responses: '200': $ref: '#/components/responses/ListPermits' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorised' '500': $ref: '#/components/responses/InternalServerError' security: - Session: [] - OAuth2: [] - Cookie: [] components: parameters: org_id: name: org_id in: path required: true description: The unique identifier for the organisation. schema: type: string format: uuid example: c000c344-8847-47da-a091-32e75902d3b1 permits_include: name: include in: query description: A comma separated list of related resources to include. required: false style: form explode: false schema: type: array items: type: string enum: - operation - work_order - street_manager_permit - responsible_people permit_filter: name: filter in: query description: > Filters the response data based on the value provided. Available filters: - `reference_in`: Filter by permit reference number(s) - `work_status_in`: Filter by work status value(s) - `work_status_not_in`: Exclude permits with specified work status value(s) - `status_in`: Filter by permit status value(s) - `status_not_in`: Exclude permits with specified status value(s) - `risk_in`: Filter by risk level value(s) - `assigned_to_me`: Filter for permits assigned to the current user For more information on using named filters, see [the docs](https://docs.ctrl-hub.com/api-reference/features#filtering) required: false schema: type: string default: '' limit: name: limit in: query description: Limit the number of resources returned by the API required: false schema: type: integer format: int64 minimum: 1 default: 100 offset: name: offset in: query description: Offset the resources returned by the API required: false schema: type: integer format: int64 minimum: 0 default: 0 responses: ListPermits: description: List of permits. headers: Content-Type: $ref: '#/components/headers/content-type' Content-Length: $ref: '#/components/headers/content-length' X-Request-ID: $ref: '#/components/headers/x-request-id' content: application/vnd.api+json: schema: allOf: - type: object required: - data properties: data: title: A list of permits type: array items: $ref: '#/components/schemas/Permit' included: $ref: '#/components/schemas/PermitIncludes' - $ref: '#/components/schemas/PermitDocumentMeta' - $ref: '#/components/schemas/JSONAPI' BadRequest: description: > There was an error with the request - this could be due to an invalid body, query parameters, or headers that were sent to the API. headers: Content-Type: $ref: '#/components/headers/content-type' Content-Length: $ref: '#/components/headers/content-length' X-Request-ID: $ref: '#/components/headers/x-request-id' content: application/vnd.api+json: schema: type: object properties: errors: type: array items: $ref: '#/components/schemas/Error' example: id: 98ca4a78-b66f-4234-9719-aaf832ee6669 status: '400' title: A validation error was encountered source: parameter: include meta: resource: wrong_value Unauthorised: description: Authentication failed headers: Content-Type: $ref: '#/components/headers/content-type' Content-Length: $ref: '#/components/headers/content-length' X-Request-ID: $ref: '#/components/headers/x-request-id' content: application/vnd.api+json: schema: type: object properties: errors: type: array items: $ref: '#/components/schemas/Error' example: id: 05fc9c8d-73b9-4697-9337-57f7a567a48f status: '401' title: You are not authorised to access this resource detail: In order to access this resource, you need the 'admin' role. code: AUTH.001 InternalServerError: description: There was a problem handling the request on the server side headers: Content-Type: $ref: '#/components/headers/content-type' Content-Length: $ref: '#/components/headers/content-length' X-Request-ID: $ref: '#/components/headers/x-request-id' content: application/vnd.api+json: schema: type: object properties: errors: type: array items: $ref: '#/components/schemas/Error' example: id: fe9d9a69-f0a7-4fdc-bb2c-176027f316c5 status: '500' title: Internal Server Error detail: An unexpected error occurred on the server. headers: content-type: description: The content type of the response schema: type: string example: application/vnd.api+json content-length: description: The length of the response body in bytes schema: type: integer format: int32 example: 1234 x-request-id: description: >- An ID that can be provided when reporting bugs to help identify the issue schema: type: string example: 8470f56af4cf25e22be08e72c70dbbdc schemas: Permit: type: object description: A permit required: - id - type - attributes - meta - relationships properties: id: type: string format: uuid description: The unique identifier of the permit. type: type: string const: permits attributes: $ref: '#/components/schemas/PermitAttributes' meta: $ref: '#/components/schemas/PermitMeta' relationships: $ref: '#/components/schemas/PermitRelationships' PermitIncludes: type: array description: Related resources that can be included when a permit is returned items: discriminator: propertyName: type mapping: operations: $ref: '#/components/schemas/Operation' work-orders: $ref: '#/components/schemas/WorkOrder' street-manager-permits: $ref: '#/components/schemas/StreetManagerPermit' users: $ref: '#/components/schemas/User' oneOf: - $ref: '#/components/schemas/Operation' - $ref: '#/components/schemas/WorkOrder' - $ref: '#/components/schemas/StreetManagerPermit' - $ref: '#/components/schemas/User' PermitDocumentMeta: type: object description: Document level meta about the resources for permits required: - meta properties: meta: type: object required: - pagination - stats properties: features: $ref: '#/components/schemas/Features' pagination: $ref: '#/components/schemas/Pagination' stats: type: object required: - risk properties: risk: type: object required: - none - low - medium - high properties: none: type: object properties: total: type: integer description: Total number of permits with no risk examples: - 1 page: type: integer description: Number of permits with no risk on the current page examples: - 1 low: type: object properties: total: type: integer description: Total number of permits with low risk examples: - 2 page: type: integer description: Number of permits with low risk on the current page examples: - 2 medium: type: object properties: total: type: integer description: Total number of permits with medium risk examples: - 3 page: type: integer description: >- Number of permits with medium risk on the current page examples: - 3 high: type: object properties: total: type: integer description: Total number of permits with high risk examples: - 4 page: type: integer description: Number of permits with high risk on the current page examples: - 4 JSONAPI: type: object description: JSON API response object required: - jsonapi properties: jsonapi: type: object required: - version properties: version: type: string description: The version of the JSON API specification examples: - '1.0' Error: type: object description: An error response properties: id: description: >- A unique identifier for this particular occurrence of the problem. If you encounter this, please provide us with the error ID and we can investigate it on our side. type: string format: uuid examples: - 05fc9c8d-73b9-4697-9337-57f7a567a48f status: description: >- The status code for the error. This might not match the HTTP status code if there are more that one errors to return with different status codes. type: string examples: - '401' - '500' title: description: A human readable title for the error. type: string examples: - You are not authorised to access this resource detail: description: >- Where there is more detail that we can provide outside of the title, we will provide it here. type: string examples: - In order to access this resource, you need the 'admin' role. code: description: >- A unique code for the error that may help us to diagnose the issue. Not all errors have codes, so this is usually empty. type: string examples: - AUTH.001 source: description: A JSON object containing additional information about the error. type: object properties: pointer: description: >- A JSON Pointer to the value in the request that caused the error. type: string examples: - /data/attributes/email parameter: description: >- A string indicating which query parameter in the request caused the error. type: string examples: - include required: - id - status - title PermitAttributes: type: object description: Attributes for a permit properties: dates: type: object properties: start: type: string format: date-time description: Permit start date examples: - '2025-09-01T09:00:00Z' end: type: string format: date-time description: Permit end date examples: - '2025-09-30T17:00:00Z' risk: type: object properties: remaining: type: object properties: days: type: number format: float description: Remaining days examples: - 5 percent: type: number format: float minimum: 0 maximum: 100 description: Remaining time as percentage (0-100) examples: - 50 status: type: string description: Risk status enum: - low - medium - high examples: - low PermitMeta: type: object description: Metadata for a permit required: - created_at - updated_at - modified_at properties: created_at: type: string format: date-time description: The date and time when the permit was created examples: - '2025-10-21T15:03:18.069Z' updated_at: type: string format: date-time description: The date and time when the permit was last updated examples: - '2025-10-21T15:03:18.069Z' modified_at: type: string format: date-time description: The date and time when the permit was last modified examples: - '2025-10-21T15:03:18.069Z' source_permit: type: object description: >- The underlying source permit that this permit is based on, for example the Street Manager one properties: usrn: type: number description: The USRN of the source permit examples: - 1234567890 reference: type: string description: The reference ID of the source permit examples: - SM-12345 status: type: string description: The permit status associated of the source permit examples: - refused work_status: type: string description: The work status associated of the source permit examples: - in_progress governance: type: object properties: complete: type: boolean description: Whether the permit has been completed examples: - true PermitRelationships: type: object description: Relationships for a permit properties: operation: type: object required: - data properties: data: $ref: '#/components/schemas/OperationRelationship' work_order: type: object required: - data properties: data: $ref: '#/components/schemas/WorkOrderRelationship' street_manager_permit: type: object required: - data properties: data: $ref: '#/components/schemas/StreetManagerPermitRelationship' Operation: type: object description: An operation required: - id - type - attributes - meta - relationships properties: id: type: string format: uuid description: The unique identifier of the operation. type: type: string const: operations attributes: $ref: '#/components/schemas/OperationAttributes' meta: $ref: '#/components/schemas/OperationMeta' relationships: $ref: '#/components/schemas/OperationRelationships' WorkOrder: type: object description: A work order required: - id - type - attributes - meta - relationships properties: id: type: string format: uuid description: The unique identifier of the work order. examples: - fb082ee5-b678-4451-b02b-8269aaf262a3 type: type: string const: work-orders attributes: $ref: '#/components/schemas/WorkOrderAttributes' meta: $ref: '#/components/schemas/WorkOrderMeta' relationships: $ref: '#/components/schemas/WorkOrderRelationships' StreetManagerPermit: type: object description: A street manager permit required: - id - type - attributes - meta - relationships properties: id: type: string format: uuid description: The unique identifier of the street manager permit. type: type: string const: street-manager-permits attributes: $ref: '#/components/schemas/StreetManagerPermitAttributes' meta: $ref: '#/components/schemas/StreetManagerPermitMeta' relationships: $ref: '#/components/schemas/StreetManagerPermitRelationships' User: type: object description: A user required: - id - type - attributes properties: id: type: string format: uuid description: The unique identifier of the user. examples: - 123e4567-e89b-12d3-a456-426614174000 type: type: string const: users attributes: $ref: '#/components/schemas/UserAttributes' meta: $ref: '#/components/schemas/UserMeta' relationships: $ref: '#/components/schemas/UserRelationships' Features: type: object description: Represents feature configurations of the API properties: include: type: object properties: options: type: array items: type: string examples: - related.resource Pagination: type: object description: Represents pagination details for API responses required: - counts - current_page - offsets - requested properties: counts: type: object required: - pages - resources properties: pages: type: integer examples: - 1 resources: type: integer examples: - 1 current_page: type: integer examples: - 1 offsets: type: object required: - next - previous properties: next: type: - integer - 'null' examples: - null previous: type: - integer - 'null' examples: - null requested: type: object required: - limit - offset properties: limit: type: integer examples: - 10 offset: type: integer examples: - 0 OperationRelationship: type: object description: Represents a relationship to an operation required: - id - type properties: id: type: string format: uuid description: The unique identifier of the operation type: type: string const: operations WorkOrderRelationship: type: object description: Represents a relationship to a work order required: - id - type properties: id: type: string format: uuid description: The unique identifier of the work order type: type: string const: work-orders StreetManagerPermitRelationship: type: object description: Represents a relationship to a street manager permit required: - id - type properties: id: type: string format: uuid description: The unique identifier of the street manager permit type: type: string const: street-manager-permits OperationAttributes: type: object description: Attributes for an operation required: - name - status properties: name: type: string code: type: string description: type: string dates: type: object properties: scheduled: type: object properties: start: type: string format: date-time end: type: string format: date-time labels: type: array items: $ref: '#/components/schemas/Label' requirements: oneOf: - type: object properties: forms: oneOf: - type: array items: type: object required: - id - required properties: id: type: string format: uuid required: type: boolean - type: 'null' - type: 'null' status: type: string enum: - done - in_progress - todo done_reason: type: - string - 'null' enum: - aborted - completed - cancelled - null allOf: - if: properties: status: const: done then: required: - done_reason OperationMeta: type: object description: Metadata for an operation required: - created_at - updated_at - counts properties: created_at: type: string format: date-time description: The date and time when the operation was created updated_at: type: string format: date-time description: The date and time when the operation was last updated counts: type: object required: - streets - properties properties: streets: type: integer description: The number of streets in this operation format: int64 minimum: 0 default: 0 properties: type: integer description: The number of properties in this operation format: int64 minimum: 0 default: 0 related_data: type: object description: Related resources for the operation properties: properties: type: array description: Array of property IDs with postcodes items: type: object description: Property ID and Postcode required: - id - postcode properties: id: type: string format: uuid description: The ID of the property postcode: type: string description: Postcode of the property OperationRelationships: type: object description: Relationships for an operation required: - work_order - scheme - organisation properties: organisation: type: object required: - data properties: data: $ref: '#/components/schemas/OrganisationRelationship' appointment: type: object required: - data properties: data: $ref: '#/components/schemas/AppointmentRelationship' scheme: type: object required: - data properties: data: $ref: '#/components/schemas/SchemeRelationship' work_order: type: object required: - data properties: data: $ref: '#/components/schemas/WorkOrderRelationship' permits: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/PermitRelationship' template: type: object required: - data properties: data: $ref: '#/components/schemas/OperationTemplateRelationship' type: type: object properties: data: $ref: '#/components/schemas/OperationTypeRelationship' teams: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/TeamRelationship' assignees: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/UserRelationship' properties: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/PropertyRelationship' streets: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/StreetRelationship' WorkOrderAttributes: type: object description: Attributes for a work order required: - name properties: name: type: string description: The name of the work order examples: - Infrastructure Maintenance Work Order code: type: string description: The code of the work order examples: - WO-2025-001 description: type: string description: The description of the work order examples: - Routine maintenance and inspection of electrical infrastructure dates: type: object description: The dates associated with the work order properties: anticipated: type: object description: The anticipated start and end dates properties: start: type: string format: date-time description: The anticipated start date examples: - '2025-08-01T09:00:00Z' end: type: string format: date-time description: The anticipated end date examples: - '2025-08-15T17:00:00Z' labels: type: array description: The labels associated with the work order items: $ref: '#/components/schemas/Label' WorkOrderMeta: type: object description: Metadata for a work order required: - created_at - updated_at - modified_at - counts - dates - completeness properties: created_at: type: string format: date-time description: The date and time when the work order was created examples: - '2025-05-06T18:37:12Z' updated_at: type: string format: date-time description: The date and time when the work order was last updated examples: - '2025-05-07T21:12:46Z' modified_at: type: string format: date-time description: The date and time when the work order was last modified examples: - '2025-05-07T21:12:46Z' dates: type: object description: The scheduled dates for the work order properties: scheduled: type: object description: The scheduled start and end dates properties: start: type: string format: date-time description: The scheduled start date examples: - '2025-08-01T09:00:00Z' end: type: string format: date-time description: The scheduled end date examples: - '2025-08-15T17:00:00Z' counts: type: object description: The counts of related entities required: - operations - properties - streets properties: operations: type: integer description: The number of operations in this work order format: int64 minimum: 0 default: 0 examples: - 1 streets: type: integer description: >- The number of streets in this work order (from all of the operations in this work order) format: int64 minimum: 0 default: 0 examples: - 1 properties: type: integer description: >- The number of properties in this work order (from all of the operations in this work order) format: int64 minimum: 0 default: 0 examples: - 1 completeness: type: object description: The completeness statistics for the work order required: - percentage - counts - statuses - done_reasons properties: percentage: type: object description: The percentage breakdown of completion status required: - completed - aborted - unknown - cancelled properties: completed: type: number minimum: 0 maximum: 100 default: 0 description: The percentage of completed operations examples: - 25 aborted: type: number minimum: 0 maximum: 100 default: 0 description: The percentage of aborted operations examples: - 0 unknown: type: number minimum: 0 maximum: 100 default: 0 description: The percentage of operations with unknown status examples: - 75 cancelled: type: number minimum: 0 maximum: 100 default: 0 description: The percentage of cancelled operations examples: - 0 counts: type: object description: The count breakdown of completion status required: - completed - aborted - unknown - cancelled properties: completed: type: integer minimum: 0 default: 0 description: The number of completed operations examples: - 1 aborted: type: integer minimum: 0 default: 0 description: The number of aborted operations examples: - 0 unknown: type: integer minimum: 0 default: 0 description: The number of operations with unknown status examples: - 3 cancelled: type: integer minimum: 0 default: 0 description: The number of cancelled operations examples: - 0 statuses: type: object required: - counts - percentages properties: counts: type: object required: - done - in_progress - todo properties: done: type: integer minimum: 0 default: 0 examples: - 3 in_progress: type: integer minimum: 0 default: 0 examples: - 1 todo: type: integer minimum: 0 default: 0 examples: - 1 percentages: type: object required: - done - in_progress - todo properties: done: type: number minimum: 0 maximum: 100 default: 0 examples: - 60 in_progress: type: number minimum: 0 maximum: 100 default: 0 examples: - 20 todo: type: number minimum: 0 maximum: 100 default: 0 examples: - 20 done_reasons: type: object required: - counts - percentages properties: counts: type: object required: - aborted - cancelled - completed properties: aborted: type: integer minimum: 0 default: 0 examples: - 1 cancelled: type: integer minimum: 0 default: 0 examples: - 2 completed: type: integer minimum: 0 default: 0 examples: - 2 percentages: type: object required: - aborted - cancelled - completed properties: aborted: type: number minimum: 0 maximum: 100 default: 0 examples: - 20 cancelled: type: number minimum: 0 maximum: 100 default: 0 examples: - 40 completed: type: number minimum: 0 maximum: 100 default: 0 examples: - 40 WorkOrderRelationships: type: object description: Relationships for a work order required: - organisation - scheme - operations properties: organisation: type: object required: - data properties: data: $ref: '#/components/schemas/OrganisationRelationship' assignees: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/UserRelationship' teams: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/TeamRelationship' scheme: type: object required: - data properties: data: $ref: '#/components/schemas/SchemeRelationship' operations: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/OperationRelationship' template: type: object required: - data properties: data: $ref: '#/components/schemas/WorkOrderTemplateRelationship' site_managers: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/UserRelationship' folder: type: object required: - data properties: data: $ref: '#/components/schemas/FolderRelationship' StreetManagerPermitAttributes: type: object description: Attributes for a street manager permit required: - activated - end_date - permit_reference_number - permit_reference_number_iteration - start_date - status - usrn - work_reference_number - work_status_ref properties: activated: type: boolean description: Whether the permit is activated or not usrn: type: number description: Unique Street Reference Number permit_reference_number: type: string description: The unique reference number for this permit permit_reference_number_iteration: type: integer description: >- The iteration number of the permit based on the permit reference number work_reference_number: type: string description: The reference number for the work associated with this permit status: type: string description: The current status of the permit enum: - submitted - granted - permit_modification_request - refused - closed - cancelled - revoked - progressed work_status_ref: type: string description: The current status of the work as a reference enum: - completed - cancelled - planned - in_progress start_date: type: string format: date-time description: The start date of the permit end_date: type: string format: date-time description: The end date of the permit StreetManagerPermitMeta: type: object description: Metadata for a street manager permit required: - created_at - modified_at - updated_at properties: created_at: type: string format: date-time description: The date and time when the street manager permit was created modified_at: type: string format: date-time description: The date and time when the street manager permit was last modified updated_at: type: string format: date-time description: The date and time when the street manager permit was last updated StreetManagerPermitRelationships: type: object description: Relationships for a street manager permit properties: latest_version: type: object required: - data properties: data: $ref: '#/components/schemas/StreetManagerPermitVersionRelationship' versions: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/StreetManagerPermitVersionRelationship' UserAttributes: type: object description: Attributes for a user properties: email: type: string format: email description: The email address of the user. examples: - john.doe@example.com status: type: string enum: - active - inactive - pending - unknown description: > The membership status of this user in the organisation in the request URL. Only populated on org-scoped member endpoints; absent on global user endpoints. examples: - active identities: type: array items: type: object properties: id: type: string format: uuid description: The unique identifier for the identity. examples: - 39ce13b8-1116-416a-ad5f-3c5edfd44f53 platform: type: string description: The platform of the identity. examples: - multi_tenant meta: type: - object - 'null' additionalProperties: true description: Additional metadata for the identity. profile: type: object properties: work: type: object properties: occupation: type: string description: The occupation of the user. examples: - Site Manager cscs: type: string description: The CSCS card number of the user. examples: - CSC123456 eusr: type: string description: The EUSR card number of the user. examples: - EUR789123 start_date: type: string format: date description: The start date of the user's employment. examples: - '2020-03-01T00:00:00.000Z' personal: type: object properties: first_name: type: string description: The first name of the user. examples: - John last_name: type: string description: The last name of the user. examples: - Doe dob: type: string format: date description: The date of birth of the user. examples: - '1985-06-15T00:00:00.000Z' username: type: string description: The username of the user. examples: - johndoe contact: type: object properties: mobile: type: string description: The mobile number of the user. examples: - +44 7700 900123 landline: type: string description: The landline of the user. examples: - +44 20 7946 0958 address: type: object properties: number: type: string description: The house number of the user's address. default: '' examples: - '42' street: type: string description: The street of the user's address. examples: - High Street area: type: string description: The area of the user's address. examples: - Westminster town: type: string description: The town of the user's address. examples: - London county: type: string description: The county of the user's address. examples: - Greater London postcode: type: string description: The postcode of the user's address. examples: - SW1A 1AA country_code: type: string description: The country code of the user's address. examples: - GB what3words: type: string description: The what3words location of the user's address. examples: - filled.count.soap settings: type: object properties: preferred_language: type: string description: The preferred language of the user. default: en-GB examples: - en-GB timezone: type: string description: The timezone of the user. examples: - Europe/London UserMeta: type: object description: Metadata for a user properties: grants: type: array items: type: string description: >- This data is only returned on the whoami endpoint - it contains all of the user's granted permissions. UserRelationships: type: object description: Relationships for a user properties: organisations: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/OrganisationRelationship' teams: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/TeamRelationship' managing_organisation: type: object required: - data properties: data: $ref: '#/components/schemas/OrganisationRelationship' Label: type: object description: A label object required: - key - value properties: key: type: string minLength: 1 examples: - Your label key value: type: string examples: - Your label value OrganisationRelationship: type: object description: Represents a relationship to an organisation required: - id - type properties: id: type: string format: uuid description: The unique identifier of the organisation type: type: string const: organisations AppointmentRelationship: type: object description: Represents a relationship to an appointment required: - id - type properties: id: type: string format: uuid description: The unique identifier of the appointment type: type: string const: appointments SchemeRelationship: type: object description: Represents a relationship to a scheme required: - id - type properties: id: type: string format: uuid description: The unique identifier of the scheme type: type: string const: schemes PermitRelationship: type: object description: Represents a relationship to a permit required: - id - type properties: id: type: string format: uuid description: The unique identifier of the permit type: type: string const: permits OperationTemplateRelationship: type: object description: Represents a relationship to an operation template required: - id - type properties: id: type: string format: uuid description: The unique identifier of the operation template type: type: string const: operation-templates OperationTypeRelationship: type: object description: Represents a relationship to an operation type required: - id - type properties: id: type: string format: uuid description: The unique identifier of the operation type type: type: string const: operation-types TeamRelationship: type: object description: Represents a relationship to a team required: - id - type properties: id: type: string format: uuid description: The unique identifier of the team type: type: string const: teams UserRelationship: type: object description: Represents a relationship to a user required: - id - type properties: id: type: string format: uuid description: The unique identifier of the user type: type: string const: users PropertyRelationship: type: object description: Represents a relationship to a property required: - id - type properties: id: type: string format: uuid description: The unique identifier of the property type: type: string const: properties StreetRelationship: type: object description: Represents a relationship to a street required: - id - type properties: id: type: string format: uuid description: The unique identifier of the street type: type: string const: streets WorkOrderTemplateRelationship: type: object description: Represents a relationship to a work order template required: - id - type properties: id: type: string format: uuid description: The unique identifier of the work order template type: type: string const: work-order-templates FolderRelationship: type: object description: Represents a relationship to a folder required: - id - type properties: id: type: string format: uuid description: The unique identifier of the folder type: type: string const: folders StreetManagerPermitVersionRelationship: type: object description: Represents a relationship to a street manager permit version required: - id - type properties: id: type: string format: uuid description: The unique identifier of the street manager permit version type: type: string const: street-manager-permit-versions securitySchemes: Session: description: | Session token for authentication. in: header name: X-Session-Token type: apiKey OAuth2: description: | OAuth2 token for authentication. flows: clientCredentials: scopes: {} tokenUrl: https://auth.ctrl-hub.com/oauth2/token type: oauth2 Cookie: description: | Cookie token for authentication. in: cookie name: ctrl_hub_session type: apiKey ````