Reckon One API: 500 Internal Server Error, When creating invoice

Raman Jit Singh

Hello Team,


There is some problem I am facing when inserting Invoice via API. Please help me, this is urgent from the client side.


Request URL: https://api.reckon.com/R1/73308201-728e-4dc3-b5dc-fd4daaa12be5/invoices
JSON: {'CustomerId':'15e4d033-e633-4892-9af9-d514275fb62c','AmountTaxStatus':2,'InvoiceAmount':2.0000,'InvoiceDiscountAmount':null,'InvoiceDiscountPercentage':null,'InvoiceTax':0.1800,'Notes':null,'PaymentDetails':null,'Reference':null,'TemplateId':'3edc5b6f-37aa-4516-8c1e-3cf268bf51e6','InvoiceDate':'2017-03-07T00:00:00','SendDate':null,'DueDate':null,'Address':null,'TaxSummaryText':null,'LineItems':[{'InvoiceId':'00000000-0000-0000-0000-000000000000','ParentInvoiceLineItemId':null,'BillableId':null,'DiscountAmountExTax':null,'DiscountAmountTax':null,'DiscountAccuracy':null,'DiscountPercent':null,'Amount':2.00,'AmountAccuracy':null,'InvoiceDiscountedAmountExTax':1.8200,'InvoiceDiscountedTaxAmount':0.1800,'HasDataForPosting':true,'IsSubTotal':false,'IsParent':false,'IsHidden':false,'AccountId':'00000000-0000-0000-0000-000000000000','PrintGroupAsSingleLine':false,'ChargeableItemId':'8cd53f00-f6b9-4d6c-891d-83cc6a348e40','LineNo':1,'Description':'SD','Quantity':null,'ProjectId':'00000000-0000-0000-0000-000000000000','UnitPriceExTax':1.8181818182,'UnitPriceTax':0.1818181818,'UnitPricePrecision':2.0,'UnitPriceIsTaxInclusive':false,'TaxGroupId':'874835af-30c4-49ca-91c9-e5648c81a444','TaxIsModified':false,'TaxAmount':0.1800,'AmountExTax':1.8182}]}
Response status500 Internal Server Error





It always returns 500 error, Please help me. This is urgent.

Simon Hutchinson_8164484

Hi Raman,

When you are authorising with the oauth server are you using a id (for example 1234-1) or a username?

Jason Hollis

You need to use your username (post Reckon Portal release) to authorise the indentity server for your integration app. This effects Reckon One only at this point. As other products of ours move into the portal eco-system they too will use ?username ?to authorise the API rather than user id.