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

# Get Secret Details (Old)

> Pre-v1.3 Syteca ACB endpoint for retrieving secret credentials with the Access Token in the JSON request body. Superseded by GET /api/secrets/{id}/password but still supported for backward compatibility.

Retrieves a secret's credentials (login, password, SSH key) using the **pre-v1.3 authentication model** — the Access Token goes in the JSON request body, not the `Authorization` header. Still supported for backward compatibility, but **new consumers should use** [`GET /api/secrets/{id}/password`](/docs/api/acb/endpoints/get-secret-credentials) instead.

<Warning>
  This endpoint passes the Access Token in the **request body** rather than a header. This is the original ACB authentication pattern preserved for backward compatibility — the response shape and field set are otherwise equivalent to the new endpoint.
</Warning>

<Note>
  For ACB deployments updated from a version prior to 1.2, switch to the `https://{hostname}/EkranACB` server in the Playground.
</Note>

### Where to get the Secret ID

The Secret ID is visible on the **Automation tab** of the Edit Secret page — see [Find the Secret ID](/docs/api/acb/secret-permissions#find-the-secret-id-and-folder-id).

### Permissions required

The user owning the Access Token must have at least **PAM User** role on the secret.

### Errors

See [Status codes](/docs/api/acb/api-reference#status-codes). Common errors:

* **401 Unauthorized** — expired or invalid Access Token.
* **403 Forbidden** — user lacks the PAM User role (or higher) on this secret.
* **404 Not Found** — secret doesn't exist or isn't visible to the authenticated user.

## Related

<CardGroup cols={2}>
  <Card title="Get secret credentials (new)" icon="key" href="/docs/api/acb/endpoints/get-secret-credentials">The v1.3+ equivalent with header-based auth.</Card>
  <Card title="Get access token" icon="key-round" href="/docs/api/acb/endpoints/get-access-token">How to obtain the Access Token this endpoint requires.</Card>
  <Card title="API reference" icon="square-code" href="/docs/api/acb/api-reference">Status codes, rate limiting.</Card>
  <Card title="Secret permissions" icon="lock-keyhole" href="/docs/api/acb/secret-permissions">Role types and permission grants.</Card>
</CardGroup>


## OpenAPI

````yaml POST /get_secret_details
openapi: 3.0.3
info:
  title: Application Credentials Broker API
  description: >-
    API for managing secrets and folders in the Application Credentials Broker
    system
  version: 1.4.0
  contact:
    name: API Support
    email: support@example.com
servers:
  - url: https://your-syteca-host/SytecaACB
    description: On-premises Syteca ACB service (v1.2 or later)
    variables:
      hostname:
        default: your-syteca-host.example.com
        description: Your Syteca Application Server hostname
  - url: https://your-syteca-host/EkranACB
    description: Legacy URL prefix for ACB deployments updated from pre-v1.2
    variables:
      hostname:
        default: your-syteca-host.example.com
        description: Your Syteca Application Server hostname
security:
  - AccessTokenAuth: []
paths:
  /get_secret_details:
    post:
      tags:
        - Old Endpoints
      summary: Get secret credentials (pre-v1.3 endpoint)
      description: >-
        Pre-v1.3 endpoint for retrieving secret credentials. Superseded by GET
        /api/secrets/{id}/password but still supported for backward
        compatibility. Access Token goes in the JSON body, not a header.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/GetSecretDetailsRequest'
      responses:
        '200':
          description: Credentials returned successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetSecretDetailsResponse'
        '401':
          description: Expired or invalid Access Token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: User lacks at least PAM User role on this secret
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Secret not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security: []
components:
  schemas:
    GetSecretDetailsRequest:
      type: object
      required:
        - accessToken
        - secretId
      properties:
        accessToken:
          type: string
          description: Access Token returned by get_access_token.
        secretId:
          type: integer
          format: int32
          minimum: 1
          description: >-
            The ID of the secret. Find it on the Automation tab of the Edit
            Secret page.
    GetSecretDetailsResponse:
      type: object
      properties:
        login:
          type: string
          description: Login name.
        password:
          type: string
          description: Password value.
        ssh_key:
          $ref: '#/components/schemas/SshKey'
          description: SSH key data (UnixAccountSSH only).
        domain:
          type: string
          description: AD domain (ADAccount only).
        server:
          type: string
          description: Server hostname (Unix/MSSQL accounts).
        computer_name:
          type: string
          description: Target computer (WindowsAccount only).
        url:
          type: string
          description: Application URL (WebAccount only).
    ErrorResponse:
      type: object
      properties:
        status:
          type: integer
          description: HTTP status code
        message:
          type: string
          description: Error message
      required:
        - status
        - message
    SshKey:
      type: object
      properties:
        private_key:
          type: string
          description: SSH private key
        pass_phrase:
          type: string
          description: Passphrase for the private key
      required:
        - private_key
  securitySchemes:
    AccessTokenAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Access token for authentication

````