cURL
Using Agreements
Submit input with permit
Submits a signed input to a deployed agreement. The input ID and values must match an input defined by the agreement JSON, and the signer must be allowed by that input.
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
Canonical API-key credential. Send X-API-Key: cns_pk_..., or Authorization: Bearer cns_pk_... only as an API-key compatibility alias.
Path Parameters
Agreement ID or deployed agreement address.
Body
application/json
Signed input submission for a deployed agreement.
Input ID defined in the agreement JSON.
Business values submitted for this input.
Wallet address that signed the EIP-712 input permit.
Unix timestamp in seconds when the input permit expires.
EIP-712 signature parts.
Example: