> ## Documentation Index > Fetch the complete documentation index at: https://docs.userkit.dev/llms.txt > Use this file to discover all available pages before exploring further. # Read an import and its lines > The report. `?outcome=` narrows to one status, which is how the two lists that matter get read — `failed` and `conflict` — without paging through the successes. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/contact-imports/{id} openapi: 3.1.0 info: title: UserKit API version: 1.0.0 description: >- The HTTP surface of UserKit. Two planes share one API. The **staff plane** is what a human uses in the panel: users, organizations, roles, members, keys. The **customer plane** is what a developer's own product uses: contacts, identities, hosted or federated sign-in. Every error answers the same envelope — `{"error": {"code", "message"}}`. The `code` is a stable contract to branch on; the `message` is for a person and may change. servers: - url: '{baseUrl}' description: The API host. variables: baseUrl: default: https://api.userkit.dev description: Base URL of the API, no trailing slash. security: - sessionToken: [] tags: - name: Authentication description: >- Public sign-up, sign-in, two-factor and password recovery for staff accounts. - name: Session description: >- The active session: who the caller is, which organization they are in, and signing out. - name: Account description: The caller's own account — profile, password, sessions, avatar. - name: Two-factor description: >- TOTP setup, activation and recovery codes. Returns 501 when two-factor is unavailable on the server. - name: Organizations description: The organizations a user belongs to, and the active one. - name: Environments description: >- The live and test environments seeded with every organization, and their identity settings. - name: Members description: Memberships and invitations. - name: Roles description: Roles and the permission catalogue they draw from. - name: Audit log description: >- What staff did inside an organization. Append-only, and read behind its own permission. - name: API keys description: Secret keys (`uk_sk_…`) and publishable keys (`uk_pk_…`). - name: Contacts (staff session) description: >- The staff view of the customer plane, opened by a staff session. Reads take `?environment=` as an explicit view parameter. - name: Contacts (API key) description: >- The machine surface, authenticated by an API key. The environment is the key's environment and cannot be named by the caller. - name: Customer plane description: >- Called from the developer's own pages with a publishable key: boot, magic link, and the contact's own session. - name: Hosted auth description: >- Sign-up, sign-in, verification and recovery for contacts, when UserKit owns the account. - name: Customer teams description: >- A customer is a team. Its roster, its invitations and its two roles — owner and member — administered by the contact's own session. The active customer travels in `X-Customer-Id`. - name: Webhooks description: >- Outbound webhooks: endpoints, the published event catalogue, the delivery log, replay and test sends. Never gated by a plan — webhooks are a developer primitive. - name: Catalogue description: >- The plans, prices and features **you** sell to your own customers. Per environment, a price per currency, and `recurring` or `one_time`. Distinct from the plan you are on with UserKit, which is `GET /v1/organization/entitlements`. - name: Subscriptions description: >- What one of **your** customers is paying you, mirrored from the gateway that charges them. The gateway is the truth about money — it holds the schedule, runs the retries and decides what a proration is worth — so these routes ask it to change something and answer with what it then said. `provider_synced_at` is how stale the copy admits to being. - name: Provider webhooks description: >- Where a payment provider delivers to. Not a surface you call — it is a URL you paste into the provider's dashboard, which is why it sits outside `/v1`: a version bump must never mean editing a setting in somebody else's product. Signed with the secret of the connection named in the path, and safe to retry. - name: Entitlements description: >- What one of **your** customers may do, resolved: the plan their subscription carries, plus the overrides you promised them on top. This is the read your own gate calls, so it is cached and answers in one round trip. It is a different question from `GET /v1/organization/entitlements`, which is the plan **you** are on with UserKit — two catalogues, same word, different money. paths: /v1/organization/contact-imports/{id}: get: tags: - Contacts (staff session) summary: Read an import and its lines description: >- The report. `?outcome=` narrows to one status, which is how the two lists that matter get read — `failed` and `conflict` — without paging through the successes. operationId: getContactImport parameters: - $ref: '#/components/parameters/OrganizationHeader' - name: id in: path required: true schema: type: string format: uuid - $ref: '#/components/parameters/EnvironmentQuery' - name: outcome in: query required: false schema: type: string enum: - pending - created - matched - conflict - failed description: Only the lines with this outcome. Omit for every line. - $ref: '#/components/parameters/Limit' - $ref: '#/components/parameters/Offset' responses: '200': description: The import and the lines behind it. content: application/json: schema: type: object properties: import: $ref: '#/components/schemas/ContactImport' rows: type: array items: $ref: '#/components/schemas/ContactImportRow' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' components: parameters: OrganizationHeader: name: X-Organization-Id in: header required: false schema: type: string description: >- The organization the caller is acting on — the `org_…` code that appears in the panel URL. It *identifies*; the membership JOIN is what *authorizes*, so a forged code reads nothing. Absent, the session's default organization answers. EnvironmentQuery: name: environment in: query required: false schema: type: string enum: - live - test default: live description: >- Which environment to act in. A view parameter, valid only on the staff surface — a machine credential never chooses its environment, it is resolved from the key. Limit: name: limit in: query required: false schema: type: integer default: 50 minimum: 1 maximum: 200 description: Page size. Values outside 1–200 fall back to 50. Offset: name: offset in: query required: false schema: type: integer default: 0 minimum: 0 schemas: ContactImport: type: object description: >- One CSV import. Progress is derived from its lines on every read rather than accumulated as the worker goes — the tallies are a query, never a counter, because a counter maintained by a job the queue may retry double-counts. properties: id: type: string format: uuid filename: type: string columns: type: array items: type: string description: >- The header as it arrived, so the report can say what was understood without keeping the file. status: type: string enum: - pending - processing - completed total: type: integer description: Lines the parse counted, fixed at upload. pending: type: integer description: Lines not applied yet. created: type: integer description: Contacts that did not exist here and now do. matched: type: integer description: Contacts that already existed. Their profiles were left alone. conflicts: type: integer description: >- Lines naming two different existing contacts. Nothing was written for them; the repair is a manual merge. failed: type: integer description: Lines that could not be read or could not be applied. created_at: type: string format: date-time finished_at: type: string format: date-time nullable: true ContactImportRow: type: object description: One line of an import, and what became of it. properties: line: type: integer description: >- The line number in the file, header included — the one the spreadsheet shows. email: type: string external_id: type: string name: type: string customer: type: string status: type: string enum: - pending - created - matched - conflict - failed error_code: type: string description: >- Stable code for a line that did not land: `no_identifier`, `invalid_email`, `invalid_customer_role`, `customer_role_without_customer`, `malformed_row`, `identity_conflict`, `apply_failed`. error: type: string description: The sentence a person reads. contact_id: type: string format: uuid nullable: true conflicting_contact_id: type: string format: uuid nullable: true description: >- The other contact a colliding line named. Both ids travel because the repair is a manual merge, and a merge takes two. Error: type: object description: Every error in this API answers this envelope. properties: error: type: object properties: code: type: string description: Stable. Branch on this. message: type: string description: For a person. May change. required: - code - message required: - error example: error: code: forbidden message: your role does not allow this action responses: BadRequest: description: '`invalid_request` — the body or a parameter is malformed.' content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: >- `unauthorized` — missing, malformed or expired credential. A well-formed credential from the wrong family says so: "this endpoint expects a staff session token, not an organization API key". content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: '`forbidden` — your role does not allow this action.' content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: >- `not_found`. Also the answer for a resource that exists in another organization or environment — the 404 never reveals which. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: sessionToken: type: http scheme: bearer description: >- A staff session token, `uk_st_…`. Minted by sign-up, sign-in or the two-factor exchange. ````