> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback/passing-the-patchworks-signature-as-a-header-for-callback-requests.md).

# Passing the Patchworks signature as a header for callback requests

## Introduction

When a [callback](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback.md) is generated via the [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md), it includes a Patchworks signature - by default, this is defined as a URL parameter. However, some third-party systems do not accept URL parameters.&#x20;

In this case, the signature element should be removed from generated URLs and passed as a `patchworks-signature` request header instead. &#x20;

## The steps

{% stepper %}
{% step %}
**Generate a callback trigger**

Access the trigger shape and add a callback (or use an existing callback).
{% endstep %}

{% step %}
**Copy the callback URL**

Copy the callback URL, then paste it into your preferred editor. It will look something like this:

{% code overflow="wrap" %}

```
https://callbacks.wearepatchworks.com/api/v1/docsdemo/01jvgtcr9gr66t84wh2fg9kse37?patchworks_signature=fr80fg6e2g94jj908f1698htggrswgw6319ns6r194fh2nkekcht
```

{% endcode %}
{% endstep %}

{% step %}
**Save the Patchworks signature value from the callback URL**

Copy the signature value and paste it somewhere accessible - you'll need this value shortly. For example:

{% code overflow="wrap" %}

```
fr80fg6e2g94jj908f1698htggrswgw6319ns6r194fh2nkekcht
```

{% endcode %}
{% endstep %}

{% step %}
**Edit the callback URL**

Remove the entire URL parameter section of the URL (i.e. remove the `?patchworks_signature` element). The updated URL will look something like this:

{% code overflow="wrap" %}

```
https://callbacks.wearepatchworks.com/api/v1/docsdemo/01jvgtcr9gr66t84wh2fg9kse37
```

{% endcode %}
{% endstep %}

{% step %}
**Apply the updated URL in your callback requests & add a signature header**

Use the updated URL in your callback request AND add a `patchworks-signature` header. The value for this header will be the signature that you saved in step 3. For example:

<div align="left"><figure><img src="/files/sS66BUXkVclsKqwzXb0y" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
The header must be `patchworks-signature` NOT `patchworks_signature` .
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape/trigger-shape-callback/passing-the-patchworks-signature-as-a-header-for-callback-requests.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.
