Implemented
0
API search for other fields than id_number or email
Source: invoiceninja/invoiceninja#3659 · opened by @frank42hh
Hi,
I'm trying to replace an old self-created invoice system with invoiceninja. Historically, the old system is not using integer IDs as customer identification, but alphanumeric ones. I managed to import the customer list, and set the "old" identification as custom_value1. The full text search on /clients is working fine, but I can't use custom_value1 in the API search, which is essential because I need to import invoice items from other databases, where I only have the old customer ID to map the items to the customer.
It would be great if I would be able to do so by
curl -H "X-Ninja-Token: abcde" -X GET "
so I can then create an invoice based on the id_number from the query result.
Is there any way to patch that into the API?
I'm trying to replace an old self-created invoice system with invoiceninja. Historically, the old system is not using integer IDs as customer identification, but alphanumeric ones. I managed to import the customer list, and set the "old" identification as custom_value1. The full text search on /clients is working fine, but I can't use custom_value1 in the API search, which is essential because I need to import invoice items from other databases, where I only have the old customer ID to map the items to the customer.
It would be great if I would be able to do so by
curl -H "X-Ninja-Token: abcde" -X GET "
so I can then create an invoice based on the id_number from the query result.
Is there any way to patch that into the API?
No pledges yet. Be the first to back this.
Comments
Similar requests
Support for Resend API as First-Class Email Provider (Including Email History)
2 votes · 0 comments
Add CC Email to Email Settings to pre-populate CC Email section
1 vote · 0 comments
Custom styling of email templates
0 votes · 0 comments
[Feature Request] Increase the number of custom fields or remove the limit on the number of custom fields
0 votes · 0 comments
Be able to Adjust the New User Language in Email
0 votes · 0 comments
No comments yet.