# credentials_orgs_users_retrieve_2

API View for managing individual credentials.

This endpoint allows retrieving, updating, and deleting specific credentials
identified by their entity_id.

Path Parameters:
    org (str): The organization/tenant identifier
    user_id (str): The user ID making the request
    entity_id (str): The credential entity ID

Methods:
    GET: Retrieve a specific credential
    PUT: Update a specific credential
    DELETE: Delete a specific credential

PUT Request Body:
    A JSON object containing credential details to update:
    - name (str, optional): Credential name
    - description (str, optional): Credential description
    - credential_type (str, optional): Type of credential
    - html_template (str, optional): HTML template for credential rendering
    - css_template (str, optional): CSS template for credential styling
    - icon_image (str, optional): URL to credential icon
    - background_image (str, optional): URL to credential background
    - thumbnail_image (str, optional): URL to credential thumbnail
    - criteria_url (str, optional): URL to credential criteria
    - criteria_text (str, optional): Text description of credential criteria
    - issuing_signal (str, optional): Signal that triggers credential issuance

Returns:
    GET: A JSON response containing:
        {
            "status": {"success": true, "description": "Ok"},
            "result": {credential object}
        }

    PUT: A JSON response containing:
        {
            "status": {"success": true, "description": "Updated"},
            "result": {credential object}
        }

    DELETE: No content (204)

Error Responses:
    400 Bad Request: If the request data is invalid
    401 Unauthorized: If the user is not authenticated
    403 Forbidden: If the user does not have permission to access this resource
    404 Not Found: If the credential doesn't exist
    500 Internal Server Error: If an unexpected error occurs

Access Control:
    - Requires CredentialAssignmentPermission
    - Users can only manage credentials they have permission to access

Endpoint: GET /api/credentials/orgs/{org}/users/{user_id}/{entity_id}
Version: 3.59.0-ai-plus
Security: PlatformApiKeyAuthentication

## Path parameters:

  - `entity_id` (string, required)

  - `org` (string, required)

  - `user_id` (string, required)

## Response 200 fields (application/json):

  - `entityId` (string, required)

  - `name` (string, required)

  - `name_override` (string,null)

  - `description` (string,null)

  - `criteriaUrl` (string, required)

  - `criteriaNarrative` (string, required)

  - `createdAt` (string, required)

  - `iconImage` (string, required)

  - `icon_image_id` (integer, required)

  - `backgroundImage` (string, required)

  - `background_image_id` (integer, required)

  - `thumbnailImage` (string, required)

  - `thumbnail_image_id` (integer, required)

  - `catalog_items` (array, required)

  - `courses` (array, required)

  - `programs` (string, required)

  - `issuerDetails` (object, required)

  - `html_template` (string,null)

  - `css_template` (string,null)

  - `metadata` (any,null)

  - `credentialType` (string, required)

  - `expires` (object, required)

  - `tags` (any,null)

  - `signatories` (array, required)

  - `signal` (string, required)

  - `pathways` (array, required)