generation

Record an accepted completion

Report that the user accepted an autocomplete suggestion. context must be exactly the {query, completion} object the completion hash was computed from — extra keys fail the hash check.

post/api/v1/complete/{completion_hash}/accept

Request

  • Base URL: https://api.sapling.ai
  • URL: https://api.sapling.ai/api/v1/complete/{completion_hash}/accept
  • Auth: one of:
    • HTTP bearer
    • none

Path parameters

completion_hashstring uuid required

The hash returned by /api/v1/complete.

Request body

keystring

Sapling API key. Required when no "Authorization: Bearer <key>" header is sent; when both are sent, the body key takes precedence over the header.

return_usageboolean

When true, a successful JSON-object response additionally carries "usage": {"characters": <n>} — the billable character count this request submitted (0 for unbilled requests; the 2.5x adjustment for logographic languages is included, so CJK requests report more than their raw length). Repeat texts inside the billing deduplication window are still counted here even though they are not re-charged, so the number is an upper bound on the final charge. Responses whose body is not a JSON object (e.g. bare-array response formats) cannot carry the field. An existing usage field (such as account/status or completion token usage) is preserved unchanged.

session_idstring

Optional session identifier used to group feedback events.

Response

Recorded.

result'success'

Changes

No recorded changes to this operation across all 1 revision of this API.