> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useanima.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Post vaultcredentials use



## OpenAPI

````yaml /openapi.json post /vault/credentials/{id}/use
openapi: 3.1.1
info:
  title: Anima API
  version: 0.1.0
  description: >-
    The Anima API provides programmatic access to unified infrastructure for AI
    agents: create and manage agents; send and receive email; place phone calls
    and send/receive SMS and voice; store and retrieve vault credentials; manage
    agent identity; and configure webhooks for real-time events. Authenticate
    using a Bearer token or an API key passed via the X-API-Key header.
  contact:
    name: Anima Labs
    url: https://useanima.sh
    email: support@useanima.sh
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://api.useanima.sh/v1
    description: Production
security:
  - BearerAuth: []
  - ApiKeyAuth: []
tags:
  - name: Agents
    description: Create and manage AI agents with email and phone capabilities
  - name: Inboxes
    description: Manage email inboxes and their configurations
  - name: Messages
    description: Send, receive, and search email messages
  - name: Webhooks
    description: Register and manage webhook subscriptions for real-time events
  - name: Organizations
    description: Manage organizations and team settings
  - name: Domains
    description: Configure and verify custom email domains
  - name: Phone
    description: Manage phone numbers and SMS/voice capabilities
  - name: Invoices
    description: Track invoices, match receipts, and reconcile payments
  - name: Billing
    description: View usage, tiers, and billing information
  - name: Security
    description: Configure security policies and access controls
  - name: Vault
    description: Store and retrieve encrypted secrets
  - name: API Keys
    description: Create and manage API keys for programmatic access
paths:
  /vault/credentials/{id}/use:
    post:
      operationId: vault.use
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
            description: Credential ID to broker the call with
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                agentId:
                  type: string
                  description: Agent ID (optional when using an agent API key)
                method:
                  enum:
                    - GET
                    - POST
                    - PUT
                    - PATCH
                    - DELETE
                    - HEAD
                  type: string
                  description: HTTP method for the outbound call
                url:
                  type: string
                  format: uri
                  description: >-
                    Absolute https:// URL. Its host MUST be on the credential's
                    allowlist.
                headers:
                  type: object
                  additionalProperties:
                    type: string
                  description: >-
                    Extra request headers. Any Authorization / auth header is
                    ignored and replaced by the credential.
                body:
                  type: string
                  description: Raw request body (encode JSON yourself).
              required:
                - method
                - url
              description: >-
                Make an outbound HTTP call with the credential attached
                server-side. The plaintext secret is never returned — the agent
                only sees the upstream response.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: integer
                    description: Upstream HTTP status code
                  headers:
                    type: object
                    additionalProperties:
                      type: string
                    description: Upstream response headers
                  body:
                    type: string
                    description: Upstream response body (UTF-8, size-capped)
                  truncated:
                    type: boolean
                    description: >-
                      True if the response body exceeded the size cap and was
                      cut off
                required:
                  - status
                  - headers
                  - body
                  - truncated
                description: The upstream response, scrubbed of the injected credential.
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT Bearer token obtained from authentication. Pass as: Authorization:
        Bearer <token>
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'API key for programmatic access. Pass as: X-API-Key: <your-key>'

````