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

# Credential Types

Credential types are used to link a [Credential Schema](/latest/guides/credential-schemas.md) to an Organisation and define the visual appearance for a credential issued by that organisation. The credential type is used in the Meeco Portal and Meeco Wallet to give a credential of that particular schema and that particlar organisation its unique look and feel.

## Prerequisites

* [Credential Schema](/latest/guides/credential-schemas.md)

## Who can use this?

Credential types are managed by an organisation administrator.

## Create Credential Type

Creation of a credential type.

**Endpoint**

```bash
POST /credential_types
```

**Request**

* Name – name of the credential type
* Credential Schema - credential schema this type is applicable for
* Style
  * Text Colour
  * Background Colour – Background colour for the credential (CSS styles supported)
  * Logo – Logo displayed in the top left corner of the credential

**Responses**

The credential type object that is created.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meeco.me/latest/guides/credential-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.