> ## Documentation Index > Fetch the complete documentation index at: https://docs.tented.ai/llms.txt > Use this file to discover all available pages before exploring further. # List per-row results > Paginated per-row outcomes of an import run, ordered by row number. Each result records what happened to one CSV row — `created`, `updated`, `skipped`, or `failed` — with the affected contact ID and any field-level validation issues. Use the `status` filter to pull just the rows that need attention (e.g. `status=failed`). ## OpenAPI ````yaml /api-reference/openapi.json get /v1/contacts/imports/{importRunId}/results openapi: 3.1.0 info: title: Tented API version: 1.0.0 description: >- The Tented public API: generate, publish, and manage AI-built web pages (tents), and run the email platform — contacts, reusable emails, one-time blasts, and triggered flows. ## Authentication Authenticate every request with a workspace API key: `Authorization: Bearer `. Keys are created in **Workspace Settings → API Keys** and are scoped to a single workspace. ## Asynchronous work Tent generation, bulk creation, and email AI generation return `202 Accepted` immediately. Poll the corresponding status endpoint (`GET /v1/tents/{tentId}`, `GET /v1/bulk-jobs/{bulkJobId}`, `GET /v1/emails/{emailId}/generations/{generationId}`) — no more than every 10 seconds. ## Pagination Email listings use cursor pagination (`cursor`/`next_cursor`). Blast, flow, and member listings use page pagination (`page`/`limit` with a `pagination` object in the response). ## Conventions Request and response fields are snake_case, with two exceptions: analytics query parameters (`tentIdOrAlias`, `daysBack`) and segment rule trees (camelCase keys such as `listId` and `timeWindow`). contact: name: Tented Support email: support@tented.ai servers: - url: https://api.tented.ai description: Production security: - bearerAuth: [] tags: - name: Tents description: >- Create, edit, publish, and manage AI-generated pages, including asset uploads and bulk creation. - name: Analytics description: Traffic analytics for single tents and the whole workspace. - name: Contacts description: >- Batch create, update, and delete contacts. Up to 25 items per request with per-item results. - name: Emails description: >- Reusable email content: AI generation, direct HTML edits, plain-text control, and approval. - name: Email Blasts description: >- One-time sends to an audience: compose, schedule, track engagement, export recipients. - name: Triggered Flows description: >- Multi-step automations that enroll contacts on triggers and move them through a step graph. - name: Contact Imports - name: Contact Fields - name: Contact Lists - name: Email Templates - name: Tent Templates description: >- Reusable, AI-editable tent layouts. Create from HTML or an existing tent, iterate with AI, approve, and clone. Approved tent templates seed new tents. paths: /v1/contacts/imports/{importRunId}/results: get: tags: - Contact Imports summary: List per-row results description: >- Paginated per-row outcomes of an import run, ordered by row number. Each result records what happened to one CSV row — `created`, `updated`, `skipped`, or `failed` — with the affected contact ID and any field-level validation issues. Use the `status` filter to pull just the rows that need attention (e.g. `status=failed`). operationId: list-contact-import-run-results parameters: - name: importRunId in: path required: true schema: type: string format: uuid description: Import run ID. - name: page in: query required: false schema: type: integer minimum: 1 default: 1 description: Page number (1-based). - name: limit in: query required: false schema: type: integer minimum: 1 maximum: 250 default: 100 description: Results per page (1–250). - name: status in: query required: false schema: type: string enum: - created - updated - skipped - failed description: Only return rows with this outcome. responses: '200': description: Page of per-row results. content: application/json: schema: type: object properties: items: type: array items: $ref: '#/components/schemas/ContactImportRowResult' description: Per-row outcomes, ordered by `row_number` ascending. pagination: $ref: '#/components/schemas/Pagination' required: - items - pagination '400': description: >- Bad request — invalid parameters. Validation failures include `details.issues` with per-field messages. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Unauthorized — missing, malformed, revoked, or expired API key. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- Not found — the resource does not exist in the workspace tied to your API key. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: ContactImportRowResult: type: object properties: row_number: type: integer description: >- 1-based CSV line number, counting the header row as line 1 (the first data row is 2). status: type: string enum: - created - updated - skipped - failed description: What happened to the row. reason: type: string description: Why the row was skipped or failed. Omitted for clean successes. contact_id: type: string format: uuid description: >- The contact the row created or updated. Omitted when no contact was written. field_issues: type: array items: $ref: '#/components/schemas/ContactImportFieldIssue' description: >- Field-level validation issues for this row. Omitted when there were none. required: - row_number - status description: The outcome of a single imported row. Pagination: type: object properties: page: type: integer description: Current page (1-based). limit: type: integer description: Page size. total: type: integer description: Total matching records. totalPages: type: integer description: Total number of pages. description: Offset pagination metadata. Error: type: object properties: error: type: string description: Human-readable error message. error_code: type: string description: >- Stable machine-readable error code (present on email, blast, flow, and related endpoints, e.g. `campaign_not_ready`, `generation_in_progress`). message: type: string description: Additional human-readable context (present on some tent endpoints). code: type: string description: >- Machine-readable code used by tent creation errors (e.g. `INVALID_PROMPT_INTENT`). details: type: object additionalProperties: true description: >- Additional error context. Validation errors include `issues`: an array of `{ path, message }` objects. limit: type: integer description: Plan limit that was hit (present on `429` publish-limit errors). current: type: integer description: >- Current usage against the limit (present on `429` publish-limit errors). required: - error description: >- Error response. All errors include `error`; the other fields vary by endpoint group. ContactImportFieldIssue: type: object properties: row_number: type: integer description: >- 1-based CSV line number, counting the header row as line 1 (the first data row is 2). header: type: string description: CSV column header the issue occurred in. target_field: type: string description: Target field `api_name` the column maps to. code: type: string enum: - invalid_email - invalid_phone - invalid_boolean - invalid_number - invalid_date - invalid_value_too_long - invalid_list_id - unknown_list_id - dynamic_list_not_supported - system_list_not_writable - missing_identity_mapping description: Machine-readable issue code. message: type: string description: Human-readable explanation. value: type: string description: The offending cell value. required: - row_number - header - target_field - code - message - value description: A field-level validation issue for one cell of the import. securitySchemes: bearerAuth: type: http scheme: bearer description: >- Workspace API key, e.g. `Authorization: Bearer tented_...`. Create keys in Workspace Settings → API Keys. ````