Skip to main content
POST
cURL
Input submission requires a wallet that can sign for an account allowed by the authored input issuer. Use the deployed agreement record’s chainId and contract address when creating the EIP-712 signature. In SDK integrations, use submitAgreementInputWithPermit(...) to sign and submit in one flow. Generated API examples document request and response shape; choose input IDs and values from the deployed agreement JSON.

Authorizations

X-API-Key
string
header
default:YOUR_API_KEY
required

Canonical API-key credential. Send X-API-Key: cns_pk_..., or Authorization: Bearer cns_pk_... only as an API-key compatibility alias.

Path Parameters

id
string
required

Agreement ID or deployed agreement address.

Body

application/json

Signed input submission for a deployed agreement.

inputId
string
required

Input ID defined in the agreement JSON.

values
object
required

Business values submitted for this input.

signer
string
required

Wallet address that signed the EIP-712 input permit.

deadline
integer
required

Unix timestamp in seconds when the input permit expires.

signature
object
required

EIP-712 signature parts.

Example:

Response

Created input record.

data
object
required
Example:
meta
object
required