> ## Documentation Index > Fetch the complete documentation index at: https://docs.member.dev/llms.txt > Use this file to discover all available pages before exploring further. # List Definitions For Hub > The team's attribute definitions, read through one of its hubs. Same document and pagination as ``GET /teams/{team_id}/contact-attributes`` (keyset on ``(position, id)``: a reorder between page requests can repeat or skip a row, see ``_definition_list_response``). That route stays team-admin only (team owner or admin). This one admits the same team owner or admin (``require_team_admin_or_hub_editor``, as ``list_hub_configs``) and also the hub's owner or admin contact, which is the only session the hub inline editor holds: its onboarding question picker needs the team's definitions. The hub in the path is what scopes the contact grant. The gate resolves it under ``team_id`` and checks the contact's live owner/admin membership of it, so a contact can only read definitions of a team it edits a hub in. A hub outside the team, or a contact with no standing on it, gets the gate's single 404; a member or moderator gets 403. Platform and API-key callers get the team-admin chain, so a missing hub stays the service's 404 below. ## OpenAPI ````yaml /openapi/mio-openapi.json get /api/v1/teams/{team_id}/hubs/{hub_id}/contact-attribute-definitions openapi: 3.1.0 info: description: >- Production API reference for Membership.io. Use the authored guides for workflows and the generated endpoint pages for exact parameters and schemas. title: Membership.io API version: 0.1.0 servers: - description: Production url: https://api.member.dev security: - bearerAuth: [] paths: /api/v1/teams/{team_id}/hubs/{hub_id}/contact-attribute-definitions: get: tags: - contact-attributes-admin-hub-config summary: List Definitions For Hub description: >- The team's attribute definitions, read through one of its hubs. Same document and pagination as ``GET /teams/{team_id}/contact-attributes`` (keyset on ``(position, id)``: a reorder between page requests can repeat or skip a row, see ``_definition_list_response``). That route stays team-admin only (team owner or admin). This one admits the same team owner or admin (``require_team_admin_or_hub_editor``, as ``list_hub_configs``) and also the hub's owner or admin contact, which is the only session the hub inline editor holds: its onboarding question picker needs the team's definitions. The hub in the path is what scopes the contact grant. The gate resolves it under ``team_id`` and checks the contact's live owner/admin membership of it, so a contact can only read definitions of a team it edits a hub in. A hub outside the team, or a contact with no standing on it, gets the gate's single 404; a member or moderator gets 403. Platform and API-key callers get the team-admin chain, so a missing hub stays the service's 404 below. operationId: >- contact_attributes_admin_hub_config.get_contact_attributes_admin_hub_config_get_teams_by_team_id_hubs_by_hub_id_contact_attribute_definitions parameters: - in: path name: team_id required: true schema: title: Team Id type: string - in: path name: hub_id required: true schema: title: Hub Id type: string - in: query name: page[after] required: false schema: anyOf: - type: string - type: 'null' title: Page[After] - in: query name: page[size] required: false schema: default: 20 maximum: 100 minimum: 1 title: Page[Size] type: integer responses: '200': content: application/vnd.api+json: schema: $ref: '#/components/schemas/DefinitionListResponse' description: Successful Response '400': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Validation error '401': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Not authenticated '403': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Forbidden '404': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Resource not found '409': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Conflict '422': content: application/vnd.api+json: schema: $ref: '#/components/schemas/JsonApiErrorResponse' description: Unprocessable entity security: - HTTPBearer: [] components: schemas: DefinitionListResponse: additionalProperties: false properties: data: items: $ref: '#/components/schemas/DefinitionResource' title: Data type: array links: additionalProperties: true title: Links type: object meta: additionalProperties: true title: Meta type: object required: - data - meta - links title: DefinitionListResponse type: object JsonApiErrorResponse: description: Error JSON:API response. properties: errors: items: $ref: '#/components/schemas/JsonApiError' title: Errors type: array meta: anyOf: - additionalProperties: true type: object - type: 'null' title: Meta required: - errors title: JsonApiErrorResponse type: object DefinitionResource: additionalProperties: false properties: attributes: $ref: '#/components/schemas/DefinitionAttributes' id: title: Id type: string links: anyOf: - $ref: '#/components/schemas/JsonApiLinks' - type: 'null' type: const: contact_attribute_definitions default: contact_attribute_definitions title: Type type: string required: - id - attributes title: DefinitionResource type: object JsonApiError: properties: code: anyOf: - type: string - type: 'null' title: Code detail: anyOf: - type: string - type: 'null' title: Detail id: anyOf: - type: string - type: 'null' title: Id meta: anyOf: - additionalProperties: true type: object - type: 'null' title: Meta source: anyOf: - additionalProperties: type: string type: object - type: 'null' title: Source status: title: Status type: string title: title: Title type: string required: - status - title title: JsonApiError type: object DefinitionAttributes: additionalProperties: false properties: created_at: format: date-time title: Created At type: string description: anyOf: - type: string - type: 'null' title: Description is_contact_editable: title: Is Contact Editable type: boolean name: title: Name type: string position: title: Position type: integer slug: title: Slug type: string team_id: title: Team Id type: string type: enum: - text - number - boolean - date - multiple - single title: Type type: string updated_at: format: date-time title: Updated At type: string required: - team_id - slug - name - type - description - is_contact_editable - position - created_at - updated_at title: DefinitionAttributes type: object JsonApiLinks: properties: self: anyOf: - type: string - type: 'null' title: Self title: JsonApiLinks type: object securitySchemes: bearerAuth: bearerFormat: JWT or mio_sk API key description: >- Send platform JWTs, contact JWTs, or team API keys as `Authorization: Bearer `. scheme: bearer type: http HTTPBearer: scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.