-
Notifications
You must be signed in to change notification settings - Fork 96
ChatAPI functionality #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ChatAPI functionality
My first instinct is that I would separate all Chat API-related objects and resources into their own sub-namespace. So where it's now |
I agree with @samwierema |
Should we do it only for the Chat related objects? |
@sotoz yes, everything else should remain in place. |
Changed namespace for chat-api related objects/resources
Fixed examples
|
||
require_once(__DIR__ . '/../autoload.php'); | ||
|
||
$MessageBird = new \MessageBird\Client('YOUR_ACCESS_KEY '); // Set your own API access key here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dummy access key contains tab character.
Please also check for double newlines (maybe run phpcs with PSR2)? |
Removed tab character from dummy access key
@@ -11,6 +11,7 @@ class Client | |||
{ | |||
|
|||
const ENDPOINT = 'https://rest.messagebird.com'; | |||
const CHATAPI_ENDPOINT = 'https://chat.messagebird.com/1'; | |||
|
|||
const CLIENT_VERSION = '1.4.1'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be updated during release somehow?
no example to create contacts? |
|
Fixed contactId and typo.
Added actions for Chat API.
Created examples for every needed action.