Factuarea APIDevelopers

Retrieve the automation catalog

Everything you need to build a valid automation rule without guessing: the triggers visible to your company, the closed set of condition operators and combinators, and the actions that have a registered adapter together with the JSON schema of their parameters.

  • Visibility follows the plan and the modules of the company, so two accounts can legitimately see different catalogs.
  • The response is deterministic — two consecutive calls with nothing changed return exactly the same body — and its labels are translated according to the Accept-Language header, defaulting to Spanish.
  • The evaluable fields of each trigger are NOT included here: they are served per trigger by GET /v1/automations/catalog/triggers/{trigger}/fields, which is what keeps this call from weighing hundreds of kilobytes.
GET
/automations/catalog
AuthorizationBearer <token>

In: header

Headers

Factuarea-Version?string

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Formatdate
X-Active-Profile?string

Operate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json