> ## Documentation Index > Fetch the complete documentation index at: https://timelines.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get WABA Account > Get details of a specific WABA account. ## OpenAPI ````yaml get /waba/accounts/{account_id} openapi: 3.0.3 info: title: Timelines Public API description: > # Timelines Public API _Some API calls may utilize message sending quota or be subject to message sending rate limits as described below._ ### Credit Utilization - Sending a message via API consumes 1 credit from message sending quota. - Sending a message with non-empty text and attachment consumes 2 credits from message sending quota. - If a message cannot be sent (invalid or not connected to WhatsApp number, WhatsApp server error), message sending quota will be restored (usually within a couple of hours). ### Message sending rate - Messages will be sent with random delay of about 2 seconds between each two messages (to avoid WhatsApp spam detection mechanisms). Contact support@timelines.ai if you want to modify delay for your workspace (available on Business plan only). - If you exceed message sending frequency, messages be queued and sent out with delay. Each queued message will consume a message sending credit, so the number of queued messages cannot exceed the available quota. ### Authorization: - Copy API token from [Public API page](https://app.timelines.ai/integrations/api/) in your TimelinesAI account. - Put the token in *Authorization* header of request as follows: ``` Authorization: Bearer 4d2d0239-e28c-4f4a-8a4d-3a3ca40056b8 ``` ### Message formatting: - use "\n" for line breaks ### Input strings: - String fields must not contain the NUL character (U+0000). version: 1.3.0 servers: - url: https://app.timelines.ai/integrations/api description: Public API root URL security: - bearerAuth: [] paths: /waba/accounts/{account_id}: get: summary: Get details of a WABA account description: > Returns the full detail of a single WABA account by its internal `id`, including the Meta cross-reference handles for looking the account up in Meta's Business Manager. parameters: - $ref: '#/components/parameters/waba_account_id' responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/WabaAccountDetailResponse' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/AccessDenied' '404': $ref: '#/components/responses/NotFound' components: parameters: waba_account_id: description: >- an internal id of the WABA account (the only value used to address this account) in: path name: account_id schema: type: integer required: true example: 4021 schemas: WabaAccountDetailResponse: type: object required: - status - data properties: status: type: string example: ok enum: - ok - error data: $ref: '#/components/schemas/WabaAccountDetail' WabaAccountDetail: type: object required: - id - status - owner_name - owner_email - connected_on - meta_phone_id - display_phone_number properties: id: type: integer example: 4021 description: Internal account id, the only value used to address this account. status: type: string example: active description: > Lifecycle status of the WABA account: `active`, `disabled`, or `disconnected`. owner_name: example: John Doe type: string owner_email: type: string example: john.doe@acme.com connected_on: type: string example: 2026-05-18 15:19:23 +0100 meta_phone_id: type: string example: '109876543210987' meta_waba_id: type: string example: '210987654321098' display_phone_number: type: string example: +1 555 010 1234 waba_profile: $ref: '#/components/schemas/WabaProfileInfo' _note: type: string description: > id is the internal account id and is the only value used to address this account. meta_phone_id and meta_waba_id are display-only cross-reference fields. ErrorResponse: required: - message - status type: object properties: message: type: string status: type: string example: error enum: - ok - error error_code: type: string description: >- Stable, machine-readable error code. Use this for branching in client integrations. example: validation_error enum: - missing_credentials - invalid_token - member_not_found - permission_denied - insufficient_scope - plan_feature_unavailable - quota_exceeded - rate_limit_exceeded - validation_error - not_found - account_inactive - template_not_approved - template_wrong_waba - template_variables_mismatch - service_window_closed - not_supported - internal_error errors: type: array description: >- Per-field validation diagnostics for request-schema (body/params) validation failures. Present only when the request failed schema validation; absent on business-rule `validation_error` rejections (which carry `message` and `error_code` only) and on auth/authorization/quota errors. items: $ref: '#/components/schemas/ValidationError' WabaProfileInfo: type: object required: - meta_waba_id - name - account_ids properties: meta_waba_id: type: string example: '210987654321098' name: type: string example: Initech Support account_ids: type: array items: type: integer example: - 4021 - 4022 ValidationError: type: object required: - fields - msg properties: fields: type: array items: type: string description: >- Path of the offending field, as a list of keys/indexes from the request root. example: - url msg: type: string description: Validator message for that field. example: must be a valid http(s) URL responses: BadRequestError: description: Invalid parameters content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' UnauthorizedError: description: Access token is missing or invalid AccessDenied: description: Access denied content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Specified entities not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer ````