The FogBugz API makes it possible to do programmatically almost anything you could do in the interface.  The API can be used alone or in conjunction with FogBugz webhooks and third party services such as Slack, Salesforce, or TestRail (among many others) to build powerful integrations to improve your workflow and make the connection between FogBugz and your other systems seamless.

Below, you’ll find some general rules for API requests as well as links to other resources. Find links to our full documentation in the sidebar to the left.  Have questions?  Our support engineers are here to help.

Looking for our old documentation? Still using FogBugz For Your Server? Click here.

Prefer to work with JSON? Click here.

Not interested in writing code? Check out Zapier’s FogBugz integrations or hire our team for custom development work.

General rules for API requests

  • In general, all requests can either GET or POST.  If you are submitting files you must use a enctype=”multipart/form-data” POST.
  • All API requests will have a cmd argument indicating the action you intend to take and a token argument.  Parameters are passed with the request as name/value pairs.
  • FogBugz is going to be religiously UTF-8.
  • All dates should be in ISO 8601 UTC format, e.g. 2013-01-21T14:24:06Z.  To avoid inconsistencies caused by individual user localization, we recommend using ISO for dates in search strings
  • The API will respond with valid XML file in UTF-8 format containing an outer <response> tag at the root.
  • If something goes wrong, the first child node will <error>.
  • All requests should be URL encoded.

Developer Resources

Visit our developer resources site for to find a Quick Start Guide to working with the FogBugz API along with recipes for a few popular API tasks.

Professional Services

Hire us to build your integration or customization for you.


Still have questions? Our support team is here to help.