Skip to main content
POST
cURL
Provide specId and either an existing proposalId, or a new proposalName with text or file. An existing proposalId takes precedence over file/text fields.
Replace the example ID with an actual completed specification ID. The HTTP 200 response contains success, vettedProposal, and proposal. The assessment’s _id is used to retrieve it later.

Billing behavior

This operation charges 100 credits before later proposal validation and analysis. Check the specification, proposal ID, name, and content before calling it. There is no documented idempotency key, async mode, or automatic refund guarantee for validation/analysis failures. Check existing assessments before retrying a request whose outcome is uncertain. Insufficient credits returns 402. Input or ID validation can return 400; a missing proposal can return 404. Read the proposal workflow for assessment fields.

Authorizations

Authorization
string
header
required

Use a pre.dev API key from https://pre.dev/projects/key.

Body

specId
string
required

24-character record ID.

Pattern: ^[a-fA-F0-9]{24}$
proposalId
string
required

Existing proposal ID. When supplied, file, text, and proposalName are ignored.

Pattern: ^[a-fA-F0-9]{24}$
proposalName
string
Minimum string length: 1
text
string
Minimum string length: 1
file
file

New proposal file, at most 20 MiB, with a supported MIME type.

Response

Assessment and proposal.

success
boolean
required
vettedProposal
object | null
required
proposal
object
required

Stored proposal. Additional metadata can be present.