Job Stuck via the API

Sometimes if you are using an API it may feel like a job is stuck or not moving through our production process.  There are two main reasons this may occur.  First your API could be in test mode.  But most of the time this is because the job entered our website from your API when you didn't have enough money in your account to cover the cost of the job.  Since we don't work on jobs until they are paid for the job is just sitting awaiting payment.

Unfortunately, even after adding payment you need to go through the check-out process to get this job(s) out.  You can add funds to your prepay and then go to the shopping cart, or you can go directly to the shopping cart (by clicking Shopping Cart in the upper right corner of the screen).

Why does it act this way?
Some API customers use our website manually AND through the API, and if adding funds automatically pushed all jobs through the shopping cart experience, you might accidentally mail someone else's' job that isn't ready to be mailed yet.

How can I improve this?
A great way to prevent this is to keep your account properly funded.  To assist with this, we recommend using the Low Balance Alert feature located on the Billing Information page.  Here you can enter your email address and a low balance amount and we will notify you any time your account falls below the balance that you've entered.

If your API is in test mode, your account will say  *** Account in Test Mode *** near the very top of the web page and it will be highlighted in yellow.  You can visit the API Information page under My Account to take your account out of test mode.  But, make sure you are thoroughly familiar with what you are doing before you make this change.  It may have many unintended consequences.