Sample - Twilio API
GET/2010-04-01/Accounts/{AccountSid}/Usage/Triggers.json

List usage triggers

Lists usage triggers belonging to an account. Use Recurring, TriggerBy, and UsageCategory to filter the results, and use the paging parameters to navigate the collection. The response includes page metadata and an array of usage trigger resources.

  • RetriesRetries up to 2×, 500ms backoff, 30s timeout.

7 parameters
AccountSidstringrequired
The 34-character SID of the account whose usage triggers you want to list, matching the `AC` SID format.
Recurringstringoptional
Filters by recurrence: `daily`, `monthly`, or `yearly` for recurring triggers, or `alltime` for non-recurring triggers.
Allowed:dailymonthlyyearlyalltime
TriggerBystringoptional
Filters by the usage field that fires the trigger: `count`, `usage`, or `price`.
Allowed:countusageprice
UsageCategorystringoptional
Filters triggers by a supported usage category.
PageSizeintegeroptional
The number of resources to return on each page. Defaults to 50 when omitted and must be between 1 and 1000.
Pageintegeroptional
The non-negative page index used to maintain client-side paging state. Defaults according to the API when omitted.
PageTokenstringoptional
The paging token provided by the API for retrieving a specific page.

1 status code
200Returns a paginated collection containing usage trigger resources and metadata including page boundaries, page size, navigation URIs, and the current page.
endintegeroptional
first_page_uristringoptional
next_page_uristringoptional
pageintegeroptional
page_sizeintegeroptional
previous_page_uristringoptional
startintegeroptional
uristringoptional
usage_triggersarray<object>optional

Error handling

AccountSid must be a 34-character account SID beginning with AC. If supplied, Recurring must be daily, monthly, yearly, or alltime, TriggerBy must be count, usage, or price, and PageSize must be between 1 and 1000. Use Page as a non-negative index and pass PageToken values provided by the API.