Google Cloud DLP compatibility
Use supported Google Cloud DLP v2 REST and gRPC contracts with ShinrAI.
The vendor contract limits what ShinrAI can return: types, confidence, media, sessions and jobs. Results can therefore be weaker than ShinrAI can deliver. For full quality, use the native PII API v2.
Endpoints
Use the vendor endpoint for an unchanged client. The same adapter also runs under a path prefix on the API host; ShinrAI extensions to the vendor format appear there first.
| API | Endpoint: change only this | Alternative on the API host |
|---|---|---|
| Google Cloud DLP | https://google.api.getshinrai.com | https://api.getshinrai.com/v1/google |
| Sandbox | https://google.api-sbx.getshinrai.com | https://api-sbx.getshinrai.com/v1/google |
This endpoint serves its own OpenAPI document: OpenAPI for this API.
Set up a Google-compatible client
Point your Google Cloud DLP client at https://google.api.getshinrai.com. Only the endpoint changes.
Authenticate with your ShinrAI key in the x-goog-api-key header or as a Bearer token. Supply exactly one method.
curl 'https://google.api.getshinrai.com/v2/projects/example/locations/eu/content:inspect' \
-H "x-goog-api-key: $SHINRAI_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"item":{"value":"Email emma@example.com"},"inspectConfig":{"includeQuote":true}}'Supported operations
| Area | Operations |
|---|---|
| Content | Inspect, de-identify, and re-identify content |
| Images | Redact supported image content |
| Discovery | List supported info types |
| Configuration | Create, get, update, list, and delete inspect templates, de-identify templates, and stored info types |
Compatibility boundaries
ShinrAI validates the pinned protobuf JSON contract and rejects unknown fields. Supported transformation types, conditions, dictionaries, KMS references, image sizes, and storage mappings depend on the deployment. This is Google DLP contract compatibility for documented operations, not service-wide feature parity.
Use the generated reference to inspect every path and method. gRPC clients use the same service contracts through the deployment's documented gRPC endpoint.