> ## Documentation Index > Fetch the complete documentation index at: https://docs.blujay.io/llms.txt > Use this file to discover all available pages before exploring further. # List saved vCards > Returns your workspace's saved contact cards, most recently updated first. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/vcards openapi: 3.1.0 info: title: Blujay API version: 1.0.0 description: >- The Blujay API lets you send and receive iMessage, RCS and SMS messages from your Blujay phone numbers, manage contacts, and receive real-time webhooks. Every response uses the same JSON envelope and carries a `trace_id` you can share with support. Authenticate with your workspace API key. servers: - url: https://api.blujay.io description: Production security: - PublicApiKey: [] tags: - name: Auth description: Check which workspace and credential a request is using. - name: Chats description: >- Direct and group conversations between your Blujay numbers and your contacts. - name: Messages description: Send, read, edit, unsend and retry messages. - name: Phone Numbers description: >- Your Blujay numbers, whether each can send right now, and their live sending limits. - name: Capability description: >- Check whether a phone number can be reached by iMessage, RCS or SMS before you send. - name: Contacts description: Create, find, update, tag, assign and opt out contacts. - name: vCards description: >- Saved contact cards that you can send in a message. Recipients get a native contact card over iMessage, SMS or RCS. - name: Team Members description: People in your workspace you can assign contacts to. - name: Workflows description: Enroll contacts in workflows you start manually. - name: Attachments description: >- Upload files once and reuse them in messages, or download files from messages. - name: Webhooks description: Subscribe to events, inspect delivery attempts and verify signatures. paths: /v1/vcards: get: tags: - vCards summary: List saved vCards description: >- Returns your workspace's saved contact cards, most recently updated first. operationId: listPublicVcards parameters: - $ref: '#/components/parameters/Cursor' - $ref: '#/components/parameters/Limit' responses: '200': description: Saved vCard list, most recently updated first. headers: X-Trace-ID: $ref: '#/components/headers/XTraceID' content: application/json: schema: allOf: - $ref: '#/components/schemas/SuccessEnvelope' - type: object required: - data properties: data: $ref: '#/components/schemas/PublicVcardList' security: - PublicApiKey: [] components: parameters: Cursor: name: cursor in: query description: >- The `next_cursor` value from the previous page. Leave it out to get the first page. schema: type: string Limit: name: limit in: query description: Maximum number of items to return. schema: type: integer minimum: 1 maximum: 100 default: 25 headers: XTraceID: description: >- Unique ID for this request. It matches `trace_id` in the body. Include it when you contact Blujay support. schema: $ref: '#/components/schemas/TraceId' schemas: SuccessEnvelope: type: object description: Wraps every successful response. The result is in `data`. required: - status - trace_id - timestamp properties: status: type: string enum: - success trace_id: $ref: '#/components/schemas/TraceId' timestamp: type: string examples: - '2026-10-14T17:01:00.000Z' format: date-time client_request_id: type: string description: >- Your `X-Request-ID` header value, echoed back when you send one. Not included on the send responses (`POST /v1/chats`, `POST /v1/chats/{chat_id}/messages`, `POST /v1/messages/{message_id}/retry`); keep your own mapping from your request ID to the returned message ID there. PublicVcardList: type: object required: - data - has_more - limit properties: data: type: array items: $ref: '#/components/schemas/PublicVcard' next_cursor: type: string examples: - AbC9xQ2nRk7vT1mZ has_more: type: boolean limit: type: integer examples: - 25 TraceId: type: string examples: - trc_8f2a1c0e4b7d pattern: ^trc_[A-Za-z0-9_-]+$ PublicVcard: type: object required: - id - first_name - last_name - company - title - phones - emails - website - has_photo - created_at - updated_at properties: id: $ref: '#/components/schemas/VcardId' first_name: type: string examples: - Sam last_name: type: - string - 'null' examples: - Lee company: type: - string - 'null' examples: - Northwind title: type: - string - 'null' examples: - Support Lead phones: type: array items: type: object required: - number - type properties: number: type: string examples: - '+15555550100' description: E.164 phone number. type: type: string enum: - mobile - work - home - main emails: type: array items: type: object required: - address - type properties: address: type: string examples: - sam@example.com format: email type: type: string enum: - work - home - other website: type: - string - 'null' examples: - https://example.com has_photo: type: boolean description: >- Whether the card has a photo. Read-only; card photos are managed in the Blujay app. created_at: type: string examples: - '2026-10-14T17:01:00.000Z' format: date-time updated_at: type: string examples: - '2026-10-14T17:01:00.000Z' format: date-time VcardId: type: string examples: - vcard_abc123 pattern: ^vcard_[A-Za-z0-9_-]+$ securitySchemes: PublicApiKey: type: http scheme: bearer bearerFormat: blu_... description: > Your workspace API key, sent as `Authorization: Bearer blu_...`. Workspace admins can find it in the Blujay app under **API**. An API key has full access to your workspace and works on every endpoint. There is no test mode: every key sends real messages and changes real data, so keep it secret and use it only from your server. Each API key can make 600 read requests and 120 write requests per minute, plus 60 attachment requests per minute. Over a limit you get `429 RATE_LIMIT_EXCEEDED` with `Retry-After`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.