For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered user
on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats:
Following up from Ioan’s email, I can confirm that this change has now been made.
Any API users who are seeing failures because of this have 2 simple options to get their integration working again:
Change the sender address in your integration to match one of the registered email addresses in the FreeAgent app
Add the sender email address as used in your integration as a user in the FreeAgent app (a user with “No Access” permissions should be fine)
If you’re still having problems please let us know.
Thanks,
Paul.On Thursday, 1 October 2015 10:54:26 UTC+1, Ioan Serban wrote:
Hi developers,
For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered user
on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats:
I am still seeing the issue mentioned by Gavin above. However this is on
the sandbox environment, is there any chance that this fix hasn’t made it
to the sandbox environment yet?On Wednesday, January 6, 2016 at 4:35:44 PM UTC, Caius Durling wrote:
Hi Gavin,
As Dave mentioned earlier this was indeed a bug introduced yesterday by
accident. I’ve just pushed out a fix for it (along with more automated
tests to prevent further regressions in future), so you should be seeing
the correct behaviour from the API now.
Please let us know if you’re still seeing issues with it.
I’m really sorry to hear this change caused problems for you - we were
monitoring the logs to proactively contact any failing integrations, though
it looks like yours slipped through the net.
We’re investigating the easiest way to mailshot API users of planned
changes - we’ve done this for an upcoming change to our SSL config http://engineering.freeagent.com/2015/10/09/weak-dh/, though it’s a
largely manual process.
In the short term, if you haven’t already, you can subscribe to email
updates from this Google Group.
Google can batch updates into a single email so it hopefully wouldn’t be
too intrusive in your inbox.
Can I ask if this change was detailed in an official email to all
FreeAgent users?
I notice that the API page does not detail this piece of information and
this broke one of our live systems!
A change like this needs to be clearly communicated.
On Thursday, 1 October 2015 10:54:26 UTC+1, Ioan Serban wrote:
Hi developers,
For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered
user on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats:
Just to confirm I’ve just tried putting a charge through on our live
system, and the ‘from’ field is still populating with the master email for
the FA account. We are providing the payment gateway for multiple customers
so it is very confusing for our customers to get our name in the from field
instead of who they are purchasing their product with.On Wednesday, January 6, 2016 at 4:35:44 PM UTC, Caius Durling wrote:
Hi Gavin,
As Dave mentioned earlier this was indeed a bug introduced yesterday by
accident. I’ve just pushed out a fix for it (along with more automated
tests to prevent further regressions in future), so you should be seeing
the correct behaviour from the API now.
Please let us know if you’re still seeing issues with it.
As Dave mentioned earlier this was indeed a bug introduced yesterday by accident. I’ve just pushed out a fix for it (along with more automated tests to prevent further regressions in future), so you should be seeing the correct behaviour from the API now.
Please let us know if you’re still seeing issues with it.
Thanks,
C
Caius Durling
Engineer, FreeAgent
One Edinburgh Quay, 133 Fountainbridge, Edinburgh, EH3 9QG
FreeAgent Central Ltd. Registered in sunny Scotland SC316774
Can I ask if this change was detailed in an official email to all FreeAgent
users?
I notice that the API page does not detail this piece of information and
this broke one of our live systems!
A change like this needs to be clearly communicated.On Thursday, 1 October 2015 10:54:26 UTC+1, Ioan Serban wrote:
Hi developers,
For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered user
on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats:
Hi,> On 14 Jan 2016, at 14:07, barnaby@parall.ax wrote:
Just to confirm I’ve just tried putting a charge through on our live system, and the ‘from’ field is still populating with the master email for the FA account. We are providing the payment gateway for multiple customers so it is very confusing for our customers to get our name in the from field instead of who they are purchasing their product with.
The change was pushed to our sandbox system as well yes, sandbox should be behaving identically to the live production system.
Could you let me know the details of a request you’ve made that’s overridden the from address please? Specifically the subdomain of the FreeAgent account you’re sending it through, and the from address you’re passing to the API. Feel free to reply to me directly off list if you don’t want to post the details publicly. I’ll take a closer look for you then.
Thanks,
C
Caius Durling
Engineer, FreeAgent
One Edinburgh Quay, 133 Fountainbridge, Edinburgh, EH3 9QG
FreeAgent Central Ltd. Registered in sunny Scotland SC316774
I have a user with the email address support@mydomain in the Users list who
has “No Access” and that’s the email address that we’re sending through to
the API, but the invoice emails are still originating from my personal
email address - definitely not what I want! I’ve tried giving the user with
support@ access to “Time” to see if that fixes things, but it doesn’t.
Where do I go from here?
GavinOn Thursday, 5 November 2015 11:29:22 UTC, Paul Smith wrote:
Following up from Ioan’s email, I can confirm that this change has now been made.
Any API users who are seeing failures because of this have 2 simple options to get their integration working again:
Change the sender address in your integration to match one of the registered email addresses in the FreeAgent app
Add the sender email address as used in your integration as a user in the FreeAgent app (a user with “No Access” permissions should be fine)
If you’re still having problems please let us know.
Thanks,
Paul.
On Thursday, 1 October 2015 10:54:26 UTC+1, Ioan Serban wrote:
Hi developers,
For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered
user on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats:
I have a user with the email address support@mydomain in the Users list
who has “No Access” and that’s the email address that we’re sending through
to the API, but the invoice emails are still originating from my personal
email address - definitely not what I want! I’ve tried giving the user with
support@ access to “Time” to see if that fixes things, but it doesn’t.
Where do I go from here?
Gavin
On Thursday, 5 November 2015 11:29:22 UTC, Paul Smith wrote:
Following up from Ioan’s email, I can confirm that this change has now been made.
Any API users who are seeing failures because of this have 2 simple options to get their integration working again:
Change the sender address in your integration to match one of the registered email addresses in the FreeAgent app
Add the sender email address as used in your integration as a user in the FreeAgent app (a user with “No Access” permissions should be fine)
If you’re still having problems please let us know.
Thanks,
Paul.
On Thursday, 1 October 2015 10:54:26 UTC+1, Ioan Serban wrote:
Hi developers,
For security reasons, we’re making a change to how emails are being sent
out, which will impact the invoices /send_email endpoint.
Currently, you can pass in any email address as the value of the from
attribute. From the end of October,
any email address passed in there will have to belong to a registered
user on the company. If the email does
not belong to a user on the company, the API request will fail. We will
accept the following formats: