New REST API Missing ExchangeRates

Extensibility
1

The new rest API does not have an endpoint or any way to modify the TX Rate when entering a new purchase in a different currency.

Frustratingly meaning I cannot raise purchases via the new API, and again back to the UI.

Please add the ability to set the exchange rate when creating the purchase (like you can on the current UI)

You clearly store the data, but you cannot SET it when creating the purchase and the system silently accepts it, but uses the Quickfile default and not one you set.

Additionally, You cant update it by the API either.

Doing more research, this appears to have been and issue with the old API for years too..
Please tell me this is going to be fixed / added to this API?

{
"id": 0,
"created_date": "string",
"receipt_date": "string",
"due_date": "string",
"supplier_name": "string",
"supplier_id": 0,
"supplier_reference": "string",
"receipt_number": "string",
"description": "string",
"currency": "string",
"net_total": 0,
"vat_total": 0,
"gross_total": 0,
"status": "string",
"exchange_rate": 0,
"parent_id": 0,
"item_lines": \[
{
"id": 0,
"nominal_code": 0,
"description": "string",
"sub_total": 0,
"vat_rate": 0,
"vat_amount": 0,
"line_total": 0
}
\],
"tags": \[
"string"
\],
"vat_codes": \[
"string"
\]
}

Thanks.

1 Like
2

Hi @Graham_S

Thank you for your feedback!

As the APIv2 is still in beta, our initial aim is to match the existing API in terms of what’s available (both functionally and data wise), so that when the older API is decommissioned, nothing is lost.

I agree this would be a helpful addition, and I’ve added it to our road map, however, I’m not able to provide a timescale for this at present.

We’ll keep you posted with any updates.

1 Like
4

Thanks, That is a major shame it cant be implemented sooner.

It seems to be a major sticking point on the current API and prevents us from using it.

Such a shame.

Hopefully it will be early on the roadmap.

5

As soon as there’s anything to share, we’ll let you know here. Watch this space.

In the meantime, as you rightfully mention, it will adopt the default daily exchange rate pulled from xe.com, the same as the web interface.

6

Thanks.

Unfortunately it doesn’t follow the web interface design in that you cannot edit it when creating.

Similar, the API doesn’t support modifying it after creation (like in the web interface)

So the addition of being able to specify the rate upon creation and being able to update it via a patch post is probably essential.

Thanks.

7

Additionally, you also have issues with Cloudflare sitting in front of your API.

Cloudflare is blocking certain python libs like URLLIB from accessing the API.

Making programmatic access very difficult.