---
title: "Check a registry secret with its registry"
url: https://docs.corefinity.com/api/reference/deployments/check-environment-registry-secret
type: endpoint
last_updated: 2026-11-13
feature: registry-secrets
related:
  - https://docs.corefinity.com/guides/sites/code-and-deployments/registry-secrets.md
---
# Check a registry secret with its registry

Asks the registry once, with the saved credential, whether it accepts it. `verified` says so, `message` says
what the registry answered, and an accepted credential gets its `verified_at`. A credential the registry
refuses, or a registry that cannot be reached, is still a `200` with `verified` false.

```http
POST /api/corestack/environments/{environment}/deploy-secrets/{secret}/verify
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 20 a minute
- Try it in the console: off. It has not been cleared for the console. Copy the request and run it yourself when you are sure.

## Path parameters

- `environment` (integer, required): The id of a CoreStack Enterprise environment. Not the same number as a site row id.
- `secret` (integer, required): The id of a registry secret of this environment, as the list answers it. Digits only.

## Request

### curl

```bash
curl -X POST https://manage.corefinity.com/api/corestack/environments/1311/deploy-secrets/318/verify \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json"
```

### PHP

```php
use Illuminate\Support\Facades\Http;

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->post('https://manage.corefinity.com/api/corestack/environments/1311/deploy-secrets/318/verify');

$data = $response->json();
```

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/corestack/environments/1311/deploy-secrets/318/verify', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
  },
});

// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);
```

### Python

```python
import os
import requests

res = requests.post(
    "https://manage.corefinity.com/api/corestack/environments/1311/deploy-secrets/318/verify",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
)

data = res.json() if res.content else None
```

## Responses

### 200 What the registry answered, and the credential as it is now.

```json
{
  "data": {
    "auth_type": "bearer",
    "id": 318,
    "kind": "composer",
    "label": "Private packages",
    "last4": "oken",
    "last_used_at": null,
    "registry": "repo.example.com",
    "scope": "",
    "verified_at": "2026-11-09T10:42:07Z"
  },
  "message": "The registry accepted these credentials.",
  "verified": true
}
```

### 401 No token, or a token that is not valid.

```json
{
  "message": "Unauthenticated."
}
```

### 403 The token lacks the `write` scope (`scope_required`), your company requires two-factor authentication and you have not set it up, or your role lacks the Edit Environment Deployment Pipeline permission (`forbidden`, with `permission`).

```json
{
  "code": "company_unavailable",
  "message": "Your company is unavailable.",
  "reason": "company_unavailable"
}
```

### 404 The id does not exist, or it is something you cannot see. Both answer the same body.

```json
{
  "message": "Not found."
}
```

### 422 The environment belongs to a CoreStack or CoreCluster site (`invalid` on `environment`). Use the site's registry secrets instead.

```json
{
  "code": "invalid",
  "errors": {
    "environment": [
      "This is a CoreStack or CoreCluster environment: name it by its site_id."
    ]
  },
  "field": "environment",
  "message": "This is a CoreStack or CoreCluster environment: name it by its site_id.",
  "reason": "invalid"
}
```

### 429 Too many requests (`rate_limited`). Wait for the number of seconds in `Retry-After`, which `retry_after_seconds` repeats.

```json
{
  "code": "rate_limited",
  "message": "Too many requests. Try again in 60 seconds.",
  "reason": "rate_limited",
  "retry_after_seconds": 60
}
```

## If it is refused

| Status | Reason | What to do |
|---|---|---|
| 401 |  | Send a valid token as `Authorization: Bearer <token>`. |
| 403 | `company_unavailable` | Your company is unavailable. |
| 403 | `forbidden` | The person is not allowed to do this. |
| 403 | `scope_required` | Use a token with the scope named in `scope`. |
| 403 | `two_factor_required` | Turn on two-factor on your account, then send again. |
| 404 |  | Check the id. You see only what your account can reach. |
| 422 | `invalid` | Fix the field named in `field`; `errors` says why. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |

## The same task elsewhere

- Guide: [Private registries](https://docs.corefinity.com/guides/sites/code-and-deployments/registry-secrets.md)
