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.
Input submission requires a wallet that can sign for an account allowed by the authored inputDocumentation Index
Fetch the complete documentation index at: https://docs.shodai.network/llms.txt
Use this file to discover all available pages before exploring further.
issuer. 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.API key. Send this value in the X-API-Key request header.
Agreement ID or deployed agreement address.
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.
{
"v": 27,
"r": "0x1111111111111111111111111111111111111111111111111111111111111111",
"s": "0x2222222222222222222222222222222222222222222222222222222222222222"
}
Created input record.
Deployed agreement address associated with this input.
Chain ID for the deployed agreement.
Input ID submitted to the agreement.
Encoded input payload retained by the API.
Business values submitted with the input.
Transaction hash for the input submission.
Input record creation timestamp.
Input record update timestamp.
Input submission status.
PENDING, MINED, FAILED Platform user ID associated with the submission, when available.
Block number for the mined input transaction, when available.
Error message when the input submission failed.