> ## 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.

# Follow Member

> Follow a member (idempotent — re-follow returns the original row, 201).

Bodyless POST. Runs the full visibility gate on the TARGET (contact_id)
before attempting the follow — a blocked, hidden, banned, left, or
missing target yields the gate's own 403/404 with no existence leak.

load_visible_member's READ gate deliberately lets an ELEVATED viewer
(owner/admin/moderator) open a banned/soft_banned target and bypass
hide_profile — correct for moderation reads, wrong for creating a follow
edge. The write-specific re-check below applies to every viewer,
elevated included, so a moderator cannot follow a banned or hidden
member. It returns the exact same 404 shape the visibility gate uses so
elevated and non-elevated responses stay indistinguishable (no new
oracle for probing target state).



## OpenAPI

````yaml /openapi/mio-openapi.json post /api/v1/hubs/{hub_id}/members/{contact_id}/follow
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/hubs/{hub_id}/members/{contact_id}/follow:
    post:
      tags:
        - follows
      summary: Follow Member
      description: |-
        Follow a member (idempotent — re-follow returns the original row, 201).

        Bodyless POST. Runs the full visibility gate on the TARGET (contact_id)
        before attempting the follow — a blocked, hidden, banned, left, or
        missing target yields the gate's own 403/404 with no existence leak.

        load_visible_member's READ gate deliberately lets an ELEVATED viewer
        (owner/admin/moderator) open a banned/soft_banned target and bypass
        hide_profile — correct for moderation reads, wrong for creating a follow
        edge. The write-specific re-check below applies to every viewer,
        elevated included, so a moderator cannot follow a banned or hidden
        member. It returns the exact same 404 shape the visibility gate uses so
        elevated and non-elevated responses stay indistinguishable (no new
        oracle for probing target state).
      operationId: follows.post_follows_post_hubs_by_hub_id_members_by_contact_id_follow
      parameters:
        - in: path
          name: hub_id
          required: true
          schema:
            title: Hub Id
            type: string
        - in: path
          name: contact_id
          required: true
          schema:
            title: Contact Id
            type: string
      responses:
        '201':
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/JsonApiResponse_MemberFollowAttributes_'
          description: Successful Response
        '422':
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
      security:
        - HTTPBearer: []
components:
  schemas:
    JsonApiResponse_MemberFollowAttributes_:
      properties:
        data:
          $ref: '#/components/schemas/JsonApiResource_MemberFollowAttributes_'
        included:
          anyOf:
            - items: {}
              type: array
            - type: 'null'
          title: Included
        links:
          anyOf:
            - $ref: '#/components/schemas/JsonApiLinks'
            - type: 'null'
        meta:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Meta
      required:
        - data
      title: JsonApiResponse[MemberFollowAttributes]
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    JsonApiResource_MemberFollowAttributes_:
      properties:
        attributes:
          $ref: '#/components/schemas/MemberFollowAttributes'
        id:
          title: Id
          type: string
        links:
          anyOf:
            - $ref: '#/components/schemas/JsonApiLinks'
            - type: 'null'
        meta:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Meta
        relationships:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Relationships
        type:
          title: Type
          type: string
      required:
        - id
        - type
        - attributes
      title: JsonApiResource[MemberFollowAttributes]
      type: object
    JsonApiLinks:
      properties:
        self:
          anyOf:
            - type: string
            - type: 'null'
          title: Self
      title: JsonApiLinks
      type: object
    ValidationError:
      properties:
        ctx:
          title: Context
          type: object
        input:
          title: Input
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
        - loc
        - msg
        - type
      title: ValidationError
      type: object
    MemberFollowAttributes:
      description: Wire-shape attributes for a member_follows resource.
      properties:
        created_at:
          format: date-time
          title: Created At
          type: string
        followed_contact_id:
          title: Followed Contact Id
          type: string
        follower_contact_id:
          title: Follower Contact Id
          type: string
        hub_id:
          title: Hub Id
          type: string
      required:
        - hub_id
        - follower_contact_id
        - followed_contact_id
        - created_at
      title: MemberFollowAttributes
      type: object
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT or mio_sk API key
      description: >-
        Send platform JWTs, contact JWTs, or team API keys as `Authorization:
        Bearer <token>`.
      scheme: bearer
      type: http
    HTTPBearer:
      scheme: bearer
      type: http

````