Upsert markdown by a stable UID whenever the source data changes. The UID is yours, so re-pushing the same document updates it rather than adding a duplicate, and re-pushing unchanged content costs nothing.
Request fields
connection_idintegerCONN_ID returned when you created the connection.uidstringa-z, 0-9, hyphen, underscore or dot. Re-using it updates that document rather than adding another.titlestringbodystring422: delete the post instead.Response fields
statusstringcreated, updated, or unchanged when the content matched what was already indexed.postobjectpost.uidstringpost.titlestringpost.chunk_countintegerpost.will_indexboolean409 rather than an upsert.post.created_attimestamppost.updated_attimestampA 201 means the post was created; an existing uid answers 200 with status of updated, or unchanged when the content already matched.
No polling step
Chunking and embedding happen inside the request, so once you have a 201 that content is already searchable by /context and /question.
For small ad-hoc notes you want back word for word rather than retrieved by meaning, use a namespace instead of a document.
Quotas
Standard custom-connection quotas apply: 1,000 posts and 100MB per connection, 100KB per post body, and up to 6 custom connections per API account within that account's ceiling of 10 connections.