Automate CallFire Documentation

What CallFire Documentation is

CallFire

API host: api.callfire.com

What HumDay can do in CallFire Documentation

55 documented operations change something in CallFire Documentation. The 52 most useful are listed here.

• POSTCreate contact list from file/contacts/lists/upload
• POSTAdd do not contact (dnc) numbers/contacts/dncs
• POSTCreate contact lists/contacts/lists
• DELETEDelete contacts from a contact list/contacts/lists/{id}/items
• POSTAdd contacts to a contact list/contacts/lists/{id}/items
• POSTAdd sound via file/campaigns/sounds/files
• POSTCreate contacts/contacts
• POSTCreate a webhook/webhooks
• DELETEDelete a contact list/contacts/lists/{id}
• PUTUpdate a contact list/contacts/lists/{id}
• DELETEDelete a contact from a contact list/contacts/lists/{id}/items/{contactId}
• POSTCreate an auto reply/texts/auto-replys
• DELETEDelete a contact/contacts/{id}
• PUTUpdate a contact/contacts/{id}
• POSTSend calls/calls
• POSTCreate media/media
• POSTSend texts/texts
• DELETEDelete do not contact (dnc) number./contacts/dncs/{number}
• PUTUpdate an individual do not contact (dnc) number/contacts/dncs/{number}
• POSTPurchase numbers/orders/numbers
• POSTPurchase keywords/orders/keywords
• POSTCreate a call broadcast/calls/broadcasts
• POSTCreate a text broadcast/texts/broadcasts
• DELETEDelete do not contact (dnc) numbers contained in source./contacts/dncs/sources/{source}
• DELETEDelete a webhook/webhooks/{id}
• PUTUpdate a webhook/webhooks/{id}
• POSTCreate api credentials/me/api/credentials
• POSTAdd sound via text-to-speech/campaigns/sounds/tts
• POSTAdd sound via call/campaigns/sounds/calls
• DELETEDelete an auto reply/texts/auto-replys/{id}
• POSTCreate a caller id/me/callerids/{callerid}
• POSTAdd batches to a call broadcast/calls/broadcasts/{id}/batches
• POSTAdd batches to a text broadcast/texts/broadcasts/{id}/batches
• POSTAdd recipients to a call broadcast/calls/broadcasts/{id}/recipients
• POSTAdd recipients to a text broadcast/texts/broadcasts/{id}/recipients
• PUTUpdate a call broadcast/calls/broadcasts/{id}
• DELETEDelete a specific sound/campaigns/sounds/{id}
• PUTUpdate a text broadcast/texts/broadcasts/{id}
• PUTUpdate a batch/campaigns/batches/{id}
• PUTUpdate a lease/numbers/leases/{number}
• PUTUpdate a lease/keywords/leases/{keyword}
• DELETEDelete api credentials/me/api/credentials/{id}
• POSTStop voice broadcast/calls/broadcasts/{id}/stop
• POSTStop text broadcast/texts/broadcasts/{id}/stop
• POSTStart voice broadcast/calls/broadcasts/{id}/start
• POSTStart text broadcast/texts/broadcasts/{id}/start
• POSTArchive voice broadcast/calls/broadcasts/{id}/archive
• POSTArchive text broadcast/texts/broadcasts/{id}/archive
• PUTUpdate a lease config/numbers/leases/configs/{number}
• PUTUpdate a keyword lease config/keywords/leases/configs/{keyword}
• POSTVerify a caller id/me/callerids/{callerid}/verification-code
• POSTDisable/enable undialed recipients in broadcast/calls/broadcasts/{id}/toggleRecipientsStatus

What HumDay can read from CallFire Documentation

These are the operations a schedule or a trigger can watch.

