Returns the cap associated to the ID
LeadConduit uses HTTP Basic Authentication
with the username API and your API key as the password.
For example: API:1f1b96c9150d8050e858c043d543bb4eadae0e6f'
ID of the cap to get 24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
OK
A cap counter keeps track of the number of leads counted against the cap. The counter has the same ID as the cap configuration saved with the flow. Most of the properties of the cap configuration are available on the cap counter, as a convenience.
The number duration_units for which the cap persists
x >= 11
The unit of time for which the cap persists
month, week, day, hour, minute The number of successful leads that will be accepted
1200
The type of this cap (LeadConduit may eventually support different types of caps)
volume ID of this cap
^[0-9a-fA-F]{24}$"5fd438f91f0d12766e2bfee5"
24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$Nested caps evaluated if rules for the parent cap pass
The number of successful leads during the current interval
Read-only time the cap interval ends
"2020-11-23T11:41:52Z"
The number of leads that failed because the cap was reached during the current interval
ID of the flow this cap belongs to
^[0-9a-fA-F]{24}$"5fd438f91f0d12766e2bfee5"
The human-readable name of the cap
"Monthly leads from TX"
ID of the source this cap belongs to
^[0-9a-fA-F]{24}$"5fd438f91f0d12766e2bfee5"
Read-only time the cap interval started
"2020-11-23T11:41:52Z"
ID of the step this cap belongs to
^[0-9a-zA-Z]{6}$"5fd438f91f0d12766e2bfee5"
The time zone in which cap resets
"America/New_York"
"2020-11-23T11:41:52Z"