> For the complete documentation index, see [llms.txt](https://docs.shadowcipher.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadowcipher.in/endpoints/signature-types.md).

# List signature types

List the signature types assigned to your client.

<mark style="color:green;">`GET`</mark> `/api/oauth/signatureTypes`

Returns the signature types assigned to the calling client. These IDs are the allowed values for `signature_type` in [Start a signing transaction](https://docs.shadowcipher.in/endpoints/initiate-transaction.md).

## Headers

| Header          | Value                   |
| --------------- | ----------------------- |
| `Authorization` | `Bearer <access_token>` |

## Example

```bash
curl https://app.shadowcipher.in/api/oauth/signatureTypes \
  -H "Authorization: Bearer $TOKEN"
```

## Responses

{% tabs %}
{% tab title="200 OK" %}

```json
{
  "signature_types": [
    { "id": 1, "name": "ImageSign" },
    { "id": 2, "name": "StandardSignature" }
  ]
}
```

| Field                    | Type    | Description                    |
| ------------------------ | ------- | ------------------------------ |
| `signature_types[].id`   | integer | Pass this in `signature_type`. |
| `signature_types[].name` | string  | Name of the signature type.    |
| {% endtab %}             |         |                                |

{% tab title="401" %}
Missing, invalid or expired access token.
{% endtab %}

{% tab title="403" %}
The token lacks the `txn:initiate` scope or the client is inactive.
{% endtab %}

{% tab title="429" %}
Rate limit exceeded. See [Rate limits](https://docs.shadowcipher.in/reference/rate-limits.md).
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Signature types are assigned to each client by the BSA team. Passing an ID that isn't assigned to you returns `403 forbidden`.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadowcipher.in/endpoints/signature-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
