# Integrating CloudSign

> CloudSign (GMO Cloud) is the dominant Japanese e-signature provider.

**Auth:** OAuth 2.0 · **Partner program:** not required · **Setup time:** about 20 minutes · **Last verified:** 2026-05-21

CloudSign (GMO Cloud) is the dominant Japanese e-signature provider.

## Auth model

OAuth 2.0 Authorization Code grant.

## Prerequisites

1. CloudSign account at [cloudsign.jp](https://www.cloudsign.jp).
2. Register an OAuth application through CloudSign's developer console.
3. Add `<base-url>/auth/docsign/cloudsign/callback` to the redirect URIs.

Set the client credentials as the adapter's config — on the platform's page in
the admin UI (`/platforms/docsign/cloudsign`), or:

```bash
curl -X POST "$INTEGRATION_SERVER_URL/admin/platforms/docsign/cloudsign/enable" \
  -H "X-Admin-Secret: $ADMIN_SECRET" -H "Content-Type: application/json" \
  -d '{"config":{"clientId":"...","clientSecret":"...","redirectUri":"<base-url>/auth/docsign/cloudsign/callback"}}'
```

These are adapter settings, not environment variables: nothing reads a
`CLOUDSIGN_CLIENT_ID` from `.env`. See
[OAuth adapter credentials](https://docs.opensteward.dev/environment/environment-variables/#oauth-adapter-credentials).

## API documentation language

CloudSign's developer documentation is primarily Japanese. The adapter uses best-known endpoint paths; verify in `apps/integration-server/src/verticals/docsign/adapters/cloudsign/constants.ts` against your account's developer portal.

## Webhooks

HMAC-SHA256 in `X-CloudSign-Signature` (hex).

## Refused fields

- Document content
- Signature images
