Skip to content

Invoice UUID not supported in API? #495

@DawerRafi

Description

@DawerRafi

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions