Get document clauses as recorded in the document, with playbook and authorship

Gets the clauses as the document's own metadata records them, together with the playbook id
stored at check-in and the attachment's authorship. The clause library is NOT consulted: no
original clause entry is looked up, no {LibraryText} is returned, and no clause is dropped
for lacking library text — so this response includes clauses that {{attachmentId}/clauses}
omits. For the same reason a markup clause, which has no library entry to resolve an id from,
comes back with an empty {ClauseId}. Use {{attachmentId}/clauses} for the
library-reconciled view.
Returns 400 when attachmentId is missing. An unknown id returns 404 only where the
underlying fetch answers with nothing; on the Conga Platform the document provider raises an error
for an unknown id and that surfaces as 500 instead. An attachment that exists but carries no clause
metadata returns 200 with an empty clause list.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string | null
required

The attachment identifier

Headers
string
required
Defaults to RLP
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

400

Bad Request

401

Unauthorized

404

Not Found

500

Server Error

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json