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

Invoice UUID not supported in API? #495

Open
DawerRafi opened this issue Apr 30, 2021 · 6 comments
Open

Invoice UUID not supported in API? #495

DawerRafi opened this issue Apr 30, 2021 · 6 comments
Assignees
Labels

Comments

@DawerRafi
Copy link

Warning: Github issues are not an official support channel for Recurly. If you have an urgent request we suggest you contact us through an official channel: [email protected] or https://recurly.zendesk.com

I was told that the API and Automated Exports does not have a 1-1 match. However, I would expect atleast some way to match records from the Automated Exports with the records in API, if incase any additional information is needed.

Currently, I have Automated Exports enabled for Invoices, but the Invoice ID I get from there is a UUID, which I cannot use in get_invoice() function, because unlike other get functions, get_invoice() does not accept UUID.

Furthermore, in the API documentation, I dont even see UUID in Invoice resource at all, which makes me wonder, why do we show Invoice UUID in Automated Exports in the first place?

In my opinion, we should add Invoice UUID to Invoice resource in the API so that its consistent with other resources

@douglasmiller
Copy link
Contributor

@DawerRafi you can use the Invoice Number when using the get_invoice operation.

Invoice ID or number. For ID no prefix is used e.g. e28zov4fw0v2. For number use prefix number-, e.g. number-1000.

get_invoice("number-%s" % invoice_number)

@douglasmiller douglasmiller self-assigned this Apr 30, 2021
@DawerRafi
Copy link
Author

DawerRafi commented Apr 30, 2021

Hi @douglasmiller, thats true. However, my use-case is a little different. I maintain our company's data warehouse and sync back incremental changes from Recurly. Initial data was loaded from the API, So we had Invoice ID and Invoice Number fields. Now, I wanted to utilize Automated Exports to load incremental data everyday.
In Automated Export for Invoice, we have Invoice UUID and Invoice Number.
But this wont work for me, because I can't Interchangeabily use Invoice UUID with Invoice ID. To remedy this, I would have to ping the API anyways with Invoice number to get the Invoice ID, which defeats the purpose of Automated Exports.

@douglasmiller
Copy link
Contributor

Ah! That's a very reasonable request, @DawerRafi. I'll check in with the team that manages Automated Exports and see if they can get the ID included. I'll get back to you.

@DawerRafi
Copy link
Author

@douglasmiller Thanks alot! Please also mention that this change is also needed in Transactions Automated Export since it also includes Invoice UUID field and the problem is the same there too.

@DawerRafi
Copy link
Author

Hi @douglasmiller, is there any update this?

@douglasmiller
Copy link
Contributor

@DawerRafi I do not have any information, unfortunately. I passed on your request and was told that they would look into it. It might bring more attention to the request if you were to contact support or email them at [email protected]

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

No branches or pull requests

2 participants