# Deploy Hooks

*Deploy hooks* enable you to trigger an on-demand deploy of your Render service with a single HTTP request. Use deploy hooks with:

- CI/CD environments like GitHub Actions ([see an example](#using-with-github-actions))
- [Image-backed services](#deploying-from-an-image-registry) (to trigger a deploy when a new image is available)
- Headless CMS systems like [Contentful](https://www.contentful.com/developers/docs/concepts/webhooks/) (to trigger a deploy when content changes)

> *Looking for webhooks?* See [this article](webhooks).

## Triggering a deploy

Each service has a secret *deploy hook URL*, available from its *Settings* tab in the [Render Dashboard][dboard]:

[img]

> *Your deploy hook URL is a secret!*
>
> Provide the URL only to people and systems you trust to trigger deploys. If you believe a deploy hook URL has been compromised, replace it by clicking *Regenerate Hook*.

To trigger a deploy, send a basic `GET` or `POST` request to your service's deploy hook URL—no special headers required.

```bash
curl https://api.render.com/deploy/srv-xyz…
```

## Deploying from an image registry

[Image-backed services](deploying-an-image) on Render pull and deploy a prebuilt Docker image from an external registry. These services do _not_ automatically redeploy if a new image is pushed to the registry. You can use a deploy hook to trigger a deploy whenever an updated image is available.

To deploy a specific tag or digest, append the `imgURL` query parameter to your deploy hook URL:

```bash