> ## Documentation Index > Fetch the complete documentation index at: https://docs.api.tamtam.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get contacts > Read contacts you already hold, by id: name, current job title and employer, location, LinkedIn URL, and the contact's verified email and phone where Tamtam has them. Repeat `contact_id` once per contact, up to 100 per call. Ids come from anywhere this API hands you a contact — a [contacts list](/api-reference/contacts-lists/list-contacts-list-contacts), a [contact search](/api-reference/contact-searches/get-contact-search), or a [people search](/api-reference/people-search/search-people). An id naming no contact in your account is left out of the response rather than failing the call, so a batch never fails as a whole; match results back by `contact_id`. Free: this reads what you already own and enriches nothing. ## OpenAPI ````yaml /reference/openapi.yaml get /v2/contacts openapi: 3.1.0 info: title: Tamtam Public API version: 2.0.0 servers: - url: https://api.tamtam.ai/api security: [] paths: /v2/contacts: get: tags: - Contacts summary: Get contacts description: >- Read contacts you already hold, by id: name, current job title and employer, location, LinkedIn URL, and the contact's verified email and phone where Tamtam has them. Repeat `contact_id` once per contact, up to 100 per call. Ids come from anywhere this API hands you a contact — a [contacts list](/api-reference/contacts-lists/list-contacts-list-contacts), a [contact search](/api-reference/contact-searches/get-contact-search), or a [people search](/api-reference/people-search/search-people). An id naming no contact in your account is left out of the response rather than failing the call, so a batch never fails as a whole; match results back by `contact_id`. Free: this reads what you already own and enriches nothing. operationId: get-contacts parameters: - description: >- Repeatable. The contacts to read, up to 100 per call. Take the ids from a contacts list, a contact search or a people search. explode: false in: query name: contact_id required: true schema: description: >- Repeatable. The contacts to read, up to 100 per call. Take the ids from a contacts list, a contact search or a people search. items: type: string type: - array - 'null' responses: '200': content: application/json: schema: $ref: '#/components/schemas/GetContactsV2OutputBody' description: OK default: content: application/problem+json: schema: $ref: '#/components/schemas/ErrorModel' description: Error security: - apikeyAuth: [] - bearerAuth: [] components: schemas: GetContactsV2OutputBody: additionalProperties: false properties: contacts: description: >- One entry per id that resolved, in no guaranteed order. An id naming no contact in this account is simply absent — read contact_id to match them back. items: $ref: '#/components/schemas/EnrichedContact' type: - array - 'null' required: - contacts type: object ErrorModel: additionalProperties: false properties: detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object EnrichedContact: additionalProperties: false properties: company_linkedin_id: description: Current company LinkedIn ID examples: - '104924588' type: string company_linkedin_slug: description: Current company LinkedIn slug examples: - tamtam-ai type: string company_name: description: Current company name examples: - TAMTAM type: string contact_id: description: Contact UUID examples: - b3c6f5e2-1234-4abc-9def-0123456789ab type: string email: description: >- Contact email address. Verified addresses only: this field is one scalar with no confidence flag, so a guessed pattern would have the API asserting an address nobody stood behind. Absent when Tamtam holds none. examples: - elliot.alderson@tamtam.ai type: string first_name: description: Contact first name examples: - Elliot type: string job_title: description: Current job title examples: - Head of Sales type: string last_name: description: Contact last name examples: - Alderson type: string linkedin_url: description: LinkedIn profile URL examples: - https://www.linkedin.com/in/elliot-alderson type: string location: description: Contact location examples: - Paris, France type: string phone: description: >- Contact phone number. When several are held, this is the one the provider stood behind; otherwise the most recently collected. Absent when Tamtam holds none. examples: - '+33639981234' type: string type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object securitySchemes: apikeyAuth: description: Account API key passed in the Authorization header in: header name: Authorization type: apiKey bearerAuth: description: Bearer JWT obtained via the OAuth 2.1 authorization flow scheme: bearer type: http ````