> ## Documentation Index > Fetch the complete documentation index at: https://docs.outbound.dev/llms.txt > Use this file to discover all available pages before exploring further. # Add rows to a list > Adds up to 500 people to a people list from what you know about them, each with at least one of `email`, `linkedinUrl`, `firstName` and `lastName`. Nothing is looked up: an email address is kept as sent, unchecked. Each row becomes a new person, even one already in the workspace: a row sent twice is added twice, and so is every row of a call sent again. A company list answers `422` `people_list_required`. Free. **Scope:** lists, with a key that can write. ## OpenAPI ````yaml /openapi.json post /v1/lists/{listId}/rows openapi: 3.1.0 info: title: outbound.dev API version: v1 description: Find people and companies, and see what every call costs, with one API key. servers: - url: https://api.outbound.dev security: [] tags: - name: People description: >- Search people with filters, a saved search or a plain-language query, count matches and look up filter values. - name: Companies description: >- Search companies, count matches, name one company by its name, domain or LinkedIn page, and list its people. - name: Saved searches description: Keep a search under a title and run it again, for people or for companies. - name: Lists description: >- Keep people or companies in lists: create and change lists, page through their rows, and add or remove people. - name: Folders description: Group lists of one kind into folders. - name: Jobs description: >- Long tasks a call started: their progress, what they produced and what they were charged. - name: Account description: >- The calling key and its organization, its rate limits, and revoking the key. - name: Billing description: The balance, the ledger of every change to it, and the price list. - name: Usage and requests description: >- Calls and spend by day, and the record of every request of the last 30 days. paths: /v1/lists/{listId}/rows: post: tags: - Lists summary: Add rows to a list description: >- Adds up to 500 people to a people list from what you know about them, each with at least one of `email`, `linkedinUrl`, `firstName` and `lastName`. Nothing is looked up: an email address is kept as sent, unchecked. Each row becomes a new person, even one already in the workspace: a row sent twice is added twice, and so is every row of a call sent again. A company list answers `422` `people_list_required`. Free. **Scope:** lists, with a key that can write. operationId: postListsListIdRows parameters: - name: listId in: path required: true description: The list's id. schema: type: string minLength: 24 maxLength: 24 pattern: ^[0-9a-fA-F]+$ requestBody: required: true content: application/json: schema: type: object properties: rows: type: array description: >- The people to add, at most 500. Each row becomes a new person, even one already in the workspace. minItems: 1 maxItems: 500 items: type: object description: >- One person: at least one of `email`, `linkedinUrl`, `firstName` and `lastName`. properties: firstName: type: string maxLength: 200 lastName: type: string maxLength: 200 email: type: string description: >- Kept as the person's address to write to. It is not checked. maxLength: 320 phone: type: string description: >- In any dialable form. Without a leading `+` and country code, it is read as a US number. maxLength: 50 linkedinUrl: type: string description: >- The LinkedIn profile. A link that is not to LinkedIn is dropped. maxLength: 500 jobTitle: type: string maxLength: 300 companyName: type: string description: >- The employer, matched to a company already in the workspace when there is one. maxLength: 300 companyDomain: type: string description: The employer's domain, such as `northwind.example`. maxLength: 300 example: - firstName: Ana lastName: Costa email: ana.costa@example.com companyName: Northwind Freight - linkedinUrl: https://www.linkedin.com/in/rui-almeida jobTitle: Fleet Manager required: - rows example: rows: - firstName: Ana lastName: Costa email: ana.costa@example.com companyName: Northwind Freight - linkedinUrl: https://www.linkedin.com/in/rui-almeida jobTitle: Fleet Manager responses: '201': description: The people added, one for each row sent. headers: X-Request-Id: $ref: '#/components/headers/RequestId' X-Charged-Usd: $ref: '#/components/headers/ChargedUsd' X-Balance-Usd: $ref: '#/components/headers/BalanceUsd' RateLimit-Limit: $ref: '#/components/headers/RateLimitLimit' RateLimit-Remaining: $ref: '#/components/headers/RateLimitRemaining' RateLimit-Reset: $ref: '#/components/headers/RateLimitReset' content: application/json: schema: type: object required: - addedCount - personIds properties: addedCount: type: integer personIds: type: array items: type: string description: The new people's ids. example: addedCount: 2 personIds: - 6a1f0c2b9d4e8a7f3c5b2e22 - 6a1f0c2b9d4e8a7f3c5b2e23 '429': $ref: '#/components/responses/RateLimited' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/ServerError' security: - apiKey: [] components: headers: RequestId: description: The request's id. Quote it when you write to support. schema: type: string example: req_6a1f0c2b9d4e8a7f3c5b2e10 ChargedUsd: description: What this call cost, in US dollars as an exact six-decimal string. schema: type: string example: '0.000500' BalanceUsd: description: >- The organization's balance after this call, in US dollars as an exact six-decimal string. schema: type: string example: '9.999500' RateLimitLimit: description: >- The calls allowed in the window of the route's limit with the fewest calls left. schema: type: integer example: 20 RateLimitRemaining: description: The calls left in that window. schema: type: integer example: 19 RateLimitReset: description: Seconds until that window resets. schema: type: integer example: 42 RetryAfter: description: Seconds to wait before calling again. schema: type: integer example: 42 responses: RateLimited: description: >- Too many calls. Wait the seconds in Retry-After, then call again. The body is empty. headers: Retry-After: $ref: '#/components/headers/RetryAfter' X-Request-Id: $ref: '#/components/headers/RequestId' RateLimit-Limit: $ref: '#/components/headers/RateLimitLimit' RateLimit-Remaining: $ref: '#/components/headers/RateLimitRemaining' RateLimit-Reset: $ref: '#/components/headers/RateLimitReset' Error: description: The request was refused. The body names the reason in `error.code`. headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/json: schema: $ref: '#/components/schemas/Error' ServerError: description: >- Something failed on our side and nothing was charged. Retry with backoff; quote X-Request-Id if it persists. The body is empty. headers: X-Request-Id: $ref: '#/components/headers/RequestId' schemas: Error: type: object required: - error properties: error: type: object required: - code - message - doc_url properties: code: type: string description: >- Stable and machine-readable: branch on it. It never changes meaning. message: type: string description: >- A human-readable explanation for logs. It may be reworded at any time. param: type: string description: The request field the error is about, when there is one. doc_url: type: string description: The code's entry in the errors reference. request_id: type: string description: >- The request's id, as in the X-Request-Id header. Quote it to support. example: error: code: insufficient_balance message: Your balance cannot cover this call. Add funds and try again. doc_url: https://docs.outbound.dev/errors#insufficient_balance request_id: req_6a1f0c2b9d4e8a7f3c5b2e10 securitySchemes: apiKey: type: http scheme: bearer description: >- An API key from the console, starting `ob_live_`, sent as `Authorization: Bearer `. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.