Frequently Asked Questions (FAQ)
In this section, we list the frequently asked questions for the BILL API AP/AR workflows.
I am asked to pay to continue testing with my Sandbox account. Am I required to pay with my credit card?
Any BILL pricing plan or subscription is not charged in the Sandbox environment.
Use your test credit card for setting up a subscription for your sandbox developer account. When the trial period for your sandbox account is over, use the same test credit card to continue using your account.
See Add a test credit card in sandbox for more information.
Am I required to set up a new developer key (devKey
) for each of my test organizations and test users?
devKey
) for each of my test organizations and test users?When you generate a developer key, the key is available for you to use with any of your test organizations and test users.
When you sign in with POST /v3/login
, the generated sessionId
in the response is available only for the selected devKey
in your request. This sessionId
does not work with another devKey
.
How do I move all my production data to sandbox?
We do not recommend that you move any of your production data to sandbox. There can be unintended consequences. For example, you may be testing with your production data in sandbox, but the vendors and customers will receive emails based on your testing with bills and invoices.
In the BILL web app, select Settings > Import & Export to move any required information between your development environments.
How do I link a money movement object to a bill id
, invoice id
, or payment?
id
, invoice id
, or payment?Money movement objects enable you to view BILL money movement information for a bill, invoice, or payment. Currently, you cannot link a MoneyMovement
object with any other BILL object.
When I am testing with the API, I get the BDC_1322
(Max number of concurrent requests per organization reached.
). What should I do?
BDC_1322
(Max number of concurrent requests per organization reached.
). What should I do?Confirm whether your concurrent API requests per developer key per organization is not more than three.
When you receive this error, all subsequent API requests fail until one concurrent request is completed. Implement exponential backoff in your code to address concurrent rate limits.
See API rate limits for more information.
Updated 6 days ago