marketplace

Acquire Capability

Acquire one visible capability through its registered type executor.

The body is OPTIONAL and generic (TOS-4215): it carries the caller's answers to whatever inputs this object's acquire plan declared, keyed by input name. Nothing in this endpoint knows what any of those names mean :func:validate_acquire_inputs checks them against the plan's own declaration, and the resolver reads them. A type declaring no inputs is unaffected and a bodiless POST remains valid for it.

Why this stopped being a 204. The caller needs to be told WHICH thing they now hold and whether it actually works yet. A connection account exists the moment it is created and carries no credential, and reporting that as connected is the defect this ticket was opened over: the production Sentry detail page read "Connected", over an identity with zero connected accounts, because nothing on the wire could say otherwise.

post/api/marketplace/capabilities/{object_id}/acquire

Request

  • Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.thinqos.com/api/marketplace/capabilities/{object_id}/acquire
  • Auth: none declared

Path parameters

object_idstring uuid required

Headers

x-impersonate-identity-idstring nullable

Request body

inputsobject

Response

Successful Response

familystring required
held_object_idstring uuid required
statestring

Changes

No recorded changes to this operation across all 2 revisions of this API.