Skip to content
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

"[HTTP 401] Unable to create record: Authenticate" #133

Open
LyndonMcjohnson opened this issue Feb 15, 2022 · 3 comments
Open

"[HTTP 401] Unable to create record: Authenticate" #133

LyndonMcjohnson opened this issue Feb 15, 2022 · 3 comments

Comments

@LyndonMcjohnson
Copy link

LyndonMcjohnson commented Feb 15, 2022

What am I doing wrong here?

.env:

TWILIO_SID=[Valid SID]
TWILIO_AUTH_TOKEN=[Valid Token]
TWILIO_NUMBER=[Valid Number]
TWILIO_APPLICATION_SID=[Valid App SID]
TWILIO_API_KEY=[Valid API Key]
TWILIO_API_SECRET=[Valid API Secret]
TWILIO_ACCOUNT_SID=[Valid Account SID]

Notification Class:

public function via($notifiable)
{
    return ['mail', 'database', TwilioChannel::class];
}

public function toTwilio($notifiable)
{
    return (new TwilioMmsMessage())
	->content('Your service request for ' . $this->subscription->service->name . ' has been updated to the ' . $this->subscription->status . ' status')
	->mediaUrl(route('services'));
}

Controller:

$subscription->client->notify((new ServiceUpdated($subscription))->afterCommit());
@AlsonicTech
Copy link

Did you fixed this? I think is related to notifications that are sent into queues maybe?

@LyndonMcjohnson
Copy link
Author

No, I scratched it.

@edgrosvenor
Copy link

The problem is that this package expects the account SID to be used as the method of authentication rather than an API key. This PR would fix it for you: #135

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants