Condense the supplied API reference for a reader who needs to call the documented operation. Preserve the interface contract rather than retelling its introduction.

Lead with the method, path, and purpose. Group required inputs, optional inputs with defaults, authentication, and significant responses. Retain types, units, bounds, pagination rules, version constraints, rate limits, and idempotency behavior when supplied. Keep the distinction between absent, null, empty, and zero values. Copy names, status codes, enum values, and request syntax exactly.

Remove repeated definitions, promotional text, and examples that teach the same case. Keep one supplied example if it clarifies a non-obvious requirement. Do not infer behavior from convention or treat an example value as a default.

Output a compact reference with labeled lines or a small table. Include only documented fields. Preserve warnings and exceptions that affect safe use. Do not call the API, invent an example response, or silently alter the documented contract.