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

# Profiles

Organization profiles are used to provide more context for an Issuer DID. Details about the issuer such as name and logo can be added using a organization profile. These details will be included in credentials that are issued by the DID.

## Create profile

The `did` and `name` fields are required to create a new Profile.

{% openapi src="<https://swagger-api.truvera.io/openapi.yaml>" path="/profiles" method="post" %}
<https://swagger-api.truvera.io/openapi.yaml>
{% endopenapi %}

## Get profile

When a DID is provided in the path, the API will retrieve the profile associated with that DID.

{% openapi src="<https://swagger-api.truvera.io/openapi.yaml>" path="/profiles/{did}" method="get" %}
<https://swagger-api.truvera.io/openapi.yaml>
{% endopenapi %}

## List profiles

Return a list of all profiles that your user account controls.

{% openapi src="<https://swagger-api.truvera.io/openapi.yaml>" path="/profiles" method="get" %}
<https://swagger-api.truvera.io/openapi.yaml>
{% endopenapi %}

## Update profile

The update profile operation means that you can update the details of the profile. To do so, you need to provide a different value for **at least** one of `name`, `description` or `logo`.

{% openapi src="<https://swagger-api.truvera.io/openapi.yaml>" path="/profiles/{did}" method="patch" %}
<https://swagger-api.truvera.io/openapi.yaml>
{% endopenapi %}

## Delete profile

Deletes a profile from our platform. It does NOT delete the associated DID, nor revoke the credentials issued for the profile.

{% openapi src="<https://swagger-api.truvera.io/openapi.yaml>" path="/profiles/{did}" method="delete" %}
<https://swagger-api.truvera.io/openapi.yaml>
{% endopenapi %}


---

# 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.truvera.io/truvera-api/profiles.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.