• GETFind do not contact (dnc) items/contacts/dncs
• GETFind contacts in a contact list/contacts/lists/{id}/items
• GETFind a specific contact list/contacts/lists/{id}
• GETFind contact lists/contacts/lists
• GETFind a specific order/orders/{id}
• GETFind a specific contact/contacts/{id}
• GETFind orders/orders
• GETFind contacts/contacts
• GETFind a contact's history/contacts/{id}/history
• GETGet do not contact (dnc)/contacts/dncs/{number}
• GETFind webhook resources/webhooks/resources
• GETFind a specific webhook/webhooks/{id}
• GETFind calls/calls
• GETFind media/media
• GETFind texts/texts
• GETFind keywords/keywords
• GETFind webhooks/webhooks
• GETDownload a MP3 media/media/{id}/file
• GETFind a specific auto reply/texts/auto-replys/{id}
• GETFind specific webhook resource/webhooks/resources/{resource}
• GETFind account details/me/account
• GETFind caller ids/me/callerids
• GETFind local numbers/numbers/local
• GETFind leases/numbers/leases
• GETFind keyword leases/keywords/leases
• GETFind number regions/numbers/regions
• GETFind call broadcasts/calls/broadcasts
• GETFind sounds/campaigns/sounds
• GETFind tollfree numbers/numbers/tollfree
• GETGet delivery reports by ad hoc criteria/reports/delivery
• GETFind text broadcasts/texts/broadcasts
• GETFind auto replies/texts/auto-replys
• GETFind a specific call/calls/{id}
• GETGet a specific media/media/{id}
• GETFind a specific text/texts/{id}
• GETFind universal do not contacts (udnc) associated with toNumber/contacts/dncs/universals/{toNumber}
• GETFind api credentials/me/api/credentials
• GETFind lease configs/numbers/leases/configs
• GETFind keyword lease configs/keywords/leases/configs
• GETGet call recordings for a call/calls/{id}/recordings
• GETFind a specific call broadcast/calls/broadcasts/{id}
• GETGet call recording by id/calls/recordings/{id}
• GETFind a specific sound/campaigns/sounds/{id}
• GETFind a specific text broadcast/texts/broadcasts/{id}
• GETFind a specific batch/campaigns/batches/{id}
• GETFind a specific lease/numbers/leases/{number}
• GETFind a specific lease/keywords/leases/{keyword}
• GETCheck for a specific keyword/keywords/{keyword}/available

How automating CallFire Documentation works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live CallFire Documentation account.
4. Grant access, then go live. You approve the specific CallFire Documentation operations it may use — and only those.

Popular CallFire Documentation integrations

Connect CallFire Documentation to the tools people pair it with most.

• CallFire Documentation and OData for namespace microsoft.graphintegration
• CallFire Documentation and Cloudflareintegration
• CallFire Documentation and NetBoxintegration
• CallFire Documentation and GitHubintegration
• CallFire Documentation and Mistintegration
• CallFire Documentation and Loket.nlintegration
• CallFire Documentation and Atlassian The Jira Cloud platformintegration
• CallFire Documentation and Magento B2Bintegration
• CallFire Documentation and Stripeintegration
• CallFire Documentation and Zuora Reference Billingintegration
• CallFire Documentation and bunqintegration
• CallFire Documentation and DocuSignintegration

Automate CallFire Documentation with these

• Zoom369 operations
• Telnyx361 operations
• Twilio199 operations
• Twilio Preview147 operations
• Twilio Conversations101 operations
• Twilio Taskrouter60 operations
• Twilio Verify53 operations
• Twilio Autopilot52 operations
• Twilio Flex50 operations
• Twilio Sync48 operations
• Twilio Trusthub48 operations
• Twilio Messaging45 operations

Categories

• Telecom

Questions about CallFire Documentation automation

Can HumDay connect to CallFire Documentation?

Yes. HumDay reads CallFire Documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 122 operations are documented.

Do I need to write code to automate CallFire Documentation?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your CallFire Documentation account.

What can HumDay do in CallFire Documentation?

55 of the 122 documented operations change something in CallFire Documentation, and 67 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my CallFire Documentation account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to CallFire Documentation is held behind that approval.

Where this came from

The operations above are read from a published API description for CallFire Documentation at www.callfire.com/v2/api-docs/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.