Ingress Endpoints

Ingress endpoints are used to modify data within TLDCRM or TLDialer. While TQL is used within these endpoints, it is not the standard. Instead Ingress allows for specific parameter and parameter patterns per endpoint depending on use-case. While most endpoints work the same there are much more robust validations in play when modifying data in TLD.

The Following are a List of Ingress Endpoints Available

Endpoint	POST	PUT	DELETE	Docs

Endpoint	POST	PUT	DELETE	Docs
`/api/ingress/callback`	✓	✘	✘	Ingress Callback
`/api/ingress/calls/inbound/billable`	✓	✘	✘	Ingress Calls - Inbound Billable
`/api/ingress/dependent`	✓	✓	✘
`/api/ingress/dnc`	✓	✘	✓	Ingress DNC - Do Not Contact
`/api/ingress/documents/upload/lead`	✓	✘	✘	Ingress Documents \| Upload: Add a Document to a Lead
`/api/ingress/documents/upload/policy`	✓	✘	✘	Ingress Documents \| Upload: Add a Document to a Policy
`/api/ingress/fpg`	✓	✘	✓	Ingress FPG - Filter Phone Groups
`/api/ingress/hopper`	✓	✘	✓	Ingress Hopper
`/api/ingress/leads`	✓	✓	✘
`/api/ingress/note`	✓	✘	✘
`/api/ingress/policies`	✓	✓	✘
`/api/ingress/relays/send`	✓	✘	✘	https://esotech.atlassian.net/wiki/x/IYD9DQ
`/api/ingress/tags`	✓	✓	✓	Ingress Tags
`/api/ingress/user_group_members`	✓	✓	✓	Ingress User Group Members
`/api/ingress/user_meta`	✘	✓	✘	Ingress User Meta
`/api/ingress/users`	✘	✓	✘	Ingress Users