Sinch Conversation
Your agent works in Sinch Conversation with your key, and never holds it.
- 7 days free
- Cancel anytime
- Nothing to install
- Kind of work
- Chat, texts and calls
- How you connect
- Client ID and secret
- What waits for you
- Nothing, until you turn on asking
What your agent can do there
Post to channels, send messages and texts, place calls.
- SMS
- RCS
- Messenger
- messaging
- conversations
- contacts
At the provider
Technical details
- Hosts
- us.conversation.api.sinch.com, eu.conversation.api.sinch.com, br.conversation.api.sinch.com
- Key type
- oauth2-cc
- Key goes in
- Authorization
Which calls read, write or destroy
| When | Class |
|---|---|
| GET ^/v1/projects/[^/]+/(apps/[^/]+/)?webhooks(/[^/]+)?/?$ | read |
Without a matching rule, GET, HEAD and OPTIONS read, POST, PUT and PATCH write, and DELETE and any other method destroy. A recipe rule only raises a GET the vendor changes something with to a write. No recipe rule makes a call destructive.
Token IP filtering
If the provider can limit a token to IP addresses, allow Sallyport's outbound address. The connection form shows it, ready to copy.
Bring a service the catalogue has never seen
Add its web address and your key, and your agent uses it like any of the 827. If your agent runs into a service you haven’t added, it sends you a link.
- 7 days free
- Cancel anytime
- Nothing to install