Hi @cliff
That’s unfortunate. I’ll try to schedule some time soon to have a look. Until then, it would be helpful if you could contact textit support to get some answers into why this is occuring.
thanks alot @diana , will be waiting
@cliff
I have just checked again that the user-agent header is added to the outgoing requests to rapidpro, and for my local development environment, it looks like this:
https://www.textit.com/api/v2/broadcasts.json {
authorization: 'Token "test"',
accept: 'application/json',
'content-type': 'application/json',
'user-agent': 'Community Health Toolkit/4.19.0-local-development (linux,x64)'
}
So something else is causing this. Could you please contact RapidPro support and work with them to figure out what is happening here? Is there some update or some documentation around this? Any way that we can have some insight into why these requests fail?
Thanks!
4 Likes
@cliff I created a test textit account and tested it against my local cht instance and have no errors.
I’m assuming there is some error in your configuration.
thanks @diana for the feedback ,
Here is the way am setting the configurations
curl -X PUT -H "Content-Type: text/plain" "https://medic:<password>@domain/api/v1/credentials/rapidpro:outgoing" -d 'Token <textit-api-token>'
curl -X PUT -H "Content-Type: text/plain" "https://medic:<password>@domain/api/v1/credentials/rapidpro:incoming" -d 'cht-api-key'
curl -X PUT -H "Content-Type: text/plain" "https://medic:<password>@domain/api/v1/credentials/rapidpro:app" -d 'Token <text-api-token>'
and in the app settings
"sms": {
"outgoing_service": "rapidpro",
"rapidpro": {
"url": "https://textit.com/"
}
},
what could i be missing ?
This should be:
curl -X PUT -H "Content-Type: text/plain" "https://medic:<password>@domain/api/v1/credentials/rapidpro:outgoing" -d '<textit-api-token>'
Without the “Token”.
2 Likes
thanks alot @diana , it works now , outgoing messages are reaching Textit
3 Likes