tag:help.lighthouseapp.com,2008-09-20:/discussions/api-developers/168-two-observationsLighthouse: Discussion 2011-04-07T05:38:32Ztag:help.lighthouseapp.com,2008-09-20:Comment/37117712010-11-09T16:32:55Z2010-11-09T16:32:56ZTwo observations<div><p>Hi guys,<br />
I just started using Lighthouse and intended to make use of the Lighthouse API via PHP.<br />
I noticed that in the API you mention getting ticket data for a project as sending a curl get request <code>/projects/#{project_id}/tickets.xml</code> which would lead one to believe it would be <code>/projects/#12345/tickets.xml</code> but in fact it should be <code>/projects/12345/tickets.xml</code></p>
<p>Also, the <code>+</code> in the email address that is provided to create tickets <code>ticket+site.12345-xx55x55@lighthouseapp.com</code> get interpreted as a space in mailto: links when using gmail.</p>
<p>Thanks!</p></div>hutch (at shutch)tag:help.lighthouseapp.com,2008-09-20:Comment/37117712010-11-09T19:01:23Z2010-11-09T19:01:23ZTwo observations<div><p>Hutch -</p>
<p>We're not able to recreate the email issue. Google does show explicit email links as invalid if you try to enter them that way, but while the hover state shows the link in an email to have a space, clicking on the mailto link pops up a new window that shows the To: address is correct. It seems to be a problem with Gmail's validation, since the format of our email is RFC valid.</p>
<p>The docs are correct. <code>#{project_id}</code> is a rubyism to show a variable needs to be there and what the variable name is.</p>
<p>Let me know if you have any other questions.</p>
<p>Thanks,<br />
Nicole</p></div>Nicole