> ## Documentation Index > Fetch the complete documentation index at: https://docs.sapt.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get a Close lead journey > Return the Sapt web journey for one native Close lead without importing it into Sapt CRM. Sapt reads the lead from the project Close connection, then resolves every tracked browser by exact Close id, normalized email/phone, or a single-candidate fbclid. A valid lead with no tracked visit returns `matched: false` and an empty journey. Authenticate with `Authorization: ApiKey ` using a project service-account key scoped to `crm_objects:read`. ## OpenAPI ````yaml https://api.sapt.ai/openapi.json get /projects/{projectId}/integrations/close/journey openapi: 3.1.0 info: title: Sapt Platform API version: 1.0.0 description: >- API for Sapt platform - project management, authentication, and email services servers: - url: https://api.sapt.ai description: Production - url: http://localhost:8787 description: Local development security: [] tags: - name: Accounts description: >- The social accounts connected to a project. Start here — the `id` of an account is the `socialAccountId` that every posting, scheduling and analytics call takes. - name: Actions - name: Ads - name: Agents - name: Analytics description: >- Account- and post-level organic performance for connected Instagram and Facebook accounts. - name: Assets - name: Auth - name: CMS - name: CRM - name: Calendar - name: Comments description: >- Read, reply to, hide and delete comments on published Instagram and Facebook posts. - name: Content Calendar description: >- Create, schedule, update and publish organic posts, and stage the media they carry. Publishing a post whose status is `failed` retries it. - name: Contracts - name: Conversions description: >- Meta server-side Conversions API (CAPI): discover pixels, connect a pixel + CAPI token, and send deduped server-side conversions. - name: Dashboard Sidebar - name: Emails - name: Engagement description: >- Act as the Page or account on published posts: comment, like, unlike, and delete a published post. - name: Geo - name: Google Ads - name: Google Analytics - name: Google Business - name: Integrations description: >- Connect third-party providers (Meta, Gmail, Google Business Profile, …). List providers, mint OAuth connect links, and poll connection status. - name: Invitations - name: Memory - name: OAuth Clients - name: Project Roles - name: Project Templates - name: Projects - name: Schedules - name: Service Accounts - name: Socials description: >- Organic social: the connected accounts, the content calendar, media staging, publishing, comments and engagement across Instagram, Facebook, TikTok, YouTube and Google Business Profile. - name: Team - name: Users - name: Web Analytics - name: Workflows paths: /projects/{projectId}/integrations/close/journey: get: tags: - Integrations - CRM summary: Get a Close lead journey description: >- Return the Sapt web journey for one native Close lead without importing it into Sapt CRM. Sapt reads the lead from the project Close connection, then resolves every tracked browser by exact Close id, normalized email/phone, or a single-candidate fbclid. A valid lead with no tracked visit returns `matched: false` and an empty journey. Authenticate with `Authorization: ApiKey ` using a project service-account key scoped to `crm_objects:read`. operationId: getCloseLeadJourney parameters: - schema: type: string format: uuid required: true name: projectId in: path - schema: type: string maxLength: 500 required: false name: cursor in: query - schema: type: integer minimum: 1 maximum: 100 required: false name: limit in: query - schema: type: string description: >- Comma-separated journey kinds: web, communication, engagement, commerce, lifecycle, advertising, system. required: false description: >- Comma-separated journey kinds: web, communication, engagement, commerce, lifecycle, advertising, system. name: kinds in: query - schema: type: string minLength: 1 maxLength: 200 description: Close lead id, for example `lead_6ANU`. required: true description: Close lead id, for example `lead_6ANU`. name: close_lead_id in: query responses: '200': description: Success content: application/json: schema: type: object properties: close_lead_id: type: string matched: type: boolean description: >- Whether this Close lead resolved to at least one tracked Sapt visitor. match_method: type: - string - 'null' enum: - close_lead_id - identity - fbclid - null description: >- Strongest resolution signal used: an exact stamped Close id, normalized email/phone, or a single-candidate first-touch fbclid. visitor_ids: type: array items: type: string description: >- Every first-party browser/device included in the returned journey. journey: type: object properties: header: type: object properties: firstTouch: type: - object - 'null' properties: utm_source: type: string utm_medium: type: string utm_campaign: type: string utm_term: type: string utm_content: type: string gclid: type: string fbclid: type: string msclkid: type: string ttclid: type: string wbraid: type: string gbraid: type: string li_fat_id: type: string twclid: type: string epik: type: string dclid: type: string sapt_cid: type: string referrer: type: string landingPath: type: string userAgent: type: string ip: type: string fbc: type: string fbp: type: string lastTouch: type: - object - 'null' properties: utm_source: type: string utm_medium: type: string utm_campaign: type: string utm_term: type: string utm_content: type: string gclid: type: string fbclid: type: string msclkid: type: string ttclid: type: string wbraid: type: string gbraid: type: string li_fat_id: type: string twclid: type: string epik: type: string dclid: type: string sapt_cid: type: string referrer: type: string landingPath: type: string userAgent: type: string ip: type: string fbc: type: string fbp: type: string firstSeenAt: type: - string - 'null' format: date-time lastSeenAt: type: - string - 'null' format: date-time webSessions: type: integer pageviews: type: integer revenueCents: type: integer orderCount: type: integer totalTouches: type: integer deviceCount: type: integer identities: type: object properties: email: type: string phone: type: string socials: type: array items: type: string required: - firstTouch - lastTouch - firstSeenAt - lastSeenAt - webSessions - pageviews - revenueCents - orderCount - totalTouches - deviceCount - identities items: type: array items: type: object properties: id: type: string source: type: string enum: - ledger - analytics - scheduled - calendar kind: type: string enum: - web - communication - engagement - commerce - lifecycle - advertising - system type: type: string occurredAt: type: string format: date-time scheduledFor: type: string format: date-time status: type: string enum: - sent - delivered - opened - clicked - failed - scheduled - waiting title: type: string channel: type: string direction: type: string enum: - inbound - outbound recordId: type: string workflowId: type: string provenance: type: object properties: workflowId: type: string runId: type: string stepIndex: type: integer totalSteps: type: integer campaignId: type: string cancel: type: object properties: kind: type: string enum: - workflow_run_v2 - scheduled_email_send - scheduled_post - scheduled_execution id: type: string required: - kind - id detail: type: object additionalProperties: {} required: - id - source - kind - type - occurredAt - title - detail nextCursor: type: - string - 'null' required: - items - nextCursor required: - close_lead_id - matched - match_method - visitor_ids - journey '400': description: Bad request content: application/json: schema: type: object properties: message: type: string description: Error message code: type: string description: Error code for programmatic handling required: - message '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string description: Error message code: type: string description: Error code for programmatic handling required: - message '403': description: Forbidden content: application/json: schema: type: object properties: message: type: string description: Error message code: type: string description: Error code for programmatic handling required: - message '404': description: Not found content: application/json: schema: type: object properties: message: type: string description: Error message code: type: string description: Error code for programmatic handling required: - message security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT token obtained from /api/auth/token endpoint. Token is verified using JWKS and must include a valid user identifier. ````