Skip to main content

Discover JML trigger-filter attribute keys​

Returns the identity attribute keys observed on the given connections' identities in the graph — the same data.attributes.* a lifecycle data input surfaces to a running workflow. This is a discovery endpoint over observed data, not a curated catalogue: attributes vary per source, so a fixed list would be wrong for every org. Each returned key is directly usable as a filters[].attr value on a JMLTrigger.

Query Parameters
  • source_connections string[] required

    Connection IDs to sample attribute keys from. Repeated parameter, e.g. ?source_connections=a&source_connections=b.

Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
Responses

Attribute catalogue

Schema
  • meta object
  • pagination object
  • limit integer
  • offset integer
  • total_count int64
  • cursor_pagination object

    Cursors are opaque. Follow the tokens the server returns; never construct, parse or modify one.

  • limit integer
  • next_cursor string

    Opaque token addressing the next page. Absent on the last page.

  • prev_cursor string

    Opaque token addressing the previous page. Absent on the first page.

  • last_cursor string

    Opaque token addressing the final page directly, so a client can jump to the end without a total count.

  • total_count int64

    Total number of matching items. Returned on the FIRST page only; clients cache it for the remainder of the walk.

  • errors object[]
  • httpcode integer
  • message string
  • code string

    Machine-readable reason, present only for errors that define one. Values today: unserved_org_region (the organization is homed in a region this deployment does not serve), wrong_region (the request must be sent to the organization's home region), region_route_missing (this instance has no route to the organization's home region).

  • result object
  • attributes string[]