Skip to main content
GET
/
v0
/
safe
/
config
Get Safe deployment configuration
curl --request GET \
  --url https://api.sumvin.com/v0/safe/config \
  --header 'x-sumvin-pat: <api-key>'
{
  "_links": {
    "self": {
      "href": "<string>",
      "method": "GET",
      "templated": false,
      "description": "<string>"
    }
  },
  "factory": "<string>",
  "factory_data": "<string>",
  "predicted_safe_address": "<string>",
  "entrypoint": "<string>",
  "chain_id": 123,
  "signer_contract_address": "<string>"
}

Authorizations

​
x-sumvin-pat
string
header
required

Personal access token issued to the Sumvin CLI. Send it in the x-sumvin-pat header to authenticate as the owning user.

Headers

​
x-juno-orgid
string | null

Tenant org ID for multi-tenant auth

​
x-sumvin-token
string | null
​
x-sumvin-pat
string | null
​
x-juno-jwt
string | null
​
X-Timestamp-Format
string

Controls how timestamp fields are serialized in JSON response bodies.

Default (header omitted or any other value): epoch milliseconds as integers. iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.

Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".

Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.

Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.

Example:

"iso8601"

Query Parameters

​
chain_id
integer
required

EVM chain ID the Safe will be deployed on.

Response

Safe deployment configuration retrieved.

​
_links
CommonLinks · object
required

HAL navigation links — self and a rpc link for submission.

​
factory
string
required

Address of the Safe factory contract. Pass this as the factory field of the UserOperation when deploying a Safe in the same bundle.

​
factory_data
string
required

ABI-encoded calldata that the factory will execute to deploy the Safe. Pass this as the factoryData field of the UserOperation.

​
predicted_safe_address
string
required

Deterministic address the Safe will deploy to (CREATE2). This address is usable as the UserOperation sender even before deployment.

​
entrypoint
string
required

Address of the ERC-4337 EntryPoint contract on this chain.

​
chain_id
integer
required

EVM chain ID this configuration applies to.

​
signer_contract_address
string | null

Address of the user's signer contract. Present when the Safe is configured to validate signatures produced by an agent signer; absent when the Safe is owned directly by an EOA (e.g. user-signed deploys).