> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Using Projects Endpoint in Esadax REST API
- URL: https://blog.esadax.com/en/using-projects-endpoint-in-esadax-rest-api-2/
- Published: 2025-07-04T00:00:00.000Z
- Updated: 2026-11-15T05:35:48.000Z
- Author: Esadax 
- Tags: #tr-platform-20-infrastructure-52-rest-api-projects, #en, #mdx-imported, Platform

To use the provided cURL commands effectively, follow these steps for each endpoint:

### Protection-Bypass PATCH Request

1. **Headers**: Include your Authorization token.
2. **Body**: Send the JSON object as the request body.

**Method**: Use PATCH with the following body:

```json
{
  "generate": {
    "secret": "your_secret_value"
  },
  "revoke": {
    "secret": "revoked_secret_value",
    "regenerate": true
  }
}

```

**URL**: Replace `SOME_STRING_VALUE` with your project ID or name.

```
https://api.esadax.com/v1/projects/{projectIdOrName}/protection-bypass?slug={slug}&teamId={teamId}

```

### Domain Verification POST Request

1. **Method**: Use POST without a body, only headers.
2. **Headers**: Include your Authorization token.

**URL**: Replace `prj_12HKQaOmR5t5Uy6vdcQsNIiZgHGB` with your project ID and `example.com` with your domain.

```
https://api.esadax.com/v9/projects/{projectId}/domains/{domain}/verify

```

### Handling Responses

- **Protection-Bypass**: Check for response codes to determine success or failure.
- **Domain Verification**: Parse the response object to check if verification was successful and handle any challenges or errors accordingly.

### Security Considerations

- Use HTTPS for all API calls.
- Handle secrets and tokens securely, avoiding logging of sensitive information.
- Implement rate limiting or retries with exponential backoff to manage API usage effectively.