Empty Response to invoice create call

Mike L

Recently we've been testing with the Sky API on our FENXT account. We have a script that parses a CSV, where each row would in turn produce related debit + credit distribution data within the overall JSON payload for the Accounts Payable invoice create call.

While successful with smaller payloads (25-50 rows), we recently created an API call that had a CSV with 240 rows, thus the payload is much larger given the debit/credit lines needed.

When calling the Sky API Invoice Create endpoint with this larger payload, we do not receive any kind of error in the API response. The API response is in fact empty after the call runs for about 100 seconds or so (and no invoice is created in the system.)

There has been no timeout on our server that's executing the API call code.

What are we to make of the SKY API silently failing in this way?

Are there any known payload size / POST call maximums/limits?

What about timeout periods on the Sky API side of things?

Any feedback that knowledgeable folks could provide on the above would be greatly appreciated.

Thanks,

-Mike

Erik Leaver

@Mike L Were you able to get this resolved? If not, please submit a support case & reach out to me with the case number so I can monitor.

Mike L

@Erik Leaver

Thank you for the follow up. Unfortunately we were never able to get around this apparent payload/timeout issue to allow for a single invoice creation on a larger distribution amount invoice.

The workaround solution for now is that our import application automatically breaks up the import/distributions into several invoice imports, so if we have an invoice import that has, say, 200 distribution lines in the CSV, it ends up creating 3 invoices that are related, e.g. InvoiceNumberXYZ-1, InvoiceNumberXYZ-2, InvoiceNumberXYZ-3.

Not exactly ideal but at least gets us to a functional standpoint ahead of us migrating fully to FENXT.

Alex Wong

@Mike L
If you haven't already, use a JSON formatter tool to confirm your payload is correctly formatted. ( https://jsongrid.com/json-grid)

if the JSON is good, then try to use the API Console on developer.blackbaud.com and debug using it.

Erik Leaver

@Mike L Glad you found a workaround. Did you ever submit a case to support?