3CX Call Control API

[Roberto Neves]

Hey guys.
I'm trying to deploy something using Call Control API on a Debian server, but I can't find any documents about it.
I tried acessing this URL (as I saw it on other posts) https://www.3cx.com/docs/call-control-api/ , but I got nothing either.
Could you guys help me? Please!
Thanks in advance.
Best regards.

 

[edossantos]

The documentation for this API is not available anymore, sorry.

 

[Roberto Neves]

Thanks for the reply, Ernesto.
Can you provide any information about the future os this API. Is it going to be discontinued?
Once again, thanks for the help.

 

[edossantos]

No, the API is still fully functional, and it's used internally by 3CX. But the management decided that the API should only be used by 3CX, so the documentation has been removed.

 

[GaSo]

So basically the functionality for advanced users is going backward instead of forward with 3CX? Programmers and people who want to build beyond what 3CX supports are not welcome at 3CX? Meaning if a customer wants something 3CX doesn't support, we need to just sell the software from a competitor from 3CX instead.. as you leave us with no options? while we have all the programmers internally... with just a few lines of code if there was only an API... that really makes no sense.

 

[Charlie Devlin]

So basically the functionality for advanced users is going backward instead of forward with 3CX? Programmers and people who want to build beyond what 3CX supports are not welcome at 3CX? Meaning if a customer wants something 3CX doesn't support, we need to just sell the software from a competitor from 3CX instead.. as you leave us with no options? while we have all the programmers internally... with just a few lines of code if there was only an API... that really makes no sense.

We bought 3CX because there was the API and now its not available, but there are people such as VOIP who have tool to do what the API should let us do ourselves. Why is this or is it just you want to charge customers extra

 

[edossantos]

We bought 3CX because there was the API and now its not available, but there are people such as VOIP who have tool to do what the API should let us do ourselves. Why is this or is it just you want to charge customers extra

As I mentioned, the API is still available and fully functional, you can use it. But there is no documentation about it.

 

[Charlie Devlin]

That clever so we are meant to guess what the calls are.

If the API is still available why hide the documentation

It like saying your new central heating system is available but there are no instructions on how to put it together.

 

[treefiddy]

This would explain my developers wanting nothing to do with 3CX and are pushing for a new phone system.

Please give customers real APIs so we can integrate your product as we please.

 

[Chris Collins]

FWIW - there was mention recently of upcoming (?) REST API (see bottom of blog post at https://www.3cx.com/blog/releases/call-flow-designer-v16/) - "Avoid using dialers in new projects, as they are soon to be deprecated in favour of outbound dialing via REST API."

I'm assuming that this is on the roadmap soon(ish) and for customer use; we're just holding tight for the time being on any more API work - I'll be interested to see what form the REST API takes.

 

[edossantos]

I'm assuming that this is on the roadmap soon(ish) and for customer use; we're just holding tight for the time being on any more API work - I'll be interested to see what form the REST API takes.

Yes, we're working on that. It will be included in a further 3CX update. We're not sure exactly when, but it's on the way.

 

[treefiddy]

@edossantos

Glad to hear. I just hope it isn't lacking in features.

Can we expect a blog post about it anytime soon?

 

[edossantos]

Can we expect a blog post about it anytime soon?

The REST API is not included in Update 1. I can't tell in which update it will be available, we're working on it. We will make an announcement in the 3CX blog when the feature is ready, you can be sure of that.